Skip to main content

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​

ItemValue
PlatformWeb
FlowAuthorization code with PKCE
Scopes requestedopenid profile email
Graph API permissionsNone beyond sign-in

Setup steps​

Step 1: Copy the redirect URI​

  1. In vastframe, open Admin › Sign-in.
  2. Select Microsoft Entra ID.
  3. Copy the redirect URI shown in the box. It looks like https://auth.<your-org-domain>/callback, for example https://auth.acme.vastframe.app/callback.

Step 2: Register the app in Entra​

  1. In the Microsoft Entra admin center, go to Entra ID › App registrations › New registration.
  2. Name it, for example "vastframe".
  3. Under Supported account types, choose accounts in this organizational directory only.
  4. Under Redirect URI, choose Web and paste the URI from step 1.
  5. Select Register.
  6. On the app's Overview, copy the Application (client) ID and the Directory (tenant) ID.
  7. Go to Certificates & secrets › New client secret, create one, and copy its Value (not the secret ID).
Make sure tokens carry the email

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​

  1. 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.
  2. Select Test connection. vastframe fetches your tenant's OpenID configuration and shows "Reached https://login.microsoftonline.com/…/v2.0".
  3. Select Save and turn on.
Keep this tab open

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​

  1. In a private window, open https://console.<your-org-domain>. You should be redirected to Microsoft sign-in.
  2. Sign in as a member. You land in the console.
  3. Sign in as someone who isn't a member. They should see "Not a member yet".
  4. Check Admin › Audit log for a sign-in.update event.

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​

SymptomCauseFix
"The Entra tenant id is a GUID"The directory ID is wrongCopy it from Entra admin center › Overview › Tenant ID.
"Connection failed" on Test connectionThe tenant ID doesn't exist or isn't reachableCheck the ID.
AADSTS50011 on sign-inRedirect URI mismatchPaste the exact URI from Admin › Sign-in, as a Web platform URI.
AADSTS7000215 invalid client secretThe secret ID was pasted instead of the value, or it expiredCreate 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 thereAdd them (or fix the address), or verify your domain and allow anyone to join.
"Token is from tenant …"Someone from another Entra tenantExpected: 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.

Was this page helpful?