Skip to main content

StackJack 0.1.0.14495+eb31649

StackJack 0.1.0.14495+eb31649

This release fixes the "Create it for me" option in the Set up Microsoft wizard, which could fail and leave step 2 with no way forward. It also makes AI agents report the state of your Microsoft partner app the same way the Portal does.

Bug fixes

  • "Create it for me" in Set up Microsoft now works. Microsoft rejected the default app name the wizard used, so the automatic create failed. The wizard now uses a default name that Microsoft accepts.
  • Step 2 is usable after a failed create. Previously, a create that stopped partway left step 2 showing only the word "App", with no Create, Bring, or Next options. Step 2 and the AI Governance Microsoft partner app page now offer the create and bring choices again. They also show a short explanation of what stopped and why, plus a "Try again" option. This explanation is still there after you reload the page.
  • Bringing your own app after a failed create replaces the unfinished one. It no longer leaves a leftover entry behind.
  • Agents now report the correct app status. When an agent checked your Microsoft partner app's health after a failed create, it reported that an app existed. The Portal showed "no app yet" in the same situation. The agent tool now reports "no app yet" too. It also reports whether setup has finished and, if not, gives the same one-line explanation the Portal shows.

UI & UX changes

  • App names are checked before anything is sent to Microsoft. If you type an app name containing Microsoft, Azure, Office, Windows, or Teams, the wizard refuses it immediately and tells you why. Microsoft does not allow these words in app names.
  • Unfinished apps no longer show a button that can't work. If setup stopped after Microsoft created the app, the "Add the ticked connectors to my app" button no longer appears. The page explains that "Try again" keeps the connectors the app was originally created for.
ImprovedBug Fix