UPDATE 2026-03-05: This new functionality has now been deployed.
As part of our ongoing effort to simplify cloud onboarding and provide a unified experience across our Elements platform, we are introducing an update to how Azure Subscriptions are onboarded for exposure scanning.
The change is expected to be released during March 2026.
What is changing?
Following the earlier transition of Microsoft Tenant onboarding to Elements Cloud Account Management (CLAM) page, Azure Subscription onboarding will now also be handled through CLAM.This gives customers a consistent and centralized way to manage cloud accounts.
Who is affected?
This change applies only to customers using Exposure Management for Cloud (cloud security posture capabilities).
If you are not using Exposure Management for Cloud, no further action is required.
Do I need to take action?
No immediate action is required.Your existing connected Azure Tenants and Subscriptions will continue to function normally.
You will only need to take action when you want to onboard a new Azure Subscription for exposure (cloud security posture) scanning.
What happens when I want to add a new Azure Subscription?
If the Tenant associated with the subscription is marked as “Legacy” in the UI, you must first re‑onboard that Tenant via CLAM.
How to re‑onboard a Legacy Tenant
- Go to the Tenant’s page in Elements.
- Locate the Cloud Security Posture capability.
- Click “Connect now” to re‑onboard the Tenant.
- Once the Tenant connection has been re‑established in CLAM, onboarding new Azure Subscriptions will be enabled.
Important Note About PowerShell Script Downloads
After this change:
- Downloading the PowerShell onboarding script for Azure Subscriptions will only be possible if the parent Tenant’s Cloud Security Posture capability is already connected and active.
If the tenant has not been re‑onboarded yet, the system will prevent script download until the connection is re‑established.