We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Azure Discovery Issue – Private Endpoints Not Discovered & MSSQL Status Incorrect

abhijee
Tera Contributor

3 weeks ago

Hello everyone,

I am currently working on Azure Cloud Discovery. The discovery process has successfully identified most of the Azure resources. However, Private Endpoints are not being discovered yet.

Additionally, I have noticed that an MSSQL database, which is active in the Azure portal, is showing an "Operational Status" as "Retired" in the CMDB.

 

Does anyone have an idea why this is happening and how we can resolve it?

 

Thank you in advance for your guidance.

0 Helpfuls
  • 311 Views
1 REPLY 1

pr8172510
Kilo Sage

3 weeks ago

Hi @abhijee,

 check the following

1. Azure Private Endpoints not discovered

  • Verify that your Service Graph Connector for Microsoft Azure version supports discovery of Azure Private Endpoints.
  • Confirm the Azure application (service principal) has the required Reader permissions for the subscription/resource group and access to Microsoft.Network/privateEndpoints.
  • Review the Service Graph Connector import logs and IRE logs for any skipped or failed records.

2. MSSQL Database showing as "Retired"

  • Check the CI's Discovery Source, Last Discovered, and Audit History to determine what updated the Operational Status.
  • If the Azure resource is still active, verify whether another discovery source, transform map, reconciliation rule, or lifecycle process has set the status to Retired.
  • Also confirm that the resource is being returned by the latest Azure import and successfully processed by the Identification and Reconciliation Engine (IRE).

Azure resources are imported through the Service Graph Connector for Microsoft Azure and updated using the Identification and Reconciliation Engine (IRE).

 

If a supported Azure resource is missing or a CI is updated with an unexpected operational status, the recommended troubleshooting steps are to validate connector support, Azure permissions, import logs, IRE logs, and reconciliation rules.