Microsoft Entra ID (formerly Azure Active Directory) supports SAML 2.0 single sign-on out of the box. Once it's configured, your team signs in to businesscards.io with their Microsoft 365 / company account.
SSO is available on the Pro plan and above. You'll be moving between the Entra admin center and your team settings on businesscards.io, so have both open.
What you need
- Entra ID admin rights (Application Administrator or Global Administrator).
- You're a team owner on businesscards.io.
- Your plan includes SSO (Pro or Enterprise).
Step 1: Get the SP metadata from businesscards.io
- Sign in to businesscards.io and open Settings → SSO.
- Note the ACS URL and the Entity ID. You'll paste these into Entra next.
Step 2: Create the Enterprise application in Entra
- Go to entra.microsoft.com and sign in as an admin.
- Navigate to Identity → Applications → Enterprise applications.
- Click New application, then Create your own application.
- Name it (e.g. "businesscards.io") and pick Integrate any other application you don't find in the gallery (Non-gallery).
- Click Create.
Step 3: Configure SAML
- In your new app, open Single sign-on in the sidebar.
- Pick SAML as the sign-on method.
- In Basic SAML Configuration, click Edit and enter:
- Identifier (Entity ID): the Entity ID from businesscards.io.
- Reply URL (Assertion Consumer Service URL): the ACS URL from businesscards.io.
- Save.
- In Attributes & Claims, verify that
nameidentifier is set to the user's email (typically user.mail or user.userprincipalname).
- In the SAML Certificates section, download the Federation Metadata XML.
Step 4: Plug Entra into businesscards.io
- Back on businesscards.io's Settings → SSO, paste the Federation Metadata XML (or paste the metadata URL).
- Save.
- Sign out and test SSO with a test user (not your owner account).
Step 5: Assign users in Entra
In the app's Users and groups tab, add the users or groups who should have access. Anyone not assigned can't sign in via SSO.
Troubleshooting
- AADSTS50105: the user isn't assigned to the app in Entra. Assign them under Users and groups.
- Email mismatch: Entra's
nameidentifier claim must map to the user's email. If your tenant uses different fields for sign-in, adjust the claim mapping in Entra.
- Test in private browsing: existing sign-in sessions can confuse the test. A new private window catches misconfigurations faster.
- Keep one owner with password sign-in: so you can always get back in if SSO breaks.
Need a hand? Email support@businesscards.io with the team name and the error you're seeing.