Skip to main content

StackJack 0.1.0.16194+9d2c828

StackJack 0.1.0.16194+9d2c828

This release adds app-only Microsoft Graph connections and lets you choose Microsoft as your organization's decision engine, including with your own Azure Foundry deployment. It also adds endpoint agent file checks on browser uploads to AI sites and makes browser upload inspection more reliable.

New features

  • App-only Microsoft Graph connections. The Microsoft Graph card on the Connectors page now asks how to connect:

  • Sign in with Microsoft is the default and works as before.

  • App-only with StackJack's app connects without any person's sign-in. You start it with Connect with Microsoft. A Global Administrator or Privileged Role Administrator of the Microsoft directory must complete the consent, and your organization must have an active Microsoft Graph subscription. If you remove your last connection to that directory, you need to run Connect with Microsoft again to reconnect.

  • App-only with your own app registration takes your tenant ID, client ID and client secret, or gives you an admin-consent link. The secret is never shown again after you save it.

  • App-only Graph for agents. The agent credential form accepts an app-only Microsoft Graph credential. For StackJack's app, the directory must already be connected for your organization.

  • App-only setup script option. The customer app-registration script has a new app-only option that sets up your own app registration for app-only connections.

  • Choose your decision engine. In Settings you can now choose Microsoft as your organization's decision engine and optionally save your own Azure Foundry deployment. Once you choose Microsoft, these features run on it:

  • Automation decide steps and smart filters. Existing steps move to Microsoft, and the Settings card and editors say so.

  • AI Governance judgments and the exposure scan.

  • Smart tool search.

    The chat builder knows about both providers.

  • Endpoint agent file checks on browser uploads. The AI Governance policy now has a file checks setting for files uploaded to AI sites through the browser extension:

  • The agent checks the file's type and, where allowed, its content. On Windows this includes text inside PDFs.

  • Blocked file types are refused.

  • When a file can't be checked, your organization's chosen rule decides whether the upload goes ahead.

  • A warned upload is recorded as warned, and continuing after a warning is recorded as such.

  • The AI Governance policy tools available to your agents now show the file check settings.

  • Shadow AI apps. A desktop app that is not in the AI app catalog and reaches an AI site is now reported as a shadow AI app. Browsers are excluded. On Windows, this uses the agent's new per-app tracking of process starts and AI-domain lookups.

Improvements

  • Clearer Microsoft Graph connection listing. The list-connections tool now shows when a Microsoft Graph connection is app-only. If you still have your own sign-in on a connection your organization switched to app-only, your calls run under your sign-in, and the listing says so.
  • Test Connection on app-only connections.
  • An app-only connection whose app can't read organization details still validates once its token is issued.
  • Consent problems on your own app registration now name your app registration.
  • If StackJack's app has not been consented, you are directed to Connect with Microsoft.
  • New Microsoft Graph troubleshooting entries. The help page now covers:
  • an app that is disabled or blocked in the tenant (AADSTS7000112, AADSTS500014, AADSTS53003);
  • Microsoft Graph not being active on your subscription;
  • consent failures caused by an app registration that lists other Microsoft services (AADSTS650052).
  • Faster effect when changing decision settings.
  • A decision engine change applies to the next decide step or exposure batch within about a minute, including runs and scans already in progress.
  • If you remove or replace your own Azure Foundry deployment, StackJack's services stop using it within five minutes, and the AI edge within 25 minutes.
  • Browser DNS when AI sites are blocked or warned. The browser deployment and AI settings scripts now set supported browsers to use the device's DNS where AI sites are blocked or warned, so the block or warning also applies inside the browser. The deploy page and readiness checks reflect this.
  • Device details. The device panel now shows per-browser coverage, any missing agent permissions, and files shared with AI sites. For shared files it shows type, size and site, never the file name.

Optimizations

  • Less waiting when reading uploaded files. The browser extension now reads all files in an upload at once against a single deadline, instead of waiting on each file in turn. Before, a selection with many slow files could hold up the page for about a minute.

Bug fixes

  • Uploads no longer stall on unreadable files. Before, a file the browser extension couldn't read could hold up an upload indefinitely. Now:
  • The extension waits up to 3 seconds, a little longer for large selections, and never more than 10 seconds.
  • A plain-text file whose text isn't read in time is left out of the content check and noted.
  • The other files in the upload are still checked as usual.
  • Activity stays with the right organization. When a device is re-enrolled into a different organization, activity it recorded under the previous organization is no longer reported to the new one.
  • Concurrent AI settings script runs. Running the AI settings script more than once at the same time on a device (for example, two RMM jobs, or a retry next to a slow run) no longer lets the runs interfere with each other. This applies to the Windows, macOS and Linux versions.

UI & UX changes

  • Microsoft Graph connections on the Connectors page show an App-only badge.
  • The Microsoft setup wizard now shows an app-only Graph connection as connected, labeled as using your app or StackJack's app.
  • It no longer offers Sign in or Move to the one app for that connection.
  • The consent step explains what to do when your only Graph connection is app-only.
  • For app-only connections, the Connectors card no longer offers a personal sign-in. If you still hold a personal key from an earlier sign-in, you can still revoke it there.

Known issues

  • The admin-consent link for an app-only app registration asks for every permission the registration lists, across every Microsoft service it names. If your registration also lists services a customer tenant doesn't have (such as Partner Center), consent fails there with AADSTS650052. Use a separate app registration for app-only connections to those customers.