Is cmdb_ci_azure_subscription still being populated by discovery via "Discover Subscription" UI Action?Issue Is cmdb_ci_azure_subscription still being used by discovery via "Discover Subscription" UI Action?ReleaseXanadu Patch 4CauseServicenow discovery is no longer using cmdb_ci_azure_subscription table. All the CI will be populated in cmdb_ci_cloud_service_account table during discovery.The UI Action "Discover Subscription" is using CAPI method hence after migrating from CPG to Pattern this method of discovering azure subscriptions is not supported. This UI action will be deprecated in the upcoming releases. Ref- Migrate from CAPI to PatternsResolutionThe intended steps to discover Azure Service Accounts is :- Go to discovery_schedule table- Select "Cloud Discovery" to launch cloud discovery wizard- Create a new Service Account by clicking on "add account", fill in details like "name" of service account, Subscription/Management Group ID, Azure Credentials & test the account.- Then fill out new schedule details and launch scheduleThis will create the new service account and populate all the subscriptions/sub-accounts under it. Also, instead of discovering each service account, we can use the "Management Group ID" instead of separate "Subscription ID" when there is a large number of accounts & datacenters to be discovered. To have reliable results we insist the usage of Cloud Discovery Workspace. Ref- Setup guide for Microsoft Azure Cloud on Cloud Provisioning and Governance