Set up Microsoft
One guided page sets up one or more Microsoft connectors at once: Microsoft Graph, Azure, Defender for Endpoint, Exchange Online, Purview, SharePoint Admin, Teams Admin and Power Platform Admin. Every…
Written By Christopher Scaminaci
Last updated About 3 hours ago
One guided page sets up one or more Microsoft connectors at once: Microsoft Graph, Azure, Defender for Endpoint, Exchange Online, Purview, SharePoint Admin, Teams Admin and Power Platform Admin. Every connector you tick uses the same Microsoft app, so no two cards can end up on different apps.
Open Connectors, then Set up Microsoft. Only an owner or an administrator of your StackJack organization can use it. You can stop at any point and open it again: it shows where you stopped and checks everything again.
The five steps
- Pick connectors. Tick the Microsoft connectors your plan includes. Connectors that are already connected are ticked. A connector not in your plan shows Not in your plan and an Add this connector link. If your organization has a subscription on the Billing page (the Your subscription card), the link opens that page with the Add a connector dialog open and that connector chosen. Review the price and select Confirm and pay; nothing is added before that. Otherwise the link opens that connector's setup form on the Connectors page. Connect with Microsoft starts it on the Free plan and signs it in, and Upgrade on its card buys a paid plan later. Come back to the wizard afterwards: the connector is then in your plan.
- Pick the app. Use StackJack's app if you have no Partner Center or GDAP. Use your own app otherwise. The wizard creates it in your partner directory (one sign-in by a Global Administrator or Application Administrator), or reads an app you bring and offers Fix my app for each problem it finds. StackJack names the app "StackJack partner app", and if creating it stops, step 2 says why and offers Try again or Use my existing app. Step 2 lists what is wrong with your app. Fix everything StackJack can fix repairs all of it in one Microsoft sign-in; if the repair uncovers more, press it again. A certificate you upload by hand has its own Fix my app button for checking afterwards. Step 2 always offers Check my app, which reads the app again with your sign-in and repairs nothing. Use it after you restore a deleted app or fix something in Microsoft by hand. If StackJack has not checked your app in the last day, step 2 does not let you go on until you press it. The AI Governance service account is not part of the connectors: step 2 says so, links to the page where it signs in, and does not stop you. If a ticked connector needs permissions your app does not have yet, step 2 offers Add the ticked connectors to my app. Microsoft Graph, for example, now also needs the security, Purview and Copilot admin permissions, so an app made earlier shows this button. Nothing is removed in Microsoft. If your app was deleted in Microsoft, step 2 says so and offers Use my existing app, so you can bring another app in its place. StackJack keeps the certificate it made, so you can upload it to the other app. The service account signs out, because its sign-in belonged to the old app, and the customers get their consent again in step 4.
- Grant and sign in. Each connector signs in as you, on the one app. A connector that is on a different app shows Move to the one app. Nothing moves until you press it.
- Customers. On your own app one run consents every ticked connector in each GDAP customer, or in the customers you pick. A run stops on a Microsoft refusal or three faults in a row and carries on where it stopped. The result counts the customers an earlier run already handled, and it names each customer that failed with Microsoft's reason. When a run finishes, Next continues even if Microsoft refused some customers. A common cause is a missing GDAP role in that customer. Next stays off before the first run and while customers are still left to do, for example after a run that stopped. On StackJack's app there is no run, and nothing on this step is required. Your sign-in at step 3 covers Microsoft Graph and Azure in your own directory. The other connectors need an administrator's approval in each directory you use them in, your own included: enter the tenant ID or domain, press Make consent links and send each link to that administrator. StackJack cannot see who opened a link. The Exchange Online and Purview links ask for every permission the app lists, because Microsoft refuses a link that names their permission (AADSTS650053) until it was granted once; a directory without one of the app's services refuses them (AADSTS650052), and the sentence under each link says so.
- Checklist. One row per connector: the app, your access, the sign-in, the customers and what is still to do. A row is ready only when all of it is checked just now. Each customer Microsoft refused is listed under its connector with Microsoft's reason, and that row is not ready. Fix the cause (often the GDAP role in that customer), then press Run again, which opens step 4.
When StackJack needs more permissions
StackJack adds features over time, and some of them need more access than your own Microsoft app was given when it was made. StackJack tells you in two places when your app falls behind:
- A banner on every page of the Portal, for owners and administrators. It names what is missing, for example "Your Microsoft app needs new permissions for StackJack features: Microsoft Graph (Security and Purview through Graph)", and has an Open Set up Microsoft button. People who cannot change the app do not see it. It goes away a few minutes after the app has what it needs.
- One email to the account owner each time what is missing changes. StackJack's daily check of your app sends it, never a page you are looking at, and it does not repeat the same email every day. If you fix everything and a later feature needs more, you get a new email.
To add the access, open Set up Microsoft and go to step 2. If a ticked connector needs permissions the app does not have yet, press Add the ticked connectors to my app. If step 2 instead lists a problem that says a permission is missing or not agreed to, press Fix everything StackJack can fix. One administrator of your partner directory signs in once to approve the change. Nothing is removed in Microsoft.
The banner and the email cover the own app that you made or brought in step 2, while you use it. They do not cover StackJack's own app, which StackJack keeps up to date. They also do not cover a Microsoft card that signs in with its own client ID and secret and was never set up as the app in step 2. For that card, check the permissions against the provisioning script's current list.
Good to know
- Purview content search needs its own consent in each customer, and the wizard cannot see it. Only the content search and search action tools need it, so a Purview row can be ready without it and keeps a note about it.
- A customer whose directory lacks a service is skipped with Microsoft's reason. That is not a failure.
- Microsoft stops a customer consent link with AADSTS650052. The directory does not have a service the link asks for, and Microsoft's message names the service by its application ID. Each link asks only for its own connector's permissions, so the service is usually that connector's own, and the directory cannot use that connector. The Exchange Online, Purview and Purview content search links are the exceptions: they ask for every permission on the app, so the directory needs every service the app lists. If the ID is
4990cffe-04e8-4e8b-808a-1175604b879f, it is the Microsoft Partner permission (user_impersonation). With StackJack's app or your own app, make fresh consent links and send them. Only the Exchange Online, Purview and Purview content search links on your own app still need the removal: remove it from the API permissions of your app registration in Microsoft Entra, or download the current provisioning script again and run it with-AppIdset to your app's application (client) ID. A re-run adds a new client secret, replaces the permission list with the tier you pass (Full if you pass none), and replaces the display name with-DisplayName, so pass the app's current name. Do not remove Microsoft Partner Center; it is a different permission. The run in step 4 does not use a consent link, so use it for your GDAP customers where you can. If the message names another service, contact support. - Microsoft Graph, Teams Admin and SharePoint Admin also ask your app for the audit log permission, because AI Governance uses it to say who changed a setting that drifted. An app made before this asks for it through Add the ticked connectors to my app.
- AI Governance standards set and watch settings through the Teams Admin, SharePoint Admin, Purview, Exchange Online, Power Platform and Azure connections, as well as Microsoft Graph. They use the organization's connection, signed in here, inside each client's directory.
- In each customer you need the AdminAgents group and Application Administrator or Cloud Application Administrator in your GDAP relationship.
- Your Microsoft cards also show the app they use. If the connectors you ticked use more than one app, each card says so and links the wizard. A connector you did not tick does not count.
- The provisioning script registers an app without the wizard, for people who prefer a shell or a runbook.
Was this helpful?
More in Connector basics
How Connectors WorkActivating a Connector (Plans & Tiers)Connecting a ConnectorValidation at SaveStill need help? Ask the team