Skip to content

Commit a19ae00

Browse files
Added issue
1 parent 0ce7bd7 commit a19ae00

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

articles/azure-monitor/scom-manage-instance/troubleshoot-scom-managed-instance.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: This article describes the errors that might occur when you deploy
55
author: PriskeyJeronika-MS
66
ms.author: v-gjeronika
77
manager: jsuri
8-
ms.date: 05/22/2024
8+
ms.date: 06/19/2024
99
ms.service: azure-monitor
1010
ms.subservice: operations-manager-managed-instance
1111
ms.topic: troubleshooting-general
@@ -92,6 +92,17 @@ This article describes the errors that might occur when you deploy or use Azure
9292

9393
**Resolution**: Provide an available IP from the subnet range and retry the operation.
9494

95+
### Issue: Identity isn’t a system admin on SQL Managed Instance: '%instance'.
96+
97+
**Cause**: Occurs due to the following reasons:
98+
99+
1. User Managed Identity isn’t SQL Admin on the SQL MI.
100+
2. User Managed Identity is confirmed as SQL Admin on the SQL MI, and this is deployed using ARM, BICEP, Terraform or other deployment solution.
101+
102+
**Resolution**: Ensure that the User Managed Identity is deployed using the AppId and not the ObjectId. You can confirm if this is applicable by navigating to the SQL MI, Microsoft Entra ID admin pane. Check if the guid that is listed with the User Managed Identity is the ObjectId or AppId of the Service Principal. When this is the ObjectId:
103+
- Set it using the portal
104+
- Redeploy with your preferred solution using the AppId.
105+
95106
## Scenario: Deploy Reports on Power BI
96107

97108
### Issue: SQL Managed Instance isn't reachable

0 commit comments

Comments
 (0)