Azure Cloud Discovery and Service Graph Connector for Azure running in parallelIssue Can we run Azure cloud discovery and Service Graph Connector for Azure in parallel and what are the implications...ReleaseService Graph Connector for AzureResolutionYou can run Azure Service Graph (SG-Azure) and Azure Cloud Discovery in parallel, and your proposed setup — daily SG-Azure for incremental updates and Azure Cloud Discovery every 15 days for full sync — is a valid and common approach in many enterprise environments. Let’s break this down with key points and caveats: SG-Azure (Service Graph Connector): ->Pulls data incrementally (daily or near real-time).->It’s more performant and reliable for frequent updates.->Limitation: It does not cover all CIs (Configuration Items) — typically focuses on core Azure resources like VMs, network interfaces, disks, resource groups, etc.->Fewer relationships and limited visibility into some service-specific or deeply nested components. Azure Cloud Discovery:->Uses Azure APIs and credentials to do a full scan.->Covers more resource classes, including some not covered by SG-Azure (e.g., App Services, Key Vaults, certain PaaS services).->More extensive CI relationships, but resource-intensive and not suitable for daily runs due to performance and API throttling concerns. Considerations->CI Overlap / Duplicate Handling: Ensure your ServiceNow CMDB or any downstream system can reconcile duplicates or has a policy to prioritize one source over the other.E.g., set precedence rules in CMDB CI Identification and Reconciliation Engine (IRE).->Credential Management: Azure Cloud Discovery requires read-access roles and credentials, while SG-Azure uses integration tokens and is managed differently.->Performance Monitoring: Monitor both integrations to ensure no API limits are breached, and performance issues are handled.->License / Cost Implications: Depending on your ServiceNow and Azure usage, there might be API call costs or licensing considerations for both methods.