Skip to content

Commit 4b24adf

Browse files
authored
Merge pull request #264255 from KarlErickson/karler-entra-fixes
fixes for Microsoft Entra
2 parents 884fa04 + c2e624e commit 4b24adf

15 files changed

+36
-36
lines changed

articles/spring-apps/connect-managed-identity-to-azure-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -115,5 +115,5 @@ Rebuild the app and deploy it to the Azure Spring Apps provisioned in the second
115115

116116
* [How to access Storage blob with managed identity in Azure Spring Apps](https://github.com/Azure-Samples/azure-spring-apps-samples/tree/main/managed-identity-storage-blob)
117117
* [How to enable system-assigned managed identity for applications in Azure Spring Apps](./how-to-enable-system-assigned-managed-identity.md)
118-
* [Learn more about managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md)
118+
* [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
119119
* [Authenticate Azure Spring Apps with Key Vault in GitHub Actions](./github-actions-key-vault.md)

articles/spring-apps/expose-apps-gateway-end-to-end-tls.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -184,9 +184,9 @@ az network public-ip create \
184184
--sku Standard
185185
```
186186

187-
## Create a Managed Identity for Application Gateway
187+
## Create a managed identity for Application Gateway
188188

189-
Application Gateway will need to be able to access Key Vault to read the certificate. To do so, it will use a User-assigned [Managed Identity](../active-directory/managed-identities-azure-resources/overview.md). Create the Managed Identity by using the following command:
189+
Application Gateway will need to be able to access Key Vault to read the certificate. To do so, it will use a user-assigned [managed identity](/entra/identity/managed-identities-azure-resources/overview). Create the managed identity by using the following command:
190190

191191
```azurecli
192192
export APPGW_IDENTITY_NAME='name-for-appgw-managed-identity'
@@ -195,7 +195,7 @@ az identity create \
195195
--name $APPGW_IDENTITY_NAME
196196
```
197197

198-
Then fetch the objectId for the Managed Identity as it will be used later on to give rights to access the certificate in Key Vault:
198+
Then fetch the objectId for the managed identity as it will be used later on to give rights to access the certificate in Key Vault:
199199

200200
```azurecli
201201
export APPGW_IDENTITY_CLIENTID=$(az identity show \
@@ -211,7 +211,7 @@ export APPGW_IDENTITY_OID=$(az ad sp show \
211211

212212
## Set policy on Key Vault
213213

214-
Configure Key Vault using the following command so that the Managed Identity for Application Gateway is allowed to access the certificate stored in Key Vault:
214+
Configure Key Vault using the following command so that the managed identity for Application Gateway is allowed to access the certificate stored in Key Vault:
215215

216216
```azurecli
217217
az keyvault set-policy \
@@ -224,7 +224,7 @@ az keyvault set-policy \
224224

225225
## Create Application Gateway
226226

227-
Create an application gateway using `az network application-gateway create` and specify your application's private fully qualified domain name (FQDN) as servers in the backend pool. Make sure to use the user-assigned Managed Identity and to point to the certificate in Key Vault using the certificate's Secret ID. Then update the HTTP setting using `az network application-gateway http-settings update` to use the public host name.
227+
Create an application gateway using `az network application-gateway create` and specify your application's private fully qualified domain name (FQDN) as servers in the backend pool. Make sure to use the user-assigned managed identity and to point to the certificate in Key Vault using the certificate's Secret ID. Then update the HTTP setting using `az network application-gateway http-settings update` to use the public host name.
228228

229229
```azurecli
230230
export APPGW_NAME='name-for-application-gateway'

articles/spring-apps/expose-apps-gateway-tls-termination.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ az network public-ip create \
105105

106106
### Create a managed identity for the application gateway
107107

108-
Your application gateway will need to be able to access Key Vault to read the certificate. To do this, the application gateway will use a user-assigned managed identity. For more information, see [What are managed identities for Azure resources?](../active-directory/managed-identities-azure-resources/overview.md). Create the managed identity by using the following command, replacing the *\<...>* placeholder:
108+
Your application gateway will need to be able to access Key Vault to read the certificate. To do this, the application gateway will use a user-assigned managed identity. For more information, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview) Create the managed identity by using the following command, replacing the *\<...>* placeholder:
109109

110110
```azurecli
111111
export APPGW_IDENTITY_NAME='<name-for-appgw-managed-identity>'

articles/spring-apps/how-to-enable-system-assigned-managed-identity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Managed identities for Azure resources provide an automatically managed identity
2424

2525
## Prerequisites
2626

27-
If you're unfamiliar with managed identities for Azure resources, see the [Managed identities for Azure resources overview section](../active-directory/managed-identities-azure-resources/overview.md).
27+
If you're unfamiliar with managed identities for Azure resources, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
2828

2929
::: zone pivot="sc-enterprise"
3030

@@ -91,9 +91,9 @@ az spring app identity assign \
9191

9292
An app can use its managed identity to get tokens to access other resources protected by Microsoft Entra ID, such as Azure Key Vault. These tokens represent the application accessing the resource, not any specific user of the application.
9393

94-
You may need to [configure the target resource to allow access from your application](../active-directory/managed-identities-azure-resources/howto-assign-access-portal.md). For example, if you request a token to access Key Vault, make sure you have added an access policy that includes your application's identity. Otherwise, your calls to Key Vault are rejected, even if they include the token. To learn more about which resources support Microsoft Entra tokens, see [Azure services that support Microsoft Entra authentication](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md#azure-services-that-support-azure-ad-authentication).
94+
You may need to [configure the target resource to allow access from your application](/entra/identity/managed-identities-azure-resources/howto-assign-access-portal). For example, if you request a token to access Key Vault, make sure you have added an access policy that includes your application's identity. Otherwise, your calls to Key Vault are rejected, even if they include the token. To learn more about which resources support Microsoft Entra tokens, see [Azure services that can use managed identities to access other services](/entra/identity/managed-identities-azure-resources/managed-identities-status).
9595

96-
Azure Spring Apps shares the same endpoint for token acquisition with Azure Virtual Machine. We recommend using Java SDK or spring boot starters to acquire a token. See [How to use VM token](../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md) for various code and script examples and guidance on important topics such as handling token expiration and HTTP errors.
96+
Azure Spring Apps shares the same endpoint for token acquisition with Azure Virtual Machine. We recommend using Java SDK or spring boot starters to acquire a token. See [How to use VM token](/entra/identity/managed-identities-azure-resources/how-to-use-vm-token) for various code and script examples and guidance on important topics such as handling token expiration and HTTP errors.
9797

9898
## Disable system-assigned identity from an app
9999

@@ -135,5 +135,5 @@ az ad sp show --id <object-ID> --query appId
135135

136136
## Next steps
137137

138-
* [Learn more about managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md)
138+
* [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
139139
* [How to use managed identities with Java SDK](https://github.com/Azure-Samples/azure-spring-apps-samples)

articles/spring-apps/how-to-manage-user-assigned-managed-identities.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@ Managed identities for Azure resources provide an automatically managed identity
2323

2424
## Prerequisites
2525

26-
- If you're unfamiliar with managed identities for Azure resources, see the [Managed identities for Azure resources overview section](../active-directory/managed-identities-azure-resources/overview.md).
26+
- If you're unfamiliar with managed identities for Azure resources, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
2727

2828
::: zone pivot="sc-enterprise"
2929

3030
- An already provisioned Azure Spring Apps Enterprise plan instance. For more information, see [Quickstart: Build and deploy apps to Azure Spring Apps using the Enterprise plan](quickstart-deploy-apps-enterprise.md).
3131
- [Azure CLI version 2.45.0 or higher](/cli/azure/install-azure-cli).
3232
- [!INCLUDE [install-app-user-identity-extension](includes/install-app-user-identity-extension.md)]
33-
- At least one already provisioned user-assigned managed identity. For more information, see [Manage user-assigned managed identities](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md).
33+
- At least one already provisioned user-assigned managed identity. For more information, see [Manage user-assigned managed identities](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities).
3434

3535
::: zone-end
3636

@@ -39,7 +39,7 @@ Managed identities for Azure resources provide an automatically managed identity
3939
- An already provisioned Azure Spring Apps instance. For more information, see [Quickstart: Deploy your first application to Azure Spring Apps](./quickstart.md).
4040
- [Azure CLI version 2.45.0 or higher](/cli/azure/install-azure-cli).
4141
- [!INCLUDE [install-app-user-identity-extension](includes/install-app-user-identity-extension.md)]
42-
- At least one already provisioned user-assigned managed identity. For more information, see [Manage user-assigned managed identities](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md).
42+
- At least one already provisioned user-assigned managed identity. For more information, see [Manage user-assigned managed identities](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities).
4343

4444
::: zone-end
4545

@@ -87,9 +87,9 @@ az spring app identity assign \
8787

8888
An application can use its managed identity to get tokens to access other resources protected by Microsoft Entra ID, such as Azure Key Vault. These tokens represent the application accessing the resource, not any specific user of the application.
8989

90-
You may need to configure the target resource to allow access from your application. For more information, see [Assign a managed identity access to a resource by using the Azure portal](../active-directory/managed-identities-azure-resources/howto-assign-access-portal.md). For example, if you request a token to access Key Vault, be sure you've added an access policy that includes your application's identity. Otherwise, your calls to Key Vault are rejected, even if they include the token. To learn more about which resources support Microsoft Entra tokens, see [Azure services that support Microsoft Entra authentication](../active-directory/managed-identities-azure-resources/services-azure-active-directory-support.md)
90+
You may need to configure the target resource to allow access from your application. For more information, see [Assign a managed identity access to a resource by using the Azure portal](/entra/identity/managed-identities-azure-resources/howto-assign-access-portal). For example, if you request a token to access Key Vault, be sure you've added an access policy that includes your application's identity. Otherwise, your calls to Key Vault are rejected, even if they include the token. To learn more about which resources support Microsoft Entra tokens, see [Azure services that support Microsoft Entra authentication](/entra/identity/managed-identities-azure-resources/services-id-authentication-support)
9191

92-
Azure Spring Apps shares the same endpoint for token acquisition with Azure Virtual Machines. We recommend using Java SDK or Spring Boot starters to acquire a token. For various code and script examples, and guidance on important topics such as handling token expiration and HTTP errors, see [How to use managed identities for Azure resources on an Azure VM to acquire an access token](../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md).
92+
Azure Spring Apps shares the same endpoint for token acquisition with Azure Virtual Machines. We recommend using Java SDK or Spring Boot starters to acquire a token. For various code and script examples, and guidance on important topics such as handling token expiration and HTTP errors, see [How to use managed identities for Azure resources on an Azure VM to acquire an access token](/entra/identity/managed-identities-azure-resources/how-to-use-vm-token).
9393

9494
## Remove user-assigned managed identities from an existing app
9595

@@ -123,5 +123,5 @@ For user-assigned managed identity limitations, see [Quotas and service plans fo
123123

124124
## Next steps
125125

126-
- [Learn more about managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md)
126+
- [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
127127
- [How to use managed identities with Java SDK](https://github.com/Azure-Samples/azure-spring-apps-samples)

articles/spring-apps/how-to-outbound-public-ip.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,5 +51,5 @@ az spring show --resource-group <group_name> --name <service_name> --query prope
5151

5252
## Next steps
5353

54-
* [Learn more about managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md)
54+
* [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
5555
* [Learn more about key vault in Azure Spring Apps](./tutorial-managed-identities-key-vault.md)

articles/spring-apps/how-to-set-up-sso-with-azure-ad.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Register your application to establish a trust relationship between your app and
5353
1. In *Redirect URI (optional)* select **Web**, then enter the URL from the above section in the text box. The redirect URI is the location where Microsoft Entra ID redirects your client and sends security tokens after authentication.
5454
1. Select **Register** to finish registering the application.
5555

56-
:::image type="content" source="./media/how-to-setup-sso-with-azure-ad/sso-create-app-registration.png" alt-text="Screenshot of how to fill out the Add App Registration screen." lightbox="./media/how-to-setup-sso-with-azure-ad/sso-create-app-registration.png":::
56+
:::image type="content" source="media/how-to-set-up-sso-with-azure-ad/sso-create-app-registration.png" alt-text="Screenshot of how to fill out the Add App Registration screen." lightbox="media/how-to-set-up-sso-with-azure-ad/sso-create-app-registration.png":::
5757

5858
When registration finishes, you'll see the *Application (client) ID* on the **Overview** screen of the *App registrations** page.
5959

@@ -65,9 +65,9 @@ You can also add redirect URIs after app registration by following these steps:
6565
1. Select **Web**, then select **Add URI** under *Redirect URIs*.
6666
1. Add a new redirect URI, then select **Save**.
6767

68-
:::image type="content" source="./media/how-to-setup-sso-with-azure-ad/sso-redirect-uri.png" alt-text="Screenshot of adding a redirect U R I to the authentication screen." lightbox="./media/how-to-setup-sso-with-azure-ad/sso-redirect-uri.png":::
68+
:::image type="content" source="media/how-to-set-up-sso-with-azure-ad/sso-redirect-uri.png" alt-text="Screenshot of adding a redirect U R I to the authentication screen." lightbox="media/how-to-set-up-sso-with-azure-ad/sso-redirect-uri.png":::
6969

70-
For more information on Application Registration, see [Quickstart: Register an app in the Microsoft identity platform ](../active-directory/develop/quickstart-register-app.md#quickstart-register-an-application-with-the-microsoft-identity-platform).
70+
For more information on Application Registration, see [Quickstart: Register an application with the Microsoft identity platform](/entra/identity-platform/quickstart-register-app).
7171

7272
## Add a client secret
7373

@@ -83,7 +83,7 @@ The application uses a client secret to authenticate itself in SSO workflow. You
8383
8484
## Configure scope
8585

86-
The `scope` property of SSO is a list of scopes to be included in JWT identity tokens. They're often referred to permissions. Identity platform supports several [OpenID Connect scopes](../active-directory/develop/v2-permissions-and-consent.md#openid-connect-scopes), such as `openid`, `email` and `profile`.
86+
The `scope` property of SSO is a list of scopes to be included in JWT identity tokens. They're often referred to permissions. Identity platform supports several OpenID Connect scopes, such as `openid`, `email` and `profile`. For more information, see the [OpenID Connect scopes](/entra/identity-platform/scopes-oidc#openid-connect-scopes) section of [Scopes and permissions in the Microsoft identity platform](/entra/identity-platform/scopes-oidc).
8787

8888
## Configure issuer URI
8989

articles/spring-apps/how-to-use-managed-identities.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ For user-assigned managed identities, see [How to assign and remove user-assigne
3838

3939
An application can use its managed identity to get tokens to access other resources protected by Microsoft Entra ID, such as Azure Key Vault. These tokens represent the application accessing the resource, not any specific user of the application.
4040

41-
You can configure the target resource to allow access from your application. For more information, see [Assign a managed identity access to a resource by using the Azure portal](/entra/identity/managed-identities-azure-resources/howto-assign-access-portal). For example, if you request a token to access Key Vault, be sure you have added an access policy that includes your application's identity. Otherwise, your calls to Key Vault will be rejected, even if they include the token. To learn more about which resources support Microsoft Entra tokens, see [Azure services that support Microsoft Entra authentication](/entra/identity/managed-identities-azure-resources/services-id-authentication-support.
41+
You can configure the target resource to allow access from your application. For more information, see [Assign a managed identity access to a resource by using the Azure portal](/entra/identity/managed-identities-azure-resources/howto-assign-access-portal). For example, if you request a token to access Key Vault, be sure you have added an access policy that includes your application's identity. Otherwise, your calls to Key Vault will be rejected, even if they include the token. To learn more about which resources support Microsoft Entra tokens, see [Azure services that support Microsoft Entra authentication](/entra/identity/managed-identities-azure-resources/services-id-authentication-support).
4242

4343
Azure Spring Apps shares the same endpoint for token acquisition with Azure Virtual Machines. We recommend using Java SDK or Spring Boot starters to acquire a token. For various code and script examples, as well as guidance on important topics like handling token expiration and HTTP errors, see [How to use managed identities for Azure resources on an Azure VM to acquire an access token](/entra/identity/managed-identities-azure-resources/how-to-use-vm-token).
4444

@@ -75,5 +75,5 @@ The following table shows the mappings between concepts in Managed Identity scop
7575

7676
## Next steps
7777

78-
- [Learn more about managed identities for Azure resources](/entra/identity/managed-identities-azure-resources/overview)
78+
- [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
7979
- [How to use managed identities with Java SDK](https://github.com/Azure-Samples/azure-spring-apps-samples)

0 commit comments

Comments
 (0)