Skip to main content
For MSPs

Standards

A standard is a list of settings, each with the value you want, that you put in place at your clients. You write it one time and use it at as many clients as you like. A standard can set Microsoft 365…

Written By Christopher Scaminaci

Last updated 7 days ago

A standard is a list of settings, each with the value you want, that you put in place at your clients. You write it one time and use it at as many clients as you like. A standard can set Microsoft 365 settings, and settings in Claude, OpenAI and ChatGPT, GitHub Copilot and Google Workspace.

At a glance

  • What it does: offers ready-made standards, and keeps your own, with a version each time you change one.
  • Plan: Pro and above.
  • Who: an Administrator of your whole organization. Other roles cannot see the library.
  • Where: AI Governance → Deploy and manage → Standards.
  • Needs: nothing to write a standard. A connection for each platform is needed to plan or apply one.

Start from a ready-made standard

The first time you open Standards, the page shows three ready-made standards. Each one follows a Microsoft guide for Copilot, and its card links to that guide:

  • Copilot setup: gets a client ready for Microsoft 365 Copilot.
  • Copilot: secure and govern: the three parts of Microsoft's foundational guide for Copilot: fix oversharing, set up guardrails, meet regulations.
  • Purview: secure by default: sensitivity labels for everyone, with the audit log on.

Each card says how its settings split, for example 3 set by StackJack, 2 by hand. StackJack sets and watches the first number itself. For the second number, StackJack cannot change the setting for you, so you do it by hand and tick it off. That is the case when the vendor has no programming interface for it, and also when StackJack cannot run that product's settings yet: a setting counts in the first number only when StackJack can run it for that product. The numbers follow what StackJack can run, so they change as it gains support for more products. Today StackJack runs the settings of Microsoft 365, Teams, SharePoint, Purview (its audit log setting runs on your Exchange Online connection), Power Platform, Azure AI, Claude, OpenAI and ChatGPT, GitHub Copilot and Google Gemini. So Copilot setup says 2 set by StackJack, 6 by hand, and Purview: secure by default says 3 set by StackJack, 2 by hand. StackJack keeps who ticked it and when, and the proof for the client shows it. Microsoft has no such interface for most of its own guidance, so a ready-made standard is mostly a tracked checklist. The card says so plainly.

Select Use this on a card. StackJack copies the standard into your library and opens it. You can change anything in the copy. The ready-made standard itself never changes.

A copy starts in report only mode. Its enforcement is off, which means StackJack reports every difference between a client and the standard and changes nothing. The standard's page shows a short guide for this: add the standard to a client, let it report for 14 days, read the Drift page, then turn enforcement on when the report looks right. Turning enforcement on is always your own step.

Make a standard

  1. Open Deploy and manage → Standards and select New standard.
  2. Type a name. You can add a short note about what the standard is for. Select Make the standard. The standard has no settings yet, and it opens.
  3. On the Settings tab, pick a platform on the left, then tick each setting the standard sets. A ticked setting opens a form for its value.
  4. Select Publish version 1.

A standard changes nothing until you add it to a client and a person approves the plan. See Deploy a standard to a client.

The Standards table lists your standards with the products each one touches, how its settings split, its version, how many clients run it and whether enforcement is on or it only reports. Open the menu at the end of a row to Duplicate a standard or Archive it.

The Settings tab

  • The platforms are named as the vendor names them (Microsoft 365 Copilot, Teams, SharePoint, Purview, Entra sign-in and apps, Power Platform, Azure AI, Claude, OpenAI and ChatGPT, GitHub Copilot, Google Gemini, Buying seats). Each shows how many of its settings the standard sets, for example 2 of 14. The page shows one platform at a time.
  • Each setting has a plain title and one line that says what it does. It carries a mark when it is a Preview feature of the vendor, when it is done By hand, or when it needs a licence.
  • Type in the search box to find a setting in any platform. The chips In this standard, Automatic, By hand and Preview narrow the list.
  • A ticked setting opens a form with the right box for each value: a switch for a yes or no, a list to pick from, a number with its unit, or a short text. You never type JSON. A setting you leave out is not touched at a client. A switch you do not set is left as it is at the client, except a switch that the product itself fills in when it is missing (a Copilot agent or app is blocked unless you say otherwise, and a SharePoint site is hidden from search unless you say otherwise). Those switches have no "leave it" choice: the form always writes them, starts from the value the product would use, and says what will be written, for example Will be set to on. If you said nothing it would be on (the default). A box that has a default says what it writes when you leave it empty.
  • Some values belong to one client: a group of its directory, a person, a site. The form does not ask for them. It says Set for each client, and each client gives them on the Clients tab.
  • At the bottom, the summary says what you have ticked, for example: This standard sets 9 settings. StackJack sets and watches 4. You do 5 by hand. It counts the same way as the cards.
  • The Publish button at the top says which version it makes and how many changes are not published yet, for example Publish version 3, 2 changes not published. It stays off until something changed. A setting whose form is not complete stops the publish and names the missing value.
  • Two standards on one client cannot set the same setting. If they do, the plan stops and says so. Remove one, or edit a standard so they do not overlap.

A value is always shown in words: Copilot in meetings: On, with transcript. A list of people, groups or items is shown as a count (3 people, 2 groups). StackJack never writes an id or an address in a value.

The Clients tab

The Clients tab lists the clients that run the standard:

  • Version shows the version each client runs, and says when a newer version is available. The menu at the end of the row has Move to version N and Stop running it here. Stopping removes the standard from a client. It does not undo anything that was already done at the client.
  • Enforcement shows Follows the standard, On here or Off here, and you can change it for one client.
  • Values says None needed, All values given, Optional values, or how many are missing, for example 2 values to give. Optional values means a setting can take something only that client has (the group a Copilot limit applies to, for example) but does not need it for a plan. Select Set values to give it. Select Give values to give them. A form opens with the settings that need something only that client has. Type the people, groups or items for the client and select Save values. A client with a missing value cannot be planned: the plan stops and tells you to give the values first. Once you save them, the plan uses the values you gave for that client. A client's own value replaces the standard's value for that setting at that client only. Use the standard's value takes it away again. It asks you to confirm first, because the ids a client gave are never shown and cannot be read back. The window stays open, and what you typed for the other settings stays.
  • Run it at the chosen client adds the current version to the client you picked in the menu. This records that the client follows the standard. It changes nothing at the client.

The Versions tab

Each version is listed with the date it was published, who published it, and what changed since the version before it, in words: settings added, removed, or changed, with each changed value (Copilot in meetings: Off to On, with transcript). A version never changes. A client keeps the version it was given until you move it to a newer one.

Enforcement

Each standard has an enforcement switch at the top of its page. While it is on, StackJack puts a setting back when a client drifts away from it. While it is off, StackJack only reports. Each client can differ: on the Clients tab, or on the Drift page, you can turn enforcement on or off for one client, or let it follow the standard. See Drift.

Archive a standard

An archived standard is no longer offered. Clients that run it keep their version. Make a new standard if you need a different one.

Use it from your AI

Two tools list and copy the ready-made standards, and aigov_get_standard says each value in words. See Use AI Governance from your AI.

What the page says when something is wrong

  • "This standard sets a control that StackJack does not know." Publish a new version without that setting.
  • "This standard is archived." Pick another standard.
  • "Another standard assigned to this client sets the same control." Remove one of the two.
  • "This client still has values to give before the standard can be planned there." Open the standard, give the values on its Clients tab, then plan again.