How Microsoft sign-in works
Requidex supports Microsoft Single Sign-On (SSO) for hiring companies. Setup involves both your Microsoft Entra ID (Azure AD) tenant and the company's SSO settings in Requidex. Configuring Microsoft alone does not enable SSO in Requidex.
Requidex uses its own Microsoft application for sign-in. Your organisation does not need to create a separate app registration or provide a client secret for the company settings. Your IT team controls access and consent in your Entra tenant.
Before you enable SSO
Identify the email domains whose users should sign in with Microsoft and the Directory (tenant) ID for the Microsoft Entra tenant that will authenticate them.
Ensure each intended user has an active Requidex account with the email address they will use in Microsoft. Sending an invitation email is optional for Microsoft sign-in: the account is verified when the user successfully signs in with Microsoft. Signing in with Microsoft does not create a Requidex account or grant company access.
Choose a support email address that users can contact if sign-in fails.
Plan any exception domains for users who should keep the normal Requidex password sign-in. Exceptions are domains, not individual email addresses.
Check access in Microsoft Entra ID
Your Entra administrator manages your tenant's security and access policies. The Requidex company form does not ask for a Microsoft client ID, client secret, SAML metadata, or a redirect URL.
Ask your Microsoft Entra administrator to confirm that your organisation permits users to sign in to the Requidex application. If Microsoft asks for consent, follow your organisation's consent process; an administrator may need to grant it.
If your organisation requires assignment to the Requidex enterprise application, assign the users or groups who need access. An unassigned user can be blocked by Microsoft even when SSO is enabled in Requidex.
Record the Directory (tenant) ID for the tenant your users will sign in through. You will enter it in the Requidex company settings.
Configure the company in Requidex
You need permission to edit the company to save these settings. Enable SSO after confirming that the intended users can access the Requidex application in Microsoft.
Open the hiring company's detail page in Requidex and select Users.
In Single Sign-On (SSO), turn on SSO Enabled.
Leave Type set to Microsoft.
Enter the sign-in email domains in Domains, separated by commas, for example example.com, company.co.uk. These domains make Requidex direct matching email addresses to Microsoft sign-in.
If needed, enter password sign-in exception domains in Exceptions, separated by commas. Keep those domains out of Domains so their users are not redirected to Microsoft at the email check.
Enter the Support Email and your Microsoft Directory (tenant) ID in Tenant ID.
Select Save.
Test sign-in
Microsoft sign-in is available on the main Requidex site, not on a separately branded portal.
On the main Requidex sign-in page, enter the email address of an existing Requidex user in a configured domain and continue.
Requidex should show that Microsoft sign-in is required and redirect the user to Microsoft. Complete sign-in with the account in the configured tenant.
Confirm that the user returns to Requidex with the expected access. The Continue with Microsoft button is another way to start Microsoft sign-in.
If sign-in does not work
No account found for this email: check that the Requidex user account exists, is active, and uses the same email address. Password sign-in also requires a verified account; Microsoft sign-in verifies the account after successful authentication.
No Microsoft redirect after entering an email: check that SSO is enabled and the email domain appears in the company's Domains field. An exception domain should not also be in Domains.
Microsoft blocks access or requests approval: ask your Entra administrator to check application consent, access policies, and any required user or group assignment.
Invalid SSO tenant for this domain: confirm the Tenant ID in Requidex matches the tenant used to sign in.
Account registration required after Microsoft sign-in: ask your company administrator to add the user to Requidex and assign the appropriate access.
If the issue continues, contact the Support Email shown during sign-in.
For agencies
An agency does not have its own SSO configuration on its agency page. A hiring company's allowed email domains do not restrict agency users changing their Requidex email address. If your agency account is expected to use Microsoft sign-in, ask the hiring company managing your access which sign-in method and email address apply. Your Requidex account must still be created and assigned access.
Switching between Requidex, Work and innDex
For both hirers and agencies, enabled Work and innDex shortcuts open the destination's Microsoft sign-in in the current tab. Your email address is passed as a login hint. Microsoft may reuse your existing Microsoft session or ask you to select an account, sign in, grant consent or complete MFA.
Each application checks its own account and permissions. Your account must already exist and have the required access; switching does not create accounts or grant access. Requidex Microsoft sign-in requires the organisation's SSO configuration and is available on the main Requidex site.
Work links to Requidex can return you to the requested timesheet or page after Microsoft sign-in. innDex currently opens its normal landing page. Signing out of one application does not sign you out of the others.