StackJack 0.1.0.14798+54801c9
StackJack 0.1.0.14798+54801c9
This release fixes several Microsoft connector problems: Power Platform Admin calls that failed, Purview calls that failed on regional redirects, and connection timeouts. It also makes step 4 of the Set up Microsoft wizard easier to get through, adds clearer guidance to Island tools about which tenants a write affects, and stops checkout from billing you twice for a connector you already pay for.
Improvements
- Island tool descriptions now explain which tenants a write affects. Create and update tools say when Island also applies a rule, policy or setting written with a root or parent key to that tenant's subtenants. Older text implied a hierarchical key could target one specific subtenant, and that has been removed.
- New Island documentation on root, parent and subtenant keys. It explains that each call goes to the tenant the key was made in. To manage one client's subtenant, use a key created inside that subtenant and add it as its own connection.
- Power Platform data policy lists now default to 50 results per page. If you don't set a page size, you get 50 results. The tool description explains how to read further: ask for a larger page size, or follow the continuation link using the path and query only.
- Clearer Power Platform error messages.
- When the Power Platform admin service keeps returning an internal error, the agent is told to compare the same page in the Power Platform admin center under the same account, and to report it to StackJack if it works there.
- When a directory has no Power Platform service set up, the agent gets a consent instruction instead of Microsoft's raw error. The instruction is to generate consent links on the Microsoft Power Platform Admin card for that directory.
- More useful connection timeout messages. When a connection to a service times out, the error now lists which addresses were tried and the outcome for each, instead of a bare "task was canceled" message.
- No more double billing for legacy subscriptions.
- If you try to check out for a connector your organization already pays for, you are now sent to the portal to manage it instead of starting a second subscription.
- When a connector moves from a legacy subscription to current billing, StackJack cancels the old subscription automatically and emails you once about it.
Bug fixes
- Power Platform Admin: Fixed calls failing with a server error after sign-in. StackJack now requests access to Power Platform in the form Microsoft documents for these services.
- Microsoft Purview: Fixed calls failing when Purview redirected the request to a regional address. StackJack now follows a valid regional redirect. It also no longer gets stuck on a remembered regional address that stops working, which previously made later Purview calls keep failing.
- Exchange Online and Purview timeouts: Fixed calls timing out when the first address for a service hung. The connection time is now shared across all of the service's addresses, so one unresponsive address no longer causes the whole call to fail.
- Set up Microsoft wizard, step 4 (your own app): Fixed Next staying disabled forever after a finished customer consent run in which Microsoft refused some customers. Once a run has finished with no customers left, you can continue. Refused customers still show as needing attention.
- Set up Microsoft wizard, re-runs: Fixed a re-run that stopped early keeping earlier results for customers it never reached. Those customers now correctly show as not done.
UI & UX changes
- Setup checklist shows refused customers. For each connector, the checklist lists the customers Microsoft refused, with Microsoft's reason in plain text. It notes that a missing GDAP role is a common cause and has a Run again button that takes you back to step 4.
- Step 4 explains refusals after a run. After a finished run with refusals, step 4 says the checklist lists the refused customers and that Next continues.
- Clearer step 4 wording when using StackJack's app. The step now says:
- Nothing on this step is required, and Next continues.
- The step 3 sign-in covers Microsoft Graph and Azure in your own directory.
- The other Microsoft connectors need an administrator's approval in each directory where you use them, including your own. To get it, enter a tenant ID or domain and choose Make consent links.