Version: 1.0
Date: June 2026
Prepared By: DataTracks
The AURORA Portal supports Microsoft Single Sign-On (SSO), allowing users to access the portal using their existing Microsoft corporate credentials without maintaining a separate password.
There are two methods available for using SSO within the portal:
Method | Description |
| Enable SSO from Profile | Existing users can link their AURORA account to their Microsoft account. |
| Import Users from Azure AD | Administrators can import users directly from Microsoft Azure Active Directory and grant access to the portal. |
This guide explains both methods in detail.
Before configuring SSO, ensure the following requirements are met:
Note: Browser pop-ups must be allowed for Microsoft authentication windows.
Before enabling SSO, users must first log in to the AURORA Portal using the existing email address and password.
You will be redirected to the AURORA Portal home page.
Note: First-time login must be completed using email and password. SSO can only be enabled after successful login. The user can user either SSO(Single Sign on) or MFA(Multi Factor Authentication)
After logging in, users can link their AURORA account with their Microsoft account. Once linked, future logins can be performed using Microsoft SSO.
The View/Edit Customer Profile page opens.
Profile Page
Scroll to the bottom of the Profile page.
The following options will be displayed:
| Option | Description |
| Enable for Me | Enables AURORA MFA for your account. |
| Enable for All Users | Enables AURORA MFA for all users in the organization. |
| ENABLE SSO | Links the account to Microsoft Azure AD and disables AURORA MFA for that user. Authentication is managed through Microsoft. |
Two Factor Authentication Section with ENABLE SSO Button
Once Single Sign-On (SSO) is enabled for a user account, the AURORA Portal's built-in Multi-Factor Authentication (MFA) functionality is automatically disabled for that user.
Authentication and any additional security verification are then managed entirely by Microsoft Azure Active Directory (Azure AD).
If your organization has Microsoft MFA enabled, users will continue to be challenged for MFA during the Microsoft sign-in process based on the organization's Azure AD security policies.
Therefore:

Microsoft Sign-In Screen
Microsoft Consent/Permissions Screen
Successful SSO Linking Confirmation
Your account is now mapped to your Microsoft identity. For future logins, use the Sign in with Microsoft option available on the login page.
Administrators can import users directly from Azure Active Directory and invite them to access the AURORA Portal.
Imported users will authenticate exclusively through Microsoft SSO.
The Users page opens displaying all existing users.
Users Page with INVITE USER and IMPORT FROM AD Buttons
Microsoft Authentication Window
Azure AD User Selection Screen
Invite Confirmation Screen
After import, the Users page displays user status information.
| Column | Description |
| Name | User's full name |
| Registered email address | |
| User Role | Assigned role |
| Invite Status | Invitation status |
| Status | Active/Inactive |
| Lock Status | Locked/Unlocked |
| Azure Status | Azure AD linkage status |
Imported Users with Azure Status
Important: Imported users do not receive a separate portal password and must use Microsoft SSO to access the application.
Once invited, users can access the portal using Microsoft authentication.
Login Page Showing Sign in with Microsoft
Figure 13 – MFA Verification Screen
Successful Portal Login After SSO
Note: No separate AURORA password is required for imported SSO users.
Signing out terminates both the AURORA Portal session and the Microsoft SSO session.
Sign Out Menu Option
Logout Confirmation/Login Page
Important: Always use Sign Out instead of closing the browser window, especially on shared devices.
| Issue | Resolution |
| Microsoft popup does not appear | Enable browser pop-ups |
| Unable to link account | Verify email address matches Azure AD email |
| User not visible in Import From AD | Confirm user exists in Azure AD |
| Login redirects repeatedly | Clear browser cache and cookies |
| MFA authentication failure | Contact your organization's IT team |
| Access denied after authentication | Verify portal permissions and assigned role |
Please contact your system administrator or DataTracks Support.
The Azure AD mapping may need to be updated by an administrator.
No. Imported users authenticate directly through Microsoft and do not maintain a separate AURORA password.
No. Once SSO is enabled, the AURORA Portal's built-in MFA functionality is disabled for that account. Any multi-factor authentication requirements must be managed through Microsoft Azure AD.
Yes, if MFA is enforced through your organization's Microsoft Azure AD policies. In this case, MFA is handled by Microsoft rather than the AURORA Portal.
| Task | Location |
| Enable SSO for yourself | Profile → Two Factor Authentication → ENABLE SSO |
| Import Azure AD Users | Users → IMPORT FROM AD |
| Invite Individual User | Users → INVITE USER |
| Verify Azure Link Status | Users → Azure Status Column |
| Login with Microsoft | Login Page → Sign in with Microsoft |
| Sign Out | Profile Menu → Sign Out |
For assistance with Single Sign-On configuration, user provisioning, or login issues, please contact the DataTracks Support Team.