My first steps
Create a Diggle
Question types
Present live
Invite participants
Results & Reports
Collaborate with others
AI - Diggle Buddy
Company Workspace
Account and settings
GDPR
Security
API & Integrations
FAQ & Troubleshooting
Table of Contents
Microsoft Entra SSO
Microsoft Entra SSO authenticates users; SCIM provisioning manages workspace access. They are separate capabilities.
Before you start
Ask your workspace administrator to confirm that Microsoft sign-in is available for your organization and that your Diggle workspace access is ready. Use the intended work Microsoft account and keep access to your Diggle account’s email inbox. Workspace invitations must be completed separately when prompted.
For an administrator rollout, coordinate tenant approval and the supported sign-in configuration with Diggle. Enabling SCIM or creating its Enterprise Application does not by itself configure SSO.
Sign in for the first time
- Open the Diggle login page and select Sign in with Microsoft.
- Choose your work account and complete your organization’s Microsoft authentication steps.
- If Diggle asks to link an existing account, prove ownership using your Diggle password or the email login code offered in the linking flow. Your Microsoft password is not your Diggle password.
- If prompted to Continue with email, complete Diggle signup and activate the account using the email link, then return to Microsoft sign-in and complete account linking.
- Complete any pending workspace invitation and verify that the correct workspace is available.
After linking, use the same Microsoft identity for later sign-ins. If the Microsoft account cannot be matched to your existing Diggle email, contact Diggle rather than creating a second account to work around the problem.
Account linking
Microsoft sign-in is linked as an external identity to a global Diggle account. A matching Microsoft email or principal alone is not permanent proof of account ownership. Existing Diggle users may need to prove ownership through the supported account-linking flow.
New users follow Diggle’s supported signup, activation and linking flow when required. A SCIM-created account does not itself prove ownership for Microsoft sign-in. A pending workspace invitation must still be accepted through its supported flow.
Later sign-ins and profile changes
After legitimate linking, the established Microsoft identity identifies the same Diggle account even if the provider’s mutable email or display name changes. Those profile changes do not automatically rewrite all global Diggle account data.
Access is evaluated separately
Successful SSO does not restore a SCIM-deactivated membership, clear a local Diggle block, recreate private project access or restore a cancelled personal paid plan. Resolve workspace access with the workspace admin and provisioning source.
Troubleshooting
| Problem | What to do |
|---|---|
| Microsoft sign-in is unavailable | Ask your workspace administrator or Diggle to confirm availability and the intended tenant configuration. |
| Microsoft requests administrator approval | Ask your Entra administrator to review the application approval request according to your organization’s policy. |
| Diggle requests account ownership proof | Complete the offered Diggle password or email-code step. A matching Microsoft email or a SCIM-created account does not replace this proof. |
| Sign-in succeeds but the workspace is missing | Check invitation acceptance and workspace membership with the workspace administrator. For SCIM-managed access, check source activity and any local block. |
| The linking attempt expired or was interrupted | Start again from the Diggle login page. If it repeats, contact Diggle with the time and visible error, without passwords, tokens or login codes. |