You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/troubleshoot/managed-identity.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.topic: troubleshooting
11
11
12
12
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).
13
13
14
-
## Scenario: Use a Managed Identity in a Runbook and it cannot authenticate against Azure
14
+
## Scenario: Managed Identity in a Runbook cannot authenticate against Azure
15
15
16
16
### Issue
17
17
When using a Managed Identity in your runbook, you receive an error as:
@@ -21,9 +21,9 @@ When using a Managed Identity in your runbook, you receive an error as:
21
21
22
22
This can happen either when:
23
23
24
-
-**Cause 1**: You use the Automation account System Managed Identity, which has not yet been created and the `Code Connect-AzAccount -Identity`, tries to authenticate to Azure and run a runbook in Azure or on a Hybrid Runbook Worker.
24
+
-**Cause 1**: You use the Automation account System Managed Identity, which has not yet been created and the `Code Connect-AzAccount -Identity` tries to authenticate to Azure and run a runbook in Azure or on a Hybrid Runbook Worker.
25
25
26
-
-**Cause 2**: The Automation account has a User managed identity assigned and not a System Managed Identity and the - `Code Connect-AzAccount -Identity`, tries to authenticate to Azure and run a runbook on an Azure virtual machine Hybrid Runbook Worker using the Azure VM System Managed Identity.
26
+
-**Cause 2**: The Automation account has a User managed identity assigned and not a System Managed Identity and the - `Code Connect-AzAccount -Identity` tries to authenticate to Azure and run a runbook on an Azure virtual machine Hybrid Runbook Worker using the Azure VM System Managed Identity.
27
27
28
28
29
29
### Resolution
@@ -32,8 +32,8 @@ This can happen either when:
32
32
33
33
-**Resolution 2**: As appropriate for your requirements, you can:
34
34
35
-
- Create the Automation Account System Managed Identity and use it to authenticate.
36
-
Or
35
+
- Create the Automation Account System Managed Identity and use it to authenticate.</br>
36
+
Or </br>
37
37
- Delete the Automation Account User Assigned Managed Identity.
0 commit comments