PackMyApp Documentation

Disconnect, Reconnect, And Why It Matters

Know when disconnect is the right action, what it changes, and how to recover cleanly.

Settings And Tenants Audience: Customer, Admin Access: Public

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

  1. Open Settings.
  2. In the left menu, click Disconnect.
  3. Read the current tenant/customer indicators on the page before proceeding.
  4. Click Disconnect tenant link.
  5. Wait for the status to update. The page will confirm disconnection.
  6. PackMyApp now shows the workspace without an active tenant.

Click Path — Reconnect

  1. In the left menu, click Tenant Connection.
  2. Follow the tenant connect flow to link the intended tenant.
  3. Run Health after reconnecting to confirm the new link is healthy.
  4. Return to App only 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

  1. If disconnect does not complete, run Health first to clear any active error state.
  2. If reconnect fails, verify you are using the correct Microsoft account for the intended tenant.
  3. If context still looks wrong after reconnect, check Customer Workspace to confirm the active customer.
  4. Use Activity Logs to trace what happened during the disconnect/reconnect cycle.
  5. Do not attempt repeated disconnect/reconnect cycles without checking the cause first.

Next Articles