Disconnecting and reconnecting an Azure subscription
How an owner disconnects Azure monitoring, what happens to history, and what to check before reconnecting.
Disconnect a subscription
As the account owner, open Dashboard → Azure Subscriptions, find the correct subscription, and choose Disconnect. Read the confirmation and confirm only if you want monitoring to stop. The control is also available under Settings → Connected Subscriptions. Viewers cannot disconnect subscriptions.
After a successful disconnect, CostRadar stops monitoring that connection; future reports and alerts no longer include it as a connected subscription. Disconnecting does not stop Azure resources or Azure charges, cancel your CostRadar paid plan, or delete your Azure subscription.
History and permissions
The disconnect operation does not itself delete existing cost history or audit logs. Retention and account-deletion policies still apply; retained storage does not guarantee that every historical view remains available after a subscription is removed from the connected list. Export any reports you need before disconnecting. Do not treat disconnect as a request to erase your account.
Disconnecting removes the connection from CostRadar. It does not revoke Azure role assignments or remove the Azure export, app registration, or storage account. If you want to revoke access, an authorized Azure administrator must review those separately. Check for other applications using them before removing anything.
Reconnect carefully
Reconnect through the Azure connection flow and validate the required read-only access and Storage Export configuration again. A previously disconnected subscription cannot be used to obtain another free trial. The same account can reconnect its own disconnected subscription during its still-active, unexpired trial; this does not restart or extend the trial. An active paid account can also pass the retired-subscription admission check, subject to the other connection and plan checks.
Admission is not proof that data imports have resumed. Verify the connection and export status and check that fresh billing data arrives before relying on monitoring. Do not assume uninterrupted history, immediate backfill, or automatic restoration of the previous configuration. If reconnection is rejected or imports do not resume, contact support@costradar.io. Never send client secrets, tokens, or SAS URLs.
If you only need to rotate a secret for the same Azure app, use Replace client secret rather than disconnecting. Changing the app or directory may require disconnecting and reconnecting.