Microsoft Entra ID (vastframe cloud)
Overview
A vastframe cloud organization can sign people in with your company's Microsoft 365 accounts. You register an app in your own Entra ID tenant, paste three values into Admin › Sign-in, and test it. Only tokens issued by your tenant are accepted.
Prerequisites
- Org Admin in vastframe.
- An Entra ID role that can create app registrations (for example Application Administrator).
- People who will sign in are members of your vastframe organization, or you've verified your email domain and allowed anyone on it to join.
Permissions
| Item | Value |
|---|---|
| Platform | Web |
| Flow | Authorization code with PKCE |
| Scopes requested | openid profile email |
| Graph API permissions | None beyond sign-in |
Setup steps
Step 1: Copy the redirect URI
- In vastframe, open Admin › Sign-in.
- Select Microsoft Entra ID.
- Copy the redirect URI shown in the box. It looks like
https://auth.<your-org-domain>/callback, for examplehttps://auth.acme.vastframe.app/callback.
Step 2: Register the app in Entra
- In the Microsoft Entra admin center, go to Entra ID › App registrations › New registration.
- Name it, for example "vastframe".
- Under Supported account types, choose accounts in this organizational directory only.
- Under Redirect URI, choose Web and paste the URI from step 1.
- Select Register.
- On the app's Overview, copy the Application (client) ID and the Directory (tenant) ID.
- Go to Certificates & secrets › New client secret, create one, and copy its Value (not the secret ID).
vastframe matches people by email. It uses the email claim, falling back to preferred_username. If your users' sign-in names differ from their email addresses, add the email optional claim under Token configuration.
Step 3: Turn it on in vastframe
- Back in Admin › Sign-in with Microsoft Entra ID selected, fill in:
- Directory (tenant) ID: the GUID from step 2.6.
- Application (client) ID: from step 2.6.
- Client secret: the value from step 2.7.
- Select Test connection. vastframe fetches your tenant's OpenID configuration and shows "Reached https://login.microsoftonline.com/…/v2.0".
- Select Save and turn on.
After saving, try signing in from a private window before you close the tab. If something is wrong, Org Admins can still use emergency access.
Verify
- In a private window, open
https://console.<your-org-domain>. You should be redirected to Microsoft sign-in. - Sign in as a member. You land in the console.
- Sign in as someone who isn't a member. They should see "Not a member yet".
- Check Admin › Audit log for a
sign-in.updateevent.
The client secret is never shown again. To keep it when you edit other fields, leave Client secret blank ("Saved (leave blank to keep)").
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| "The Entra tenant id is a GUID" | The directory ID is wrong | Copy it from Entra admin center › Overview › Tenant ID. |
| "Connection failed" on Test connection | The tenant ID doesn't exist or isn't reachable | Check the ID. |
AADSTS50011 on sign-in | Redirect URI mismatch | Paste the exact URI from Admin › Sign-in, as a Web platform URI. |
AADSTS7000215 invalid client secret | The secret ID was pasted instead of the value, or it expired | Create a new secret and paste its value. |
| "Not a member yet" | The person isn't in Admin › People, or their token's email/preferred_username doesn't match the address there | Add them (or fix the address), or verify your domain and allow anyone to join. |
| "Token is from tenant …" | Someone from another Entra tenant | Expected: only your tenant is accepted. |
Client secrets expire. Put a reminder in your calendar before the expiry date and update the secret in Admin › Sign-in.