HowToFixMe
Entra Identity

Conditional Access SSO SAML AADSTS50105 issuer mismatch: Fix

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
BrandConditional Access
FamilyEntra Identity
CategoryMicrosoft
Guide typeProblem Fix
Skill levelIntermediate

What's happening on your Conditional Access

You hit SSO SAML AADSTS50105 issuer mismatch on a Conditional Access device in the Entra Identity family. This sits in the most-reported issue list for Conditional Access in 2026 across community forums and vendor support, meaning the recovery path is mostly known.

Fast triage (5 minutes)

  1. service restart: stop the resource cleanly for 60 seconds, then power on. About 30% of Conditional Access "SSO SAML AADSTS50105 issuer mismatch" reports clear here.
  2. Check status: any indicator service health indicators, dashboard alerts, or display codes on the Conditional Access unit right now? Note them: they decide which branch to take below.
  3. Check release notes: is this device on the latest service version / OS update from Conditional Access? An advisory for "SSO SAML AADSTS50105 issuer mismatch" may already be published.
  4. Try a clean test: a known-good cable / network / account isolates the device from external causes.
  5. Capture the exact symptom string, vendor TAC will ask for it verbatim.

Step-by-step fix for Conditional Access SSO SAML AADSTS50105 issuer mismatch

  1. Confirm scope. Is this only on the one device, or fleet-wide? If fleet-wide, treat as a release / config / network issue, not a hardware fault.
  2. Apply the safe fix first.

- On Conditional Access for "SSO SAML AADSTS50105 issuer mismatch", that usually means: soft reset → service version update from the Conditional Access official portal → re-pair the device with its management tool / app.

  1. Targeted diagnostics. Use the Conditional Access-specific diagnostic mode (most Conditional Access Entra Identity devices have one). It surfaces the exact subsystem reporting the fault, which speeds up parts ordering or escalation.
  2. Controlled hard reset (only if soft fix fails). Back up settings + data first. Then tenant reset following the Conditional Access user manual for your model. Re-enrol from scratch.
  3. Validate. Reproduce the original trigger to confirm the fix held.
  4. Document. Log what worked. If it returns, you've got a faster path next time.

Escalation path for Conditional Access

Avoid recurrence

Frequently asked questions

How long should the recovery / setup take?

For most Conditional Access Entra Identity cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every Conditional Access model?

The procedure reflects current Conditional Access behaviour. Menu paths shift between service version generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. Conditional Access doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Conditional Access support coverage?

Standard operation per the user manual + applying official service version updates does NOT void support coverage. Opening managed services, third-party repair, or unauthorised modifications can void support coverage, check before going further.

Related guides worth a look while you sort this one out:

References

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

What changed recently?

Fault diagnosis on a Conditional device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the Conditional device fix goes cleanly:

How to confirm it's actually fixed

On a Conditional device, the test is rarely "reboot and see". Use this list:

Escalation guide

For a Conditional device, the right escalation depends on impact:

More frequently asked questions

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Are there safer alternatives for non-technical users?

Yes. the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (service version updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

Can I roll this back if something breaks?

Yes for software-level changes (service version rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Field notes from real Entra Identity incidents

When I work on Conditional Access SSO SAML AADSTS50105 issuer mismatch: Fix the rhythm I lean on is the one I have built over years of these tickets. Conditional Access What-If is the only safe way to test a policy change; deploying first and watching the support queue light up is the dangerous way. The Microsoft Graph PowerShell SDK is the path forward for Entra automation; the legacy AzureAD module is on a timer. Sign-in logs are the single highest-signal Entra surface, every failure has a specific status code and the doc page for that code is one search away.

Tools I actually reach for

For Conditional Access SSO SAML AADSTS50105 issuer mismatch: Fix on Conditional Access the cheapest signal I can land usually comes from Audit logs, then Entra ID Diagnostics & Logs, Sign-in logs, Conditional Access What-If tool, AzureAD module (legacy, deprecation pending) when Audit logs cannot see the layer the fault sits in, and Microsoft Graph PowerShell SDK for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark Conditional Access SSO SAML AADSTS50105 issuer mismatch: Fix resolved on a Conditional Access unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

Get-MgConditionalAccessPolicy | Select-Object DisplayName,State

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Connect-MgGraph -Scopes 'AuditLog.Read.All','Directory.Read.All'

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Get-MgAuditLogSignIn -Top 25 -Filter "createdDateTime gt 2026-05-01T00:00:00Z"

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Entra > Diagnose and solve problems > run the relevant playbook

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Entra Identity detail, the disambiguation order I lean on is stable. I usually start at learn.microsoft.com/entra for the ground-truth view on Entra Identity. I usually start at techcommunity.microsoft.com/category/azure-active-directory for the ground-truth view on Entra Identity. I usually start at azure.microsoft.com/updates for the ground-truth view on Entra Identity. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Conditional Access SSO SAML AADSTS50105 issuer mismatch: Fix have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Conditional Access unit, not things I read about. Sign-in logs are the single highest-signal Entra surface: every failure has a specific status code and the doc page for that code is one search away. Conditional Access What-If is the only safe way to test a policy change; deploying first and watching the support queue light up is the dangerous way. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand Conditional Access SSO SAML AADSTS50105 issuer mismatch: Fix off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Conditional Access on the Entra Identity family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For Conditional Access SSO SAML AADSTS50105 issuer mismatch: Fix on a Conditional Access unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.