Skip to main content

StackJack 0.1.0.14631+38a9d54

StackJack 0.1.0.14631+38a9d54

AI Governance standards can now apply and monitor settings in six more Microsoft products, using your existing connection in each client's Microsoft directory. This release also makes deploy results easier to understand and shows platform names in plain words across the governance pages.

New features

  • Standards now apply and monitor settings in more Microsoft products. You can now target SharePoint admin, Microsoft Purview, Exchange Online, Power Platform, Azure (Azure OpenAI and AI Foundry), and Microsoft Teams admin when deploying standards. StackJack uses your organization's connection for that product in the client's Microsoft directory. A product is available as a target only when it has an enabled connection and the client's directory is recorded. Drift checks read these settings back through the same connection the last plan used.
  • Teams admin settings are now automated. The two automated Teams controls carry a preview label. The preview label alone does not send a step to a person for review. Your approval rules decide, the same as for other preview controls.
  • Starter standards automate more settings. "Purview secure by default" now has 3 settings applied by StackJack and 2 done by hand. "Copilot setup" now includes an automated Teams meeting policy step at clients with a Teams admin connection.

Improvements

  • Clearer deploy step results. Every result a deploy step can end with now has its own plain explanation instead of a generic message. Examples:
  • Vendor changes not enabled: points you to the Vendor changes page and the control for turning changes on.
  • Plan requirement: says which plan deploy steps require.
  • Partial changes: if a vendor refuses a change after earlier parts of the step were already applied, the message no longer says that nothing changed. It tells you to check the vendor's console.
  • Lists too large to read: if a group or policy list is too large to read in full, the message now says so.
  • Better explanations for drift gaps. When a platform shows as not connected, the message lists the possible causes: no plan has run there yet, there is no connection, or the client's Microsoft directory is missing or has changed.
  • The AI tool for reading a standard now uses plain names. It names the platform and area in words (for example, "Microsoft Teams admin" or "Azure AI") instead of internal identifiers. Automation context uses the same plain names.
  • Product documentation now describes which products standards can apply, plan, and monitor.

Bug fixes

  • Deploys stop after a client's Microsoft directory is disconnected. If you disconnect a client's directory, StackJack no longer offers deploy targets there and does not request fixes during enforcement. Drift shows the platform as not connected. The same applies if the client is linked to a different directory. A step approved before that change now stops without reading or writing anything, and explains that the client's directory may have been disconnected or re-linked.
  • No more duplicate Power Platform billing policies. If Power Platform returns billing policy data in an unexpected format, the step now stops safely. Previously it could treat an existing policy as missing and create another one on each attempt.

UI & UX changes

  • The Drift and Fleet pages now show each platform by its proper name (for example, "Power Platform" or "SharePoint admin") instead of internal identifiers such as "Powerplatform" or "Sharepoint".
  • The Vendor changes list now labels Azure connections as "Microsoft Azure" instead of "the vendor".