Skip to main content
For MSPs

Deploy a standard to a client

To deploy a standard, you plan it, read the plan, send it for approval, and let StackJack make the changes. Every step shows the value StackJack read at the client when it made the plan (Now) and the…

Written By Christopher Scaminaci

Last updated 4 days ago

To deploy a standard, you plan it, read the plan, send it for approval, and let StackJack make the changes. Every step shows the value StackJack read at the client when it made the plan (Now) and the value it will write (Will be), in plain words, so you decide with the facts in front of you. When the run ends you can download a record of it for the client.

At a glance

  • What it does: reads a client, shows what a standard would change, and makes the changes after approval.
  • Plan: Pro and above.
  • Who: an Administrator of your whole organization, or a person whose role was given Request changes at the client, who can plan and send for approval. Approving needs Apply changes on a run they planned themselves, or Approve changes up to a limit. See Approvals and automatic changes.
  • Where: AI Governance → Deploy and manage → Deploy.
  • Needs: a standard added to the client, and a working connection for each platform the standard sets. Until everything is in place, an Administrator sees Set up deploy and manage at the top of this tab, with the step to do now. See Deploy and manage.

Plan

  1. Pick the client in the client picker.
  2. Open Deploy and manage → Deploy. The client's name is at the top of the page. The panel Standards at the client lists the standards it follows.
  3. Select Plan what it would change beside a standard.
  4. StackJack opens the run. It shows StackJack is reading the client now. This takes about a minute and the page refreshes by itself. You can leave and come back.

StackJack uses the default connection of each platform. To use another connection, make it the default on the Connectors page before you plan. A plan reads the client and sends nothing.

Teams, SharePoint, Purview, Exchange Online, Power Platform and Azure settings run with that connection's own Microsoft sign-in, inside the client's directory. So the client needs its Microsoft directory on record, as for Microsoft 365, and the person who signed the connection in needs that product's role at the client through your delegated access, for example Teams Administrator for Teams. The Purview audit log setting runs on the Exchange Online connection.

The two Teams settings, Copilot in a meeting policy and Copilot in a calling policy, carry the Preview mark. Your approval rules decide them like any other setting: the mark does not send them to a person by itself. If you want a person to look at each one, keep A person approves for Applying a standard and Drift fixes. See Approvals and automatic changes.

If the plan cannot be made, the run says why in a sentence. The usual reasons are a connection that is switched off or has no permission to read, or a Microsoft client with no directory on record.

Read the plan

The Summary panel at the top of the run says it in one line, for example: "14 changes. 2 purchases: 1,512.00 USD over 12 months. 3 steps for you by hand. 1 cannot run: no connection for its platform." The buttons to decide are at the top of the page.

Under it, the plan is one table, grouped in the order StackJack runs it: Buy, Groups, Licences, Settings, then By hand. Each row has these columns:

ColumnWhat it shows
SettingThe setting in plain words, and its area.
NowThe value StackJack read at the client when it made the plan. It uses the same labels as Will be and covers only what the step changes: for a role change, the role the person has now; for a person to add, Not set while they are not there. For a purchase, it is the seats the client holds or has on order, such as "Seats: 5". A plan made before StackJack kept this value says Not recorded.
Will beThe value StackJack will write.
CostThe seats, the term and the total with its currency of a purchase. When the distributor gave no price, the row says so and shows no total.
Who decidesA person, the approval policy or an automation, and when an automation's time runs out.
StateWhere the step stands, and its result in plain words when it ran.

A value is always in words, such as "Copilot in meetings: On, with transcript". People, groups and other ids are counted, such as "3 people", and never listed.

Some rows are not changes:

  • Cannot run. A setting StackJack cannot change at this client, with the reason (for example, a connection that cannot read). It sits in its group with the state Cannot run.
  • By hand. A setting StackJack cannot change itself, with a link when the vendor has one. Tick the box when you have done it in the vendor's console. StackJack cannot read these settings, so a tick is your word and not a check. The run keeps who ticked the line and when, the audit trail has an entry for it, and the proof for the client shows it. Tick the box again to take the tick back.
  • Start the sign-in job. When a step made an Entra provisioning (sign-in) job, Microsoft makes the job paused. The plan then adds a by-hand line with a link to Microsoft Entra: save the vendor's connection details (the web address and the secret token) on the application's Provisioning page, then start it. StackJack never stores the secret token.

A setting that the client already has set is not in the plan, and nothing is changed for it.

Decide

  1. Select Send for approval. Your approval rules now decide each step. A step may be approved at once by a rule, handed to an automation, or wait for a person. See Approvals and automatic changes.

  2. For the steps that wait for a person, select Approve and the number of steps. A window opens. It repeats the summary of the steps it approves, so you approve what you read. Type the phrase shown and select Approve again. The phrase is in capital letters and must match exactly. The run's kind sets the phrase:

    Kind of runPhrase
    Applying a standardAPPLY STANDARD
    Putting settings back (drift)FIX DRIFT
    Changing seatsCHANGE SEATS
    Buying seatsBUY SEATS
    Changing settings by handAPPLY CHANGES
  3. The button stays off until the phrase matches and your sign-in used a second factor. If it has none, the window says so and links to sign in again. The window approves exactly the steps it showed. If a step was added or decided by someone else while it was open, nothing is approved, and the page asks you to read the plan again.

  4. To refuse, select Reject them. Nothing is changed. Reject them is shown only when you can see every step that waits. Some runs hold steps of other kinds of change that you may not decide. The page then says how many other steps wait for someone else, and the approve button covers only the steps you see. To refuse a step you see, skip it, as in the next step.

  5. To skip one step and approve the rest, open the menu at the end of its row and select Skip this step. A window asks why. It also says how many waiting steps need this one: they cannot run without it, so they are skipped with it, and your reason covers them. Type a reason of 10 to 500 characters and select Skip this step. The reason is kept in the record, and the proof for the client shows it.

  6. To stop the whole run, select Cancel the whole run. Steps that already ran are not undone.

Before StackJack can change anything through a connection at a client, changes must be turned on for that connection at that client. Open AI Governance → AI inventory → Vendor changes, type ALLOW CHANGES and select Turn changes on for the connection. See Making changes in your AI vendor accounts. A step on a connection whose changes are off ends with "Changes are not turned on for this connection at this client", and nothing is changed.

A step runs only in the client's Microsoft directory of now. If the client's directory was disconnected or linked again after the plan, the step ends without a change and says so. Plan again.

StackJack makes approved changes within a minute. A step that waits for a decision for seven days expires. Nothing is changed, and you plan again if you still want it.

What each step can end as

ResultWhat it means
DoneStackJack made the change and read the value back to check it.
Already setThe client already had the value.
FailedThe platform refused, or the value read back was not the one asked for. The step says which, and what to check.
Skipped or RejectedA person decided, with a reason for a skip.
Cancelled or ExpiredThe run was cancelled, or nobody decided in seven days.
Not runA step it depends on failed or was skipped. Fix that step first.

If a step reads back a different value than the one sent, or could not be read back, the run says so. Look at the setting in the vendor's console before you rely on it.

The proof for the client

When every step is done, skipped or failed, the run is finished. The Summary panel then shows the result, for example "12 done, 1 skipped, 1 failed", and a link to the same proof as JSON. The button Download the proof for the client is at the top of the page. The proof is a page you can print or save as a PDF.

The proof shows, for each step, in words: the value before the change (what StackJack read when it made the plan), what the standard asked for, what StackJack found at the client when the step ended, the result, who approved it and when. People, groups and ids are counted, not listed. A step that never ran shows no found value, so a value that was not read is never shown as set. A step planned before StackJack kept the value it read says Not recorded. A person is named by kind only (a person, a rule, an automation). The audit trail names people. The lines you did by hand are listed under Done by hand, each as Ticked by a person on a date or as Not ticked.

The proof holds the client's own settings, so it is for the client and for you. Each download writes one entry in the audit trail. A run that is not finished has no proof, and a run of another client is not found.

Common messages

  • "A change to this setting is already waiting or running for this client." Wait for it to finish, or cancel it, then plan again.
  • "StackJack could not read this client to make a plan." Try again in a few minutes. If it keeps failing, contact support.
  • "The price, the seats or the term changed after you approved this purchase, so nothing was ordered." Plan the purchase again and approve the new numbers.
  • "This change was edited after you opened it." Reload, read it again and decide again.