StackJack 0.1.0.14531+e41f53b
StackJack 0.1.0.14531+e41f53b
This release focuses on the Set up Microsoft wizard and your Microsoft partner app. Checks are more accurate, repairs take fewer sign-ins, and one customer's consent problem no longer affects your other customers. The Microsoft Graph connector also now covers every permission its sign-in asks for.
New features
- Replace a Microsoft app that was deleted in Microsoft. If your partner app was removed on the Microsoft side, the wizard used to show a "missing app" blocker with no way forward. You can now point the wizard at another existing app by entering its client ID.
- Your StackJack certificate and your selected connectors carry over.
- Nothing is deleted in Microsoft.
- The service account will need to sign in again, and customer consent is tracked fresh for the new app.
Improvements
- Graph permissions now cover the whole connector. The Microsoft Graph connector's app permissions now include the security, Purview, Copilot administration, and read permissions its own sign-in requests, at every permission tier. Before, technicians who were not administrators could see "Need admin approval", and some customer calls were refused.
- For an existing app, use Add the ticked connectors in the wizard to add the missing permissions.
- One customer's consent problem no longer affects the rest. A single customer without consent, or with a lapsed delegated admin relationship, used to sign the service account out for every customer and stop the whole consent run.
- That customer is now marked as failed by name, and the run continues for everyone else.
- Deployments report a specific reason for that one client: it may not have consented, or the delegated admin relationship may be missing.
- Clearer messages throughout the wizard. Every wizard outcome now has its own explanation instead of a generic "The request was refused."
- "Your Microsoft app is fixed" now appears only when the app really is fixed. Otherwise the wizard says that more work is left or that nothing changed.
- Service account sign-in explains refusals. If the service account sign-in is refused, the Health card now shows a plain explanation of why, instead of a generic failure.
- Permission catalog updates reach your customers. When StackJack updates the permissions behind a connector, those changes are now pushed to your customers as intended.
- The AI agent's partner app health tool points to the right place. For repairs it now directs you to the Set up Microsoft wizard. It points to the partner app page only for signing in the service account.
Bug fixes
- Certificate check: The app check never recognized the certificate StackJack holds, so an app with the correct certificate uploaded kept reporting that it had certificates "but not the one StackJack holds." It now matches correctly.
- Check results not saved: Running Fix my app when there was nothing to repair did not save the new check result, so the finding stayed after you uploaded a certificate by hand. The result is now saved.
- Unsaved results reported as success: If a check or fix result could not be saved, the wizard could still report the app as checked or fixed. It now tells you the check could not be saved and asks you to press Check my app again.
- Power Platform Admin sign-in: Apps created by the wizard were missing the Power Platform sign-in address, so that sign-in failed. New apps include it, and existing apps show a finding that Fix my app repairs.
- Existing certificates preserved: Fix my app could replace an existing certificate on your app when Microsoft reported that certificate in an unexpected format. Existing certificates are now always kept.
- New apps marked missing: A newly created app could be marked as missing because Microsoft had not finished making it visible. The wizard now waits for it. If the app still isn't visible, Try again picks up where it left off without creating anything twice.
- Findings erased by the daily check: The daily check could erase real findings about your app (such as certificate, sign-in address, or permission problems) when the service account was not signed in. That could let the wizard pass a broken app. Those findings are now kept.
- Outdated checks in step 2: Step 2 could accept an outdated or missing check, and you were then blocked later in steps 3 or 4. Step 2 now catches this and offers Check my app.
- Second-factor warning: The service account's second-factor warning could never clear. It now appears only when the sign-in actually showed no second factor, and it reads "did not show a second factor."
- Step 4 refusing valid connections: Step 4 refused a connection that had been signed in with the secret from the app registration script, even though step 3 had accepted it. It is now accepted.
- Consent status after replacing an app: Consent results from a previous app were counted for a replacement app, so every customer showed as consented.
- Consent results now belong to the app they were made for.
- Consent runs from before this release are treated as not yet run. You may need one extra click to run consent again; customers that are already consented are recognized as current.
- Sign-ins on an unfinished app: A technician sign-in could start on an unfinished app. It is now refused with an explanation.
- Resuming app creation: Resuming an app creation that had already made the app in Microsoft could be refused after a connector's permissions changed. It now resumes with the app's original permissions, and you can add new connectors afterwards.
- Unexpected wizard errors: Temporary Microsoft errors (such as throttling) or an internal StackJack storage fault during the wizard's customer step could end the step with an unexpected error. The step now stops cleanly with a clear message.
UI & UX changes
- One sign-in for repairs. Step 2 now has one Fix everything button that repairs all fixable issues in a single administrator sign-in. Before, each finding had its own button and its own sign-in. Certificate uploads and renewals keep their own button.
- No Fix button for service account findings. These findings no longer show a Fix button that led to a dead end. Instead you see a note that the service account is only needed for unattended work and does not block your connectors. The note links to where it can be signed in, or tells you to ask an AI Governance administrator if you don't have access.
- Check my app is always available. The Check my app button now appears for every finished app, including one that was reported missing and has since been restored in Microsoft.
Fixed customer-reported issues
- The Microsoft Graph connector returned consent errors for customer tenants reached through delegated admin relationships (
01M63GB3PHC6BQ5N0Y8WAVFMWY). - The partner app's Graph permissions now include every permission the connector's sign-in requests.
- One customer's consent problem no longer affects your other customers.
- Existing apps can pick up the missing permissions with Add the ticked connectors and then a new consent run.