Skip to content

Commit 6fb4894

Browse files
committed
fix links
Signed-off-by: Troy Connor <[email protected]>
1 parent ab98e52 commit 6fb4894

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/operator-nexus/howto-create-cluster-with-user-assigned-managed-identity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To create a cluster without a service principal user name and password, you can
1919
1. Install the latest version of the
2020
[appropriate CLI extensions](./howto-install-cli-extensions.md)
2121
1. A Log Analytics Workspace
22-
1. A user-assigned managed identity resource with permissions over the log analytics workspace of [Log Analytics Contributor](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/analytics#log-analytics-contributor).
22+
1. A user-assigned managed identity resource with permissions over the log analytics workspace of [Log Analytics Contributor](/azure/role-based-access-control/built-in-roles/analytics#log-analytics-contributor).
2323

2424
> [!NOTE]
2525
> This functionality exists with the latest GA API offered by Azure Operator Nexus
@@ -29,7 +29,7 @@ To create a cluster without a service principal user name and password, you can
2929

3030
1. Create a Log Analytics Workspace [Create a Log Analytics Workspace](/azure/azure-monitor/logs/quick-create-workspace).
3131
1. Assign the "Log Analytics Contributor" role to users and managed identities which need access to the Log Analytics Workspace.
32-
1. See [Assign an Azure role for access to the analytics Workspace](azure/azure-monitor/logs/manage-access?tabs=portal#azure-rbac). The role must also be assigned to either a user-assigned managed identity or the cluster's own system-assigned managed identity.
32+
1. See [Assign an Azure role for access to the analytics Workspace](/azure/azure-monitor/logs/manage-access?tabs=portal#azure-rbac). The role must also be assigned to either a user-assigned managed identity or the cluster's own system-assigned managed identity.
3333
1. For more information on managed identities, see [Managed identities for Azure resources](/entra/identity/managed-identities-azure-resources/overview).
3434
1. If using the Cluster's system assigned identity, the system assigned identity needs to be added to the cluster before it can be granted access.
3535
1. When assigning a role to the cluster's system-assigned identity, make sure you select the resource with the type "Cluster (Operator Nexus)."

0 commit comments

Comments
 (0)