Skip to content

Commit d528fa3

Browse files
Merge pull request #272883 from SnehaSudhirG/21Apr-TSGUpdate
added new scenario
2 parents 72fc645 + 1db746b commit d528fa3

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

articles/automation/troubleshoot/managed-identity.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,29 @@ title: Troubleshoot Azure Automation managed identity issues
33
description: This article tells how to troubleshoot and resolve issues when using a managed identity with an Automation account.
44
services: automation
55
ms.subservice:
6-
ms.date: 10/26/2021
6+
ms.date: 04/22/2024
77
ms.topic: troubleshooting
88
---
99

1010
# Troubleshoot Azure Automation managed identity issues
1111

1212
This article discusses solutions to problems that you might encounter when you use a managed identity with your Automation account. For general information about using managed identity with Automation accounts, see [Azure Automation account authentication overview](../automation-security-overview.md#managed-identities).
1313

14+
15+
## Scenario: Runbook with system assigned managed identity fails with 400 error message
16+
17+
### Issue
18+
19+
Runbook with system assigned managed identity fails with the error as `unable to acquire for tenant organizations with error ManagedIdentityCredential authentication failed. Managed System Identity not found! Status 400 (Bad Request)`
20+
21+
22+
### Cause
23+
You haven't assigned permissions after creating the system-assigned managed identity.
24+
25+
### Resolution
26+
Ensure to assign the appropriate permissions for system-assigned managed identity. [Using a system-assigned managed identity for an Azure Automation account](../enable-managed-identity-for-automation.md)
27+
28+
1429
## Scenario: Managed Identity in a Runbook cannot authenticate against Azure
1530

1631
### Issue

0 commit comments

Comments
 (0)