Merge pull request #206636 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: ttorble

articles/active-directory/external-identities/whats-new-docs.md

@@ -1,7 +1,7 @@
 ---
 title: "What's new in Azure Active Directory External Identities"
 description: "New and updated documentation for the Azure Active Directory External Identities."
-ms.date: 07/01/2022
+ms.date: 08/01/2022
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: reference
@@ -15,6 +15,18 @@ manager: CelesteDG
 
 Welcome to what's new in Azure Active Directory External Identities documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the External Identities service, see [What's new in Azure Active Directory](../fundamentals/whats-new.md).
 
+## July 2022
+
+### Updated articles
+
+- [Configure cross-tenant access settings for B2B collaboration](cross-tenant-access-settings-b2b-collaboration.md)
+- [Configure cross-tenant access settings for B2B direct connect](cross-tenant-access-settings-b2b-direct-connect.md)
+- [Add Google as an identity provider for B2B guest users](google-federation.md)
+- [Azure Active Directory External Identities: What's new](whats-new-docs.md)
+- [Overview: Cross-tenant access with Azure AD External Identities](cross-tenant-access-overview.md)
+- [B2B direct connect overview](b2b-direct-connect-overview.md)
+- [Azure Active Directory B2B collaboration invitation redemption](redemption-experience.md)
+
 ## June 2022
 
 ### Updated articles
@@ -57,19 +69,3 @@ Welcome to what's new in Azure Active Directory External Identities documentatio
 - [Azure AD B2B in government and national clouds](b2b-government-national-clouds.md)
 - [External Identities in Azure Active Directory](external-identities-overview.md)
 - [Troubleshooting Azure Active Directory B2B collaboration](troubleshoot.md)
-
-## April 2022
-
-### Updated articles
-
-- [Email one-time passcode authentication](one-time-passcode.md)
-- [Configure external collaboration settings](external-collaboration-settings-configure.md)
-- [Add a self-service sign-up user flow to an app](self-service-sign-up-user-flow.md)
-- [B2B direct connect overview](b2b-direct-connect-overview.md)
-- [Azure Active Directory B2B collaboration invitation redemption](redemption-experience.md)
-- [Federation with SAML/WS-Fed identity providers for guest users (preview)](direct-federation.md)
-- [Azure Active Directory External Identities: What's new](whats-new-docs.md)
-- [Azure Active Directory B2B best practices](b2b-fundamentals.md)
-- [Troubleshooting Azure Active Directory B2B collaboration](troubleshoot.md)
-- [Properties of an Azure Active Directory B2B collaboration user](user-properties.md)
-- [B2B collaboration overview](what-is-b2b.md)

articles/api-management/api-management-transformation-policies.md

@@ -258,7 +258,7 @@ The XML response to the client will be:
 or
 
 ```xml
-<set-backend-service backend-id="identifier of the backend entity specifying base URL of the backend service" />
+<set-backend-service backend-id="name of the backend entity specifying base URL of the backend service" />
 ```
 
 > [!NOTE]
@@ -317,7 +317,7 @@ In this example the policy routes the request to a service fabric backend, using
 |Name|Description|Required|Default|
 |----------|-----------------|--------------|-------------|
 |base-url|New backend service base URL.|One of `base-url` or `backend-id` must be present.|N/A|
-|backend-id|Identifier of the backend to route to. (Backend entities are managed via [Azure portal](how-to-configure-service-fabric-backend.md), [API](/rest/api/apimanagement), and [PowerShell](https://www.powershellgallery.com/packages?q=apimanagement).)|One of `base-url` or `backend-id` must be present.|N/A|
+|backend-id|Identifier (name) of the backend to route to. (Backend entities are managed via [Azure portal](how-to-configure-service-fabric-backend.md), [API](/rest/api/apimanagement), and [PowerShell](https://www.powershellgallery.com/packages?q=apimanagement).)|One of `base-url` or `backend-id` must be present.|N/A|
 |sf-partition-key|Only applicable when the backend is a Service Fabric service and is specified using 'backend-id'. Used to resolve a specific partition from the name resolution service.|No|N/A|
 |sf-replica-type|Only applicable when the backend is a Service Fabric service and is specified using 'backend-id'. Controls if the request should go to the primary or secondary replica of a partition. |No|N/A|
 |sf-resolve-condition|Only applicable when the backend is a Service Fabric service. Condition identifying if the call to Service Fabric backend has to be repeated with new resolution.|No|N/A|

articles/api-management/backends.md

@@ -31,7 +31,7 @@ Custom backends require extra configuration to authorize the credentials of re
 After creating a backend, you can reference the backend in your APIs. Use the [`set-backend-service`](api-management-transformation-policies.md#SetBackendService) policy to redirect an incoming API request to the custom backend instead of the default backend for that API.
 
 > [!NOTE]
-> When you use the `set-backend-service` policy to redirect requests to a custom backend, refer to the backend by its identifier (`backend-id`), not by its URL.
+> When you use the `set-backend-service` policy to redirect requests to a custom backend, refer to the backend by its name (`backend-id`), not by its URL.
 
 ## Benefits of backends
 

articles/applied-ai-services/form-recognizer/disaster-recovery.md

@@ -31,10 +31,73 @@ If your app or business depends on the use of a Form Recognizer custom model, we
 
 The process for copying a custom model consists of the following steps:
 
-1. First you issue a copy authorization request to the target resource—that is, the resource that will receive the copied model. You get back the URL of the newly created target model, which will receive the copied data.
-1. Next you send the copy request to the source resource—the resource that contains the model to be copied. You'll get back a URL that you can query to track the progress of the operation.
+1. First you issue a copy authorization request to the target resource—that is, the resource that will receive the copied model. You get back the URL of the newly created target model, which will receive the copied model.
+1. Next you send the copy request to the source resource—the resource that contains the model to be copied with the payload (copy authorization) returned from the previous call. You'll get back a URL that you can query to track the progress of the operation.
 1. You'll use your source resource credentials to query the progress URL until the operation is a success. You can also query the new model ID in the target resource to get the status of the new model.
 
+# [Form Recognizer v3.0 (Preview)](#tab/v30)
+
+## Generate Copy authorization request
+
+The following HTTP request gets copy authorization from your target resource. You'll need to enter the endpoint and key of your target resource as headers.
+
+```
+POST https://{TARGET_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecognizer/documentModels:authorizeCopy?api-version=2022-06-30-preview
+Ocp-Apim-Subscription-Key: {TARGET_FORM_RECOGNIZER_RESOURCE_KEY}
+```
+Request body
+```json
+{
+  "modelId": "target-model-name",
+  "description": "Copied from SCUS"
+}
+```
+
+You'll get a `200` response code with response body that contains the JSON payload required to initiate the copy.
+
+```
+{
+    "targetResourceId": "/subscriptions/{targetSub}/resourceGroups/{targetRG}/providers/Microsoft.CognitiveServices/accounts/{targetService}",
+    "targetResourceRegion": "region",
+    "targetModelId": "target-model-name",
+    "targetModelLocation": "model path",
+    "accessToken": "access token",
+    "expirationDateTime": "timestamp"
+}
+```
+
+## Start Copy operation
+
+The following HTTP request starts the copy operation on the source resource. You'll need to enter the endpoint and key of your source resource as the url and header. Notice that the request URL contains the model ID of the source model you want to copy.
+
+```
+POST {{source-endpoint}}formrecognizer/documentModels/{model-to-be-copied}:copyTo?api-version=2022-06-30-preview
+Ocp-Apim-Subscription-Key: {SOURCE_FORM_RECOGNIZER_RESOURCE_KEY}
+```
+
+The body of your request is the response from the previous step.
+
+```json
+{
+    "targetResourceId": "/subscriptions/{targetSub}/resourceGroups/{targetRG}/providers/Microsoft.CognitiveServices/accounts/{targetService}",
+    "targetResourceRegion": "region",
+    "targetModelId": "target-model-name",
+    "targetModelLocation": "model path",
+    "accessToken": "access token",
+    "expirationDateTime": "timestamp"
+}
+```
+
+You'll get a `202\Accepted` response with an Operation-Location header. This value is the URL that you'll use to track the progress of the operation. Copy it to a temporary location for the next step.
+
+```
+HTTP/1.1 202 Accepted
+Operation-Location: https://{source-resource}.cognitiveservices.azure.com/formrecognizer/operations/{operation-id}?api-version=2022-06-30-preview
+```
+
+
+# [Form Recognizer v2.1 (GA)](#tab/v21)
+
 ## Generate Copy authorization request
 
 The following HTTP request gets copy authorization from your target resource. You'll need to enter the endpoint and key of your target resource as headers.
@@ -71,16 +134,22 @@ The body of your request needs to have the following format. You'll need to ente
 }
 ```
 
-> [!NOTE]
-> The Copy API transparently supports the [AEK/CMK](https://msazure.visualstudio.com/Cognitive%20Services/_wiki/wikis/Cognitive%20Services.wiki/52146/Customer-Managed-Keys) feature. This doesn't require any special treatment, but note that if you're copying between an unencrypted resource to an encrypted resource, you need to include the request header `x-ms-forms-copy-degrade: true`. If this header is not included, the copy operation will fail and return a `DataProtectionTransformServiceError`.
-
 You'll get a `202\Accepted` response with an Operation-Location header. This value is the URL that you'll use to track the progress of the operation. Copy it to a temporary location for the next step.
 
 ```
 HTTP/1.1 202 Accepted
 Operation-Location: https://{SOURCE_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecognizer/v2.1/custom/models/eccc3f13-8289-4020-ba16-9f1d1374e96f/copyresults/02989ba8-1296-499f-aaf4-55cfff41b8f1
 ```
 
+-----
+
+
+
+> [!NOTE]
+> The Copy API transparently supports the [AEK/CMK](https://msazure.visualstudio.com/Cognitive%20Services/_wiki/wikis/Cognitive%20Services.wiki/52146/Customer-Managed-Keys) feature. This doesn't require any special treatment, but note that if you're copying between an unencrypted resource to an encrypted resource, you need to include the request header `x-ms-forms-copy-degrade: true`. If this header is not included, the copy operation will fail and return a `DataProtectionTransformServiceError`.
+
+
+
 ### Common errors
 
 |Error|Resolution|
@@ -90,6 +159,15 @@ Operation-Location: https://{SOURCE_FORM_RECOGNIZER_RESOURCE_ENDPOINT}/formrecog
 
 ## Track Copy progress
 
+# [Form Recognizer v3.0 (Preview)](#tab/v30)
+
+```
+GET https://{source-resource}.cognitiveservices.azure.com/formrecognizer/operations/{operation-id}?api-version=2022-06-30-preview
+Ocp-Apim-Subscription-Key: {SOURCE_FORM_RECOGNIZER_RESOURCE_KEY}
+```
+
+# [Form Recognizer v2.1 (GA)](#tab/v21)
+
 Track your progress by querying the **Get Copy Model Result** API against the source resource endpoint.
 
 ```
@@ -105,6 +183,10 @@ Content-Type: application/json; charset=utf-8
 {"status":"succeeded","createdDateTime":"2020-04-23T18:18:01.0275043Z","lastUpdatedDateTime":"2020-04-23T18:18:01.0275048Z","copyResult":{}}
 ```
 
+-----
+
+
+
 ### Common errors
 
 |Error|Resolution|

articles/azure-cache-for-redis/cache-how-to-premium-persistence.md

@@ -17,10 +17,18 @@ Azure Cache for Redis offers Redis persistence using the Redis database (RDB) an
 - **RDB persistence** - When you use RDB persistence, Azure Cache for Redis persists a snapshot of your cache in a binary format. The snapshot is saved in an Azure Storage account. The configurable backup frequency determines how often to persist the snapshot. If a catastrophic event occurs that disables both the primary and replica cache, the cache is reconstructed using the most recent snapshot. Learn more about the [advantages](https://redis.io/topics/persistence#rdb-advantages) and [disadvantages](https://redis.io/topics/persistence#rdb-disadvantages) of RDB persistence.
 - **AOF persistence** - When you use AOF persistence, Azure Cache for Redis saves every write operation to a log. The log is saved at least once per second into an Azure Storage account. If a catastrophic event occurs that disables both the primary and replica cache, the cache is reconstructed using the stored write operations. Learn more about the [advantages](https://redis.io/topics/persistence#aof-advantages) and [disadvantages](https://redis.io/topics/persistence#aof-disadvantages) of AOF persistence.
 
-Azure Cache for Redis persistence features are intended to be used to restore data after data loss, not importing it to a new cache. You can't import from AOF page blob backups to a new cache. To export data for importing back to a new cache, use the export RDB feature or automatic recurring RDB export. For more information on importing to a new cache, see [Import](cache-how-to-import-export-data.md#import).
+Azure Cache for Redis persistence features are intended to be used to restore data to the same cache after data loss and the RDB/AOF persisted data files cannot be imported to a new cache.
+
+To move data across caches, use the Import/Export feature. For more information, see [Import and Export data in Azure Cache for Redis](cache-how-to-import-export-data.md).
+
+To generate backup of data that can be added to a new cache, you can write automated scripts using PowerShell or CLI to export data periodically.
 
 > [!NOTE]
-> Importing from AOF page blob backups to a new cache is not a supported option.
+> Persistence features are intended to be used to restore data to the same cache after data loss.
+>
+> - RDB/AOF persisted data files cannot be imported to a new cache.
+> - Use the Import/Export feature to move data across caches.
+> - Write automated scripts using PowerShell or CLI to create a backup of data that can be added to a new cache.
 
 Persistence writes Redis data into an Azure Storage account that you own and manage. You configure the **New Azure Cache for Redis** on the left during cache creation. For existing premium caches, use the **Resource menu**.
 

articles/azure-cache-for-redis/cache-whats-new.md

@@ -25,7 +25,7 @@ The **RediSearch** module is also now available for Azure Cache for Redis. For m
 
 ### Redis 6 becomes default for new cache instances
 
-On November 1, 2022, all the versions of Azure Cache for Redis REST API, PowerShell, Azure CLI, and Azure SDK will create Redis instances using the latest stable version of Redis offered by Azure Cache for Redis by default. Previously, Redis version 4.0 was the default version used. However, as of October 2021, the latest stable Redis version offered in Azure Cache for Redis is 6.0.
+Beginning November 1, 2022, all versions of Azure Cache for Redis REST API, PowerShell, Azure CLI, and Azure SDK will create Redis instances using the latest stable version of Redis offered by Azure Cache for Redis by default. Previously, Redis version 4.0 was the default version used. However, as of October 2021, the latest stable Redis version offered in Azure Cache for Redis is 6.0.
 
 >[!NOTE]
 > This change does not affect any existing instances. It is only applicable to new instances created from November 1, 2022, and onward.