Administration
GuideSet up Microsoft Entra ID sign-in
Let your organization's members sign in to Volobox with Microsoft Entra ID, through the Microsoft 365 connection or your own app registration.
At the end of this guide your organization's members sign in to Volobox with their Microsoft Entra ID accounts. There are two ways to set it up: through the Microsoft 365 connection, with nothing to register in Entra, where your installation offers it (Volobox Cloud does), or with your own app registration, which is the only way on self-hosted installations. A Volobox administrator with the Account settings permission turns sign-in on; a Microsoft Entra administrator approves Volobox or creates the app registration.
Before you begin
- A Volobox account with Account settings. Connecting Microsoft 365 also needs Manage integrations.
- For the Microsoft 365 connection: someone in your Entra tenant with the Global Administrator, Privileged Role Administrator, Cloud Application Administrator or Application Administrator role, to approve Volobox. It does not have to be the Volobox administrator.
- For your own app registration: permission in Microsoft Entra to create an app registration and a client secret.
- Decide who may sign in. Sign-in is open to your organization's members as soon as it is on.
Warning: The Microsoft 365 connection never creates accounts
Before you turn sign-in on through the connection, create a Volobox account for everyone who should sign in, with the same email address as their Microsoft account.
Option 1: use the Microsoft 365 connection
Connect your organization
- Open Admin on the left activity rail, then Settings, and select the Integrations tab of Organization Settings.
- In the Microsoft 365 panel, select Connect Microsoft 365. Microsoft opens its approval page.
- Sign in with a work or school account of your organization that holds one of the Entra roles above, review the permissions, and approve. Approving turns on neither Microsoft sign-in nor Microsoft Teams.
- Microsoft asks you to sign in once more. This sign-in proves which organization you approved for.
- Back in Integrations, the panel shows Connected to your organization and its default domain.
Tip
If an Entra administrator already approved Volobox, use Already approved in Microsoft Entra? Finish connecting. It skips the approval page and asks you to sign in with a member account of that organization.
Turn on Microsoft sign-in
- In the Microsoft 365 panel, find Used for, then Microsoft Entra ID sign-in.
- Select Turn on Microsoft sign-in, or Switch to this connection when sign-in already runs on your own app registration.
- If Volobox asks you to confirm because people's existing Microsoft links would be removed, select Turn on or Switch. Removed links are rebuilt on each person's next Microsoft sign-in by matching their email address.
You can do the same in Organization Settings under Accounts, Sign-in: switch on Microsoft Entra ID, choose Configure, and under Connection choose Microsoft 365 connection.
With the connection, only members of the connected organization can sign in. Guest (B2B) accounts are refused, and a Microsoft email address is used to find an account only when its domain is one of the organization's verified domains.
Option 2: use your own app registration
-
In the Microsoft Entra admin center, create an app registration for accounts in this organizational directory only.
-
Add a Web platform, and copy the exact Redirect URI shown in the Volobox Microsoft Entra ID card into it.
-
Create a client secret and copy its value while Microsoft still shows it.
-
Make sure the ID token includes the user's email address. Add the optional
emailclaim when your directory does not issue one by default. -
In Volobox, open Organization Settings, then Accounts, Sign-in, External provider. Switch on Microsoft Entra ID, choose Configure, and choose Your own app registration under Connection when it is shown.
-
Enter the Authority, the Application (client) ID and the Client secret. The Authority uses your tenant ID:
Texthttps://login.microsoftonline.com/{tenant-id}/v2.0 -
Decide whether Create Volobox users on first Microsoft Entra ID sign-in is on. Keep it on to create accounts as people first sign in; turn it off when administrators create every account in advance.
-
Decide whether an existing Volobox account matched by email must confirm its Volobox password before the Microsoft sign-in is linked.
-
Save. Volobox checks the tenant's discovery document before it stores the configuration.
Note
The client secret is never shown after saving. Leave its field blank to keep the saved secret, and enter a new value only when you rotate it.
Control who can sign in
In Microsoft Entra, open the Volobox enterprise application, turn on Assignment required, and assign the users or groups that may use Volobox. People who are not assigned are refused by Microsoft before they reach Volobox.
Warning
Assign yourself before you connect, reconnect or finish connecting, or Microsoft refuses you too.
Once members sign in with Microsoft, you can turn off password sign-in for them under Accounts, Sign-in, General. It applies to workspace members only: customers and external collaborators always sign in to the Portal with their email address and password.
Check that it works
- Open a private browser window and go to the Volobox login page.
- Select Microsoft Entra ID and sign in with an existing account.
- With your own app registration and account creation on, also sign in once with a permitted first-time account.
Troubleshooting
| Symptom | Fix |
|---|---|
| Microsoft Entra ID is missing from the login page (Microsoft 365 connection) | Check that the provider is on, the Microsoft 365 panel shows Connected to your organization, and Used for, Microsoft Entra ID sign-in shows On. Needs confirmation means someone with Account settings must select Turn on Microsoft sign-in. |
| Microsoft Entra ID is missing from the login page (your own app registration) | Check that the provider is on and that Authority, client ID and client secret are all saved, then reload the login page. |
| Someone is told they have no Volobox account | The Microsoft 365 connection never creates accounts. Create their account with the same email as their Microsoft account, or correct the email on either side. |
| A guest account cannot sign in through the Microsoft 365 connection | Guests are refused by design. The person needs a member account in the connected organization. |
| Microsoft reports AADSTS50105 | Assignment required is on for the Volobox enterprise application. Assign the person in Microsoft Entra. |
| Save rejects the Authority | Use the tenant ID form shown above. common, organizations, another host, HTTP, custom ports, query strings and fragments are not accepted. |
| Microsoft says the redirect URI does not match | Copy the exact URI from the Volobox card again, and add it as a Web redirect, not a single-page application redirect. |
| A first-time user has no email claim | Add a valid email address to the directory account. With your own app registration, also configure the optional email ID-token claim. |