StackJack 0.1.0.15572+6c87d7d
This release makes Microsoft connector setup and consent more reliable, gets SharePoint Admin tools working in customer directories managed through GDAP, and fixes Purview for Canada-region tenants. It also clarifies several AI tool descriptions and improves the message shown when a card is declined during a bundle change.
Improvements
- Exchange Online and Purview admin consent for customer directories is now a one-click link on the connector cards and in the Set up Microsoft wizard. A short note beside the link explains three things:
- The consent covers every permission the app lists.
- A directory that doesn't have one of those services will refuse it.
- If you use your own app, its registration must include the Exchange management permission.
- GDAP customers are still directed to Authorize all customers. The setup guides and help text now match this flow.
- When Microsoft reports a missing consent for Exchange Online or Purview, the guidance now tells you what to check first and points you to the consent link.
- The Autotask charge-writing tools now tell your AI agent that charges created through the API are recorded under the API user, not the technician who asked.
- The SharePoint Admin tools for reading and updating SharePoint settings now point your AI agent to the tenant-property tools when working in a customer directory through GDAP. Microsoft doesn't allow the settings tools in that setup.
- StackJack's support assistant now picks up messages you send in support chat conversations, including conversations with no ticket or a closed ticket.
- The support assistant can now answer questions about your connectors' own data that use billing-like words, such as Autotask ticket charges or QuickBooks invoices. Previously it declined these questions.
Optimizations
- SharePoint Admin calls in GDAP-managed customer directories now remember the admin site location between requests. This avoids repeating the lookup on every call.
Bug fixes
- SharePoint Admin tools that use the SharePoint admin site now work in customer directories accessed through GDAP. Previously they failed in every such directory.
- When a SharePoint Admin call hits a network problem or throttling, StackJack now reports it as a temporary error you can retry. Previously it showed a misleading sign-in or consent message.
- Purview connector calls for tenants in the Canada region no longer time out.
- For connections that use your organization's Microsoft partner app with a certificate, Generate link now produces a consent link for your app instead of StackJack's.
- While you're adding a new Microsoft connection, the consent link now uses the app details entered in the form instead of the default connection's.
- While you're adding a Microsoft Graph connection, the card now shows a message if the permission tier isn't known yet, instead of generating a full-permission link.
- The Autotask stocked-items list tool now names the correct field for filtering by product. Filtering on the wrong field caused errors from Autotask.
UI & UX changes
- Signing in to a Microsoft connector now always asks you to choose an account. Previously the browser could silently reuse whichever Microsoft account was already signed in.
- The NinjaOne Region list now shows the host and location for the two US regions, so it's easier to tell them apart. Choosing the wrong one leads to a sign-in error on NinjaOne's side.
- A passing Test for Exchange Online, SharePoint Admin, Defender, Teams Admin, Purview and Power Platform now says what was actually checked:
- The sign-in works.
- The service itself wasn't tested.
- Each customer directory still needs its own consent and role.
- If your card is declined during a bundle change, you now see a clear message: nothing was changed, and you should update your payment method and try again. Previously you only saw a generic "please try again".
Fixed customer-reported issues
- Connecting NinjaOne failed with a region and domain mismatch on NinjaOne's sign-in page (
01M7K70QP98HGEASV4RW82V4C2). The Region list now names each US region's host and location, so the correct one is easier to pick. - Microsoft consent links failed in customer directories, with unclear results when a directory lacked a required service (
01M7DT4XWD0CM9FAGK2VD1FS4P). Exchange Online and Purview now use a one-click consent link, with a note explaining when and why a directory may refuse it.