Vendor asks SAML or OIDC, unsure which to pick
SAML is older, XML-based, widely supported. OIDC is newer, JSON, better for mobile and SPAs. Functionally equivalent for SSO.
Try this first
- 1Check which option identity provider supports well
- 2SAML: exchange metadata XML
- 3OIDC: exchange client ID and secret
- 4Test login as test user before rollout
When to bring us in
Vendor only does SAML but IdP only OIDC: ask about bridge.
See also
- New hire has an account but cannot reach Outlook or TeamsAn M365 account without a license is an empty shell. Assigning takes a few clicks, but picking the right plan pays off long-term.
- Employee left, but their email must be retainedPulling the license straight away starts a 30-day timer on the mailbox. The right route keeps access to the mail without paying for the license.
- We pay for licenses nobody usesBetween leavers, duplicate plans, and test accounts there is often 10-20% wasted license spend. A usage report exposes it fast.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.