After CAPI to Pattern migration, Cloud Discovery schedule that has multiple service accounts linked does not launch all the cloud patterns for each service accountIssue After CAPI to Pattern migration, Cloud Discovery schedule that has multiple service accounts linked does not launch all the cloud patterns for each service account. This is due to changes on the design of Cloud Discovery. ResolutionFor AWS, if multiple cmp_discovery_ldc_config records are created to link different service accounts to one discovery schedule, then please make sure all these service accounts belong to same main account, also cmp_discovery_ldc_config must exist for the main account for the discovery schedule. This is because we are filtering the output of the Service Account pattern, and if it doesn't exist for the main account, the Sub Account pattern will not launch. For Azure, please create Azure Management Group, then add all the subscriptions to the Management Group. Assign permission to the Management group for a Service Principal.On the instance, Navigate to Discovery > Home > View Schedules > Add schedule > Add Cloud Schedule > create a new schedule for Azure here. Use group ID as the Account id, also add credential with information of the Service Pincipal that was given permission on the Management Group.