Skip to content

Commit a0cbe9b

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-data-flow
2 parents b0404cf + a0977b2 commit a0cbe9b

File tree

987 files changed

+5004
-5237
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

987 files changed

+5004
-5237
lines changed

.openpublishing.redirection.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5923,6 +5923,16 @@
59235923
"source_path_from_root": "/articles/reliability/reliability-hdinsight-on-aks.md",
59245924
"redirect_url": "/azure/reliability/overview-reliability-guidance",
59255925
"redirect_document_id": false
5926+
},
5927+
{
5928+
"source_path_from_root": "/articles/managed-grafana/concept-role-based-access-control.md",
5929+
"redirect_url": "/azure/managed-grafana/how-to-manage-access-permissions-users-identities",
5930+
"redirect_document_id": false
5931+
},
5932+
{
5933+
"source_path_from_root": "/articles/managed-grafana/how-to-share-grafana-workspace.md",
5934+
"redirect_url": "/azure/managed-grafana/how-to-manage-access-permissions-users-identities",
5935+
"redirect_document_id": false
59265936
}
59275937
]
59285938
}

articles/app-service/configure-authentication-oauth-tokens.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ From your client code (such as a mobile app or in-browser JavaScript), send an H
3737
When your provider's access token (not the [session token](#extend-session-token-expiration-grace-period)) expires, you need to reauthenticate the user before you use that token again. You can avoid token expiration by making a `GET` call to the `/.auth/refresh` endpoint of your application. When called, App Service automatically refreshes the access tokens in the [token store](overview-authentication-authorization.md#token-store) for the authenticated user. Subsequent requests for tokens by your app code get the refreshed tokens. However, for token refresh to work, the token store must contain [refresh tokens](/entra/identity-platform/refresh-tokens) for your provider. The way to get refresh tokens are documented by each provider, but the following list is a brief summary:
3838

3939
- **Google**: Append an `access_type=offline` query string parameter to your `/.auth/login/google` API call. For more information, see [Google Refresh Tokens](https://developers.google.com/identity/protocols/OpenIDConnect#refresh-tokens).
40-
- **Facebook**: Doesn't provide refresh tokens. Long-lived tokens expire in 60 days (see [Facebook Expiration and Extension of Access Tokens](https://developers.facebook.com/docs/facebook-login/access-tokens/expiration-and-extension)).
40+
- **Facebook**: Doesn't provide refresh tokens. Long-lived tokens expire in 60 days (see [Long-Lived Access Tokens](https://developers.facebook.com/docs/facebook-login/guides/access-tokens/get-long-lived/)).
4141
- **X**: Access tokens don't expire (see [OAuth FAQ](https://developer.x.com/en/docs/authentication/faq)).
4242
- **Microsoft**: In [https://resources.azure.com](https://resources.azure.com), do the following steps:
4343
1. At the top of the page, select **Read/Write**.

articles/app-service/deploy-staging-slots.md

Lines changed: 99 additions & 94 deletions
Large diffs are not rendered by default.

articles/app-service/environment/zone-redundancy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ To make your apps zone redundant, you need to deploy two zonal ILB ASEs. The two
8989

9090
ILB ASEs deployed in an availability zone will only store customer data within the region where the zonal ILB ASE has been deployed. Both website file content and customer supplied settings and secrets stored in App Service remain within the region where the zonal ILB ASE is deployed.
9191

92-
Customers ensure single region data residency by following the steps outlined earlier in the section "How to Deploy an App Service Environment in an Availability Zone". By configuring an App Service Environment according to these steps, an App Service Environment deployed in an availability zone satisfies in region data residency requirements including those specified in the [Azure Trust Center](https://azuredatacentermap.azurewebsites.net/).
92+
Customers ensure single region data residency by following the steps outlined earlier in the section "How to Deploy an App Service Environment in an Availability Zone". By configuring an App Service Environment according to these steps, an App Service Environment deployed in an availability zone satisfies in region data residency requirements including those specified in the [Microsoft Datacenters Explorer](https://datacenters.microsoft.com/globe/explore).
9393

9494
Customers can validate that an App Service Environment is properly configured to store data in a single region by following these steps:
9595

-42.4 KB
Loading
-45.7 KB
Loading
-52.8 KB
Loading
12.6 KB
Loading
-38.9 KB
Loading
-2.59 KB
Loading

0 commit comments

Comments
 (0)