Skip to main content
For MSPs

The Microsoft partner app and its health

To read and change your clients' Microsoft 365 settings, deploy and manage uses one Microsoft app that you own, the Microsoft partner app. It also uses one service account, a Microsoft account that…

Written By Christopher Scaminaci

Last updated 4 days ago

To read and change your clients' Microsoft 365 settings, deploy and manage uses one Microsoft app that you own, the Microsoft partner app. It also uses one service account, a Microsoft account that runs the work nobody is sitting at: drift checks, scheduled standards and automatic approvals. The Microsoft partner app tab is the health card for both. It tells you in one sentence per problem what is wrong, and where to fix it.

At a glance

  • What it does: shows whether the app and the service account are healthy, and signs the service account in.
  • Plan: Pro and above.
  • Who: an Administrator of your whole organization.
  • Where: AI Governance → Deploy and manage → Microsoft partner app.
  • Needs: the app, made in the Microsoft setup wizard on the Connectors page.

The setup rail

Until deploy and manage is fully set up, an Administrator of your whole organization sees Set up deploy and manage at the top of Clients and standards, Drift and Deploy. Its five steps sit on one line, in the order you do them. One card under the line holds the step to do now, with where it stands, why it is needed and its one button:

  1. Microsoft partner app. Done when the app is made and its setup finished. The button opens the Microsoft setup wizard.
  2. Service account. Done when the service account is signed in. The button signs it in.
  3. Clients consented (n of m). Done when every client the consent step of the wizard reached allows the app with its current permissions. m counts the clients the consent step reached. A client whose directory has none of the services is not counted, because there is nothing to consent. n counts the ones where the consent landed with the app's current permissions. The button opens the wizard, where you run the consent step.
  4. A standard published. The button opens Standards.
  5. A standard at a client. The button opens Clients and standards.

A done step says Done. A step after the one to do now waits and says "Opens after step N". On the page that does a step itself, the card has no button and says what to do there. The rail reads only what StackJack stored. It never asks Microsoft anything when a page opens, so a change you just made in Microsoft shows after the next check. The rail goes away when all five steps are done.

Make or repair the app

The card never repairs the app itself. The app is made, repaired and changed in one place: the Microsoft setup wizard. When the card says there is no app, or shows a problem, it links to the wizard. Open it from the card, or from Connectors.

The card

The app shows one of these states:

StateWhat it means
HealthyNothing is wrong.
Needs attentionA warning. Nothing has stopped yet.
Broken: unattended work is stoppedA problem stops drift checks, scheduled standards and automatic approvals until it is fixed.
Not checked yetThe app has not been checked. Select Check now.

StackJack checks every day and before every consent run. Check now asks again at once, so you can see the result of a fix.

Each problem is one sentence. It says whether unattended work waits until this is fixed or it is a warning: nothing stopped yet, and it has a link Fix it in the wizard. The problems StackJack looks for are:

  • The app is missing, or is not set to work for other directories.
  • A redirect address is missing.
  • The app has no certificate, or the certificate expired, or it ends in 30 days or in 7 days.
  • A permission is missing, or no administrator of your directory has agreed to it.
  • A Partner Center permission is missing or not agreed to.
  • The app's service entry is missing in your directory.
  • The service account is not signed in, or its sign-in stopped working, or its sign-in did not show a second factor.
  • The service account cannot read the audit log at your clients, so StackJack cannot say who changed a setting. This is a warning and never stops anything. It shows when a drift check could not read the audit log at any client for lack of a role, and goes away when one client reads it. Give the service account Reports Reader, and Compliance Administrator for Teams and SharePoint changes, in your delegated access to each client.

When StackJack needs more permissions

StackJack adds features over time, and some need more Microsoft access than your app was given when it was made. You do not have to open this card to find out. StackJack tells you in two ways:

  • A banner on every page of the Portal, for owners and administrators, that names what is missing and has an Open Set up Microsoft button.
  • One email to the account owner each time what is missing changes. The daily check sends it. It is not repeated every day, and a new email comes only when something new is missing or when a fixed gap comes back.

The banner and the email read the same two things this card shows: a connector you ticked in the wizard that needs a permission the app does not hold yet, and a problem that says a permission is missing or not agreed to. A certificate, the service account and the other problems on this card do not raise the banner or the email.

To fix it, open the Microsoft setup wizard, go to step 2 and press Add the ticked connectors to my app, or Fix everything StackJack can fix when the list shows a permission problem. One administrator of your partner directory signs in once to approve it. The banner goes away a few minutes after the app has what it needs.

The service account

The service account is the Microsoft account that signs in for the unattended work. Changes it makes also show under its name in your client's Microsoft logs. StackJack's own record names the person or the rule that approved each change.

The card says one of:

  • No service account is signed in yet. Unattended work waits until one is.
  • Signed in as the account, and since when it has been kept alive.
  • The service account's sign-in stopped working, so unattended work is stopped. Sign it in again.
  • The service account is signed out.

The role it needs to say who changed a setting

When a client's setting drifts, StackJack reads the client's Microsoft audit log as the service account to say who changed it (see Drift). The log is read only by an account that holds a role for it. Give the service account Reports Reader in your delegated access to each client. For Teams and SharePoint changes it also needs Compliance Administrator, which Microsoft's own pages name as a role that may search the audit log. The Microsoft setup wizard asks your app for the audit log permission for these connectors. Nothing stops without the roles: the drift page only shows that the name cannot be read, and which role adds it.

Sign the service account in

  1. Select Sign the service account in, or Sign the service account in again.
  2. Microsoft asks you to sign in. Use the Microsoft account you want StackJack to use, with its second factor. The account must belong to your partner directory.
  3. You come back to the card. It shows The service account is signed in. Unattended work can run again.

StackJack keeps the account signed in, and tells you if it stops working. If the sign-in did not show a second factor, the card says so and asks you to sign in again with one. A sign-in whose result says nothing about a second factor raises no warning.

Only an Administrator of your whole organization can sign the account in, and it must be the same person who started the sign-in, on the same address, within ten minutes. A sign-in link can be used one time.

If you come back with a message instead, it is one of these:

MessageWhat to do
The sign-in was cancelled or refusedTry again, and sign in with the account you want StackJack to use.
That sign-in took too long or was already usedStart it again.
Only an administrator of your whole organization can sign the service account inAsk one, or sign in as the person who started it.
The Microsoft partner app is not switched on yetIt is a platform setting. Contact StackJack support.
StackJack could not use this web address for the sign-inOpen the Portal on its normal address and try again.
Microsoft did not send back what StackJack needsStart the sign-in again.
StackJack could not finish the sign-inTry again in a moment. If it keeps failing, contact support.

Use it from your AI

aigov_get_partner_app_health reads the same card. To repair the app, open the Microsoft setup wizard in the Portal; to sign the account in again, open the card. Both need an interactive Microsoft sign-in that a tool cannot do, so the tool answers with a link to each. It says a sign-in showed no second factor only when it did, and says nothing about a second factor otherwise. See Use AI Governance from your AI.