Skip to main content
For MSPs

Drift

Drift is a setting that no longer holds the value its standard asks for. StackJack reads the client again and again and shows each difference in words: what the client holds now, what the standard…

Written By Christopher Scaminaci

Last updated 4 days ago

Drift is a setting that no longer holds the value its standard asks for. StackJack reads the client again and again and shows each difference in words: what the client holds now, what the standard asks for, since when, and what StackJack did about it. With enforcement on, StackJack can put a setting back. You can also put one back now, or accept a difference with a reason and an end date.

At a glance

  • What it does: shows where a client differs from its standards, and keeps it on them if you ask.
  • Plan: Pro and above.
  • Who: any role with access to the client can look. To accept a difference, end an exception, resume enforcement or change enforcement, a person needs Apply changes for Turning enforcement on or off at that client. Check now and Put back now need Request changes for Drift fixes. An Administrator of your whole organization has all of it everywhere.
  • Where: AI Governance → Deploy and manage → Drift. To see every client at once, open Clients and standards. See Deploy and manage.
  • Needs: a standard added to the client, and a connection that can read it.

When the client has no standard

The page says No standard at this client yet and offers Add a standard. It never shows a green tick for a client that has nothing to compare. Check now is off, and its tooltip says why. While no standard is published yet, Add a standard is off too: its tooltip says "Opens after step 4 of the setup", and "Finish step 4 first." sits beside it. When a standard is added and no check has run, the page says Not checked yet.

What the page shows

  • The top of the page. The client's name and Check now. A short line beside the button says how long ago the last check was, such as "Checked 12 minutes ago." or "Not checked yet.". StackJack checks every few hours. Select Check now to ask for a new check. If one is already waiting, or one ran a moment ago, Check now is off and the line says "A check is waiting." or "A check ran a moment ago.". The exact time of the last check and of the next one are under the settings table.
  • Five tiles. Match, Differ, Accepted, Could not read, and Put back in 30 days.
  • One table of settings. Use Show to look at the settings that differ, the accepted ones, the ones StackJack could not read, the ones that match, or all of them. When something differs, the table starts on the differences.
ColumnWhat it says
SettingThe setting, its platform and its state. Under them, for a setting that differs, who changed it when StackJack can tell: Changed by Ada Admin, at 09:14 UTC. The section Who changed it below says more.
Now and Should beWhat the client holds and what the standard asks for, one line for each member of the value, such as "Copilot in meetings: On, with transcript". Both use the setting's own labels. For a Claude, OpenAI, GitHub Copilot or Google setting, StackJack reads the whole list, so Now says how many it found, such as "Users: 120, Invites: 3". A member that differs between the two is marked.
SinceHow long the setting has differed, such as "3 days".
What StackJack didPut back at 09:14 UTC, Waiting for approval with a link to the run, Being put back now, or Not put back: and the reason.

A setting's value is always in words. A setting that holds people or groups shows a count, such as "3 people". An id, an address or a sign-in name is never shown.

A setting StackJack could not read is not counted as drift, and StackJack changes nothing in it. A check reads each platform through the connection that a plan or a run at that client last used, so a platform no plan has used at the client reads as could not read until one does. The same happens after the client's Microsoft directory is disconnected or linked again: StackJack never reads a directory the client no longer holds, so plan the standard again. The row says why and what to fix, for example "StackJack's service account is not signed in to Microsoft. Sign it in on the Microsoft partner app page."

Who changed it

For a Microsoft setting that matched at the last check and differs now, StackJack asks the client's Microsoft audit log who changed it and when. It reads the log as your service account, once per client at each check, and shows the answer under the setting: Changed by Ada Admin, at 09:14 UTC.

  • Who sees the name. Only a person who may already see names: an Administrator, or a person whose access has Sees names, in an organization whose name setting shows names. Everyone else with access to the client reads Changed in the client's tenant, with the time. An organization whose name setting hides names (the default in the EU and the UK) stores no name at all.
  • Why the setup asks for more access. The audit log is not open to every account. The Microsoft setup wizard asks your Microsoft app for the audit log permission, and your service account needs a role at each client that may read the log: Reports Reader for Microsoft Entra changes, and Compliance Administrator for Teams and SharePoint changes, which Microsoft's own pages name as a role that may search the audit log. You give the roles in your delegated access to the client.
  • When StackJack cannot read the log. The row says in one sentence which role or permission adds it, for example "To see who changed this, the service account needs the Reports Reader role at this client." When the client has not yet allowed the audit log permission, because your Microsoft app gained it after the client was consented, the row says to run the customers step of the Microsoft setup wizard instead. Nothing else changes: the setting is checked, reported and put back as before.
  • Some answers take hours. Teams and SharePoint changes are in Microsoft's audit search, which answers later. The row says StackJack is waiting, and StackJack looks again at the next checks. After six checks without an answer it stops asking for that difference.
  • StackJack does not guess. When more than one person changed settings of that kind in that time, or the log shows nobody, the row says no name. When the client's log held more changes in that time than StackJack reads in one check, the row says that in a sentence instead. Settings that Microsoft's audit log does not record in a way StackJack can read show no line at all.

Put back now

Select Put back now on a row that differs. StackJack asks to read the client and plan putting that one setting back. The plan is ready in about a minute. The page links to it. Open it and send it for approval. Your Drift fixes approval rule decides who approves it, and approving by hand needs the phrase FIX DRIFT. Put back now changes nothing by itself.

It is not offered for a setting that a person accepted, a setting that enforcement stopped for, a fix that is already waiting, or a setting whose fix would mean buying or changing seats.

While changes are off for the connection a fix would use, StackJack does not ask for a fix by itself: the row says "Changes are off for this connection at this client". A fix you ask for with Put back now while changes are off changes nothing: the next check cancels it with that reason, or, if it is approved and runs first, it ends with "Changes are not turned on for this connection at this client". Turn changes on for that connection, as Deploy a standard to a client says. The next check then asks for the fix, or you can put the setting back again.

Accept a difference

  1. Select Accept on the row.
  2. Write a reason of 10 to 500 characters. People who may see this client can read it.
  3. Check the end date. 90 days from now is filled in, and you can pick a day up to 365 days out.
  4. Select Accept this difference.

The person who accepts it owns it, and the audit trail records who that is. StackJack leaves the setting alone until the end date, and checks it again after that. To bring the check back sooner, select End the exception on the row.

Enforcement

Each standard the client follows has one choice with three buttons: Follow the standard, On here and Off here. The button that is in force is marked. With enforcement on, StackJack plans a drift fix when a setting differs, and your Drift fixes approval rule decides who approves it. See Approvals and automatic changes.

Report first, then enforce. While enforcement is off, StackJack only reports differences and changes nothing. The page says how long it has been reporting and offers Turn enforcement on for when the differences look right. A standard copied from a ready-made one starts this way.

StackJack never fixes by itself a difference that would mean buying seats or changing seats. A person plans those.

Why a difference was not fixed

What the page saysWhat it means
Enforcement is off for this clientStackJack reports the difference and changes nothing.
A person accepted this differenceStackJack leaves it alone.
Enforcement stopped for this setting after it was put back three times in one daySomething keeps changing it back. A person must look and resume.
Fixing this means buying seats, or changing seatsA person plans it.
A change to this setting is already openStackJack waits for it.
Changes are off for this connection at this clientStackJack reports the difference and asks for no fix. A fix that was already waiting for approval is cancelled. Turn changes on for the connection, and the next check asks for the fix. These differences never stop enforcement, and fixes that could not run because changes were off do not count toward a stop.
StackJack could not start a fixCheck the connection, then check again.

When enforcement stops for a setting, select Resume enforcement on the row after you find out what keeps changing it. If every fix that led to the stop failed only because changes were off for the connection, nothing changed the setting back, so StackJack resumes enforcement by itself at the next check.

A fix that waits is cancelled when the facts change. If enforcement is no longer on for the client (its enforcement choice was changed, or the standard no longer applies there), or a person accepts the difference, a fix that still waits for approval is cancelled and nothing is changed. The row and the History say which one happened, in those words. They say "Nobody approved it" only when a person rejected or skipped the fix, or nobody approved it in time.

History

Select History on a row to see what happened to that setting at this client, newest first: when it started to differ and who changed it, each fix and how it ended, each accepted difference with its reason, and when an exception ended or lapsed.

From your AI

aigov_get_drift reads the same table, in the same words, with who changed each setting where your role may see names. aigov_put_back_setting asks for the plan to put a setting back at one client or several, up to 25 at once. aigov_manage_drift sets or ends an exception, resumes enforcement or asks for a check. aigov_set_enforcement turns enforcement on or off for one client or for a standard. aigov_get_fleet reads every client and where each standard stands. See Use AI Governance from your AI.