Exclusive Symania OIDC authention EntraID Bypass
Budget: $250 – $750 USD
Our Microsoft Entra ID tenant is 100 % cloud-only, yet users still see the default flow: Entra password first, then Microsoft Authenticator / e-mail OTP / QR prompts. I need that entire first-party sequence removed so the sign-in goes straight to our external OpenID Connect provider, Symania, and nothing else.
What has to happen
• At sign-in the user is redirected immediately to Symania’s OIDC page, no password screen or Microsoft second factors in between.
• Microsoft Authenticator, e-mail OTP, QR code, passkeys, and any other built-in methods must be completely suppressed.
• The approach must rely solely on cloud configuration (Conditional Access, external IdP federation, authentication strengths, etc.); no on-prem servers or physical security keys.
Acceptance criteria
• Demo with a freshly created test user showing the direct hand-off to Symania and successful token issuance.
• A reproducible configuration guide (screenshots or scripted steps) covering every Entra ID setting you touched.
• Confirmation that the solution stays compliant after tenant syncs or license changes.
If you have deep experience tweaking Entra ID’s federation options, authentication strengths, or preview features that let external OIDC override passwords, I’d like to see how you would implement and document it.
See attched diagram by microsoft. looks that their primary method is a must.
What has to happen
• At sign-in the user is redirected immediately to Symania’s OIDC page, no password screen or Microsoft second factors in between.
• Microsoft Authenticator, e-mail OTP, QR code, passkeys, and any other built-in methods must be completely suppressed.
• The approach must rely solely on cloud configuration (Conditional Access, external IdP federation, authentication strengths, etc.); no on-prem servers or physical security keys.
Acceptance criteria
• Demo with a freshly created test user showing the direct hand-off to Symania and successful token issuance.
• A reproducible configuration guide (screenshots or scripted steps) covering every Entra ID setting you touched.
• Confirmation that the solution stays compliant after tenant syncs or license changes.
If you have deep experience tweaking Entra ID’s federation options, authentication strengths, or preview features that let external OIDC override passwords, I’d like to see how you would implement and document it.
See attched diagram by microsoft. looks that their primary method is a must.
Related categories:
Azure
Compliance
OAuth
Documentation
Security
Cloud Security
API Integration
Microsoft 365