Require Microsoft sign-in
The Sign-in tab on the Organization page lets an owner require everyone in the organization to sign in with the organization's Microsoft account. With that in place, a leaked password or a forwarded sign-in link cannot get anyone in.
Not seeing the tab? Require Microsoft sign-in is turned on for an organization by Structured, and by default only organization owners can open the tab. To have it turned on, contact support.
The three stages
- Off - everyone signs in as they do today: Microsoft, Google, an emailed sign-in link or a password. This is where every organization starts.
- Report only - nothing changes for anyone. Sign-ins that would have been refused if Microsoft were required are recorded, so you can see who would be affected before you commit.
- Enforce - everyone must sign in with the organization's Microsoft account. Other sign-in methods are refused, except emailed sign-in links for the people on the break-glass list.
Start with Report only, read Who would be locked out, fix what it shows, and only then move to Enforce.
Allow Google sign-in
While sign-in is enforced, you can also let people sign in with a Google account. It is off by default. Leave it off to require Microsoft alone. Switching it off while sign-in is enforced is treated like enforcing again: everyone is signed out (see What happens when you enforce).
Who would be locked out
The page lists the people who could not sign in if you enforced right now, with the reason for each:
- Has never signed in with Microsoft - they use another method today.
- Directory not yet confirmed - they have a Microsoft identity, but we have not seen which Microsoft directory it belongs to, so we cannot tell whether it is yours. They may be fine. Ask them to sign in with Microsoft once, then press Refresh.
- Signs in with a Microsoft account from a different directory - their account belongs to another Microsoft directory, not yours.
People who also use Google, and people already on the break-glass list, are marked. The list is a preview and changes as people sign in.
The lockout guard
Enforce is refused unless both of these are true, so that an owner cannot lock themselves and everyone else out:
- Your organization's Microsoft directory has been confirmed. Structured confirms it for you; contact support if the tab says it has not been.
- You are signed in with your organization's Microsoft account yourself. If you signed in another way, sign out and sign back in with Microsoft first. Signing in with an emailed link does not count.
When the guard refuses, the page shows the reason in the confirmation dialog and nothing changes.
Break-glass list
Up to five people can be kept on the break-glass list. When Microsoft sign-in is required, they can still sign in with an emailed sign-in link. Use it for the case where Microsoft is unavailable or someone cannot use a Microsoft account, and keep it short. Only active members of your organization can be on it.
If you remove someone from the list while sign-in is enforced, their sessions and add-in keys end. That includes you, if you remove yourself: sign back in with Microsoft afterwards.
What happens when you enforce
Moving to Enforce takes effect immediately:
- Everyone's sessions end. Everyone has to sign in again, with Microsoft.
- Add-in keys are revoked. People sign in again in Revit, AutoCAD and the other add-ins.
- AI app connections are revoked. People reconnect their AI apps after signing in with Microsoft.
- Emailed sign-in links that are already open stop working.
- Your own session stays signed in, because you have just proved yourself through Microsoft.
The page asks you to confirm before it does any of this.
Getting back
You can move the stage back to Off or Report only yourself at any time, from the same tab. If nobody in the organization can sign in to do it, contact Structured support: staff can reset your organization to Off. A staff reset does not sign anyone out; people can then use their usual sign-in method again.
After Structured switches the feature off and on again
In an emergency, Structured can switch Require Microsoft sign-in off for every organization at once. While it is off, everyone signs in as they did before, and sign-ins made in that time stay valid when it is switched back on. If your organization was on Enforce, move it to Report only and then back to Enforce once the feature is back: that signs everyone out again, so only Microsoft sign-ins remain. Structured tells owners when this is needed.
Who can change it
By default, only organization owners can open the tab and change the policy. An owner can let others: on the Settings tab of the Organization page, open Permissions, find Who can change the sign-in policy and tick the roles that should have it. Because a wrong change can lock people out, think carefully before ticking it for anyone else.
Every change is recorded in the Audit log.
See How access works for how roles and permissions fit together.