From c9eb06eb972190a281537c2a98928bd5eb3dfcda Mon Sep 17 00:00:00 2001 From: Steven Masley Date: Tue, 31 Dec 2024 06:17:59 -0500 Subject: [PATCH] chore: remove dead link to azure docs issues (#15982) --- docs/admin/users/idp-sync.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/admin/users/idp-sync.md b/docs/admin/users/idp-sync.md index bb2d48d4a0..a28407c0ce 100644 --- a/docs/admin/users/idp-sync.md +++ b/docs/admin/users/idp-sync.md @@ -62,9 +62,9 @@ There are two ways you can configure group sync: On login, users will automatically be assigned to groups that have matching names in Coder and removed from groups that the user no longer belongs to. -For cases when an OIDC provider only returns group IDs ([Azure AD][azure-gids]) -or you want to have different group names in Coder than in your OIDC provider, -you can configure mapping between the two with the +For cases when an OIDC provider only returns group IDs or you want to have +different group names in Coder than in your OIDC provider, you can configure +mapping between the two with the [OIDC group mapping](../../reference/cli/server.md#--oidc-group-mapping) server flag: @@ -93,9 +93,6 @@ coder: From the example above, users that belong to the `myOIDCGroupID` group in your OIDC provider will be added to the `myCoderGroupName` group in Coder. -[azure-gids]: - https://github.com/MicrosoftDocs/azure-docs/issues/59766#issuecomment-664387195 - ## Runtime (Organizations)