Skip to content

Commit 814c58f

Browse files
committed
minor edits
1 parent 5a54c61 commit 814c58f

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/automation/troubleshoot/managed-identity.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.topic: troubleshooting
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-
## 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
1515

1616
### Issue
1717
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:
2121

2222
This can happen either when:
2323

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.
2525

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.
2727

2828

2929
### Resolution
@@ -32,8 +32,8 @@ This can happen either when:
3232

3333
- **Resolution 2**: As appropriate for your requirements, you can:
3434

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>
3737
- Delete the Automation Account User Assigned Managed Identity.
3838

3939

0 commit comments

Comments
 (0)