Newly added Azure subscriptions in CloudHealth may appear with an Unknown or Critical status shortly after onboarding. This can cause confusion for users expecting these subscriptions to report as healthy once they are added to the platform.
This behavior is a known issue and is related to the onboarding process for certain Azure subscriptions. In these cases, manual intervention from the CloudHealth engineering team is required to complete the onboarding and correctly populate the subscription status.
If a newly added Azure subscription remains in an Unknown or Critical state, open a support ticket with CloudHealth Technical Support. Include the affected subscription IDs and any relevant screenshots so the engineering team can manually complete the onboarding and update the subscription status.