Disconnect, Reconnect, And Why It Matters
Prerequisites
- You are signed in.
- You understand which customer and tenant context is currently active.
When To Disconnect
Disconnect is needed in these situations:
- You want to link a different Microsoft tenant to the same customer workspace.
- The current tenant link is stale or broken and reconnect requires a clean start.
- You are switching between customers and need to ensure no cross-tenant contamination.
- Health checks report a tenant link error that cannot be resolved by reconnecting alone.
Do not disconnect unless you have a specific reason. A disconnected workspace blocks all deploy and update actions until the tenant is reconnected.
Click Path — Disconnect
- Open
Settings. - In the left menu, click
Disconnect. - Read the current tenant/customer indicators on the page before proceeding.
- Click
Disconnect tenant link. - Wait for the status to update. The page will confirm disconnection.
- PackMyApp now shows the workspace without an active tenant.
Click Path — Reconnect
- In the left menu, click
Tenant Connection. - Follow the tenant connect flow to link the intended tenant.
- Run
Healthafter reconnecting to confirm the new link is healthy. - Return to
Apponly after health confirms the tenant is active.
Expected Result
- Old tenant link is removed cleanly.
- New tenant connection is active and confirmed by Health.
- Deploy and update actions are available again.
If It Fails
- If disconnect does not complete, run
Healthfirst to clear any active error state. - If reconnect fails, verify you are using the correct Microsoft account for the intended tenant.
- If context still looks wrong after reconnect, check
Customer Workspaceto confirm the active customer. - Use
Activity Logsto trace what happened during the disconnect/reconnect cycle. - Do not attempt repeated disconnect/reconnect cycles without checking the cause first.