Skip to content

Commit c0174d3

Browse files
authored
Merge pull request #110807 from SteveBurkettNZ/patch-39
Fix Log Analytics workspace branding
2 parents a57e13a + ef12cd0 commit c0174d3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automanage/overview-about.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ There are several prerequisites to consider before trying to enable Azure Automa
4646
Please visit [this page](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?regions=all&products=all) to view which regions Automanage supports.
4747

4848
> [!NOTE]
49-
> If the machine is connected to a log analytics workspace, the log analytics workspace must be located in one of the supported regions listed above.
49+
> If the machine is connected to a Log Analytics workspace, the Log Analytics workspace must be located in one of the supported regions listed above.
5050
5151
### Required RBAC permissions
5252
To onboard, Automanage requires slightly different RBAC roles depending on whether you are enabling Automanage for the first time in a subscription.
@@ -80,4 +80,4 @@ In this article, you learned that Automanage for machines provides a means for w
8080
Try enabling Automanage for Azure virtual machines or Arc-enabled servers in the Azure portal.
8181

8282
> [!div class="nextstepaction"]
83-
> [Enable Automanage for virtual machines in the Azure portal](virtual-machines-custom-profile.md)
83+
> [Enable Automanage for virtual machines in the Azure portal](virtual-machines-custom-profile.md)

0 commit comments

Comments
 (0)