Merge pull request #241541 from MicrosoftDocs/repo_sync_working_branch

Resolve syncing conflicts from repo_sync_working_branch to main

Author: huypub

articles/azure-maps/how-to-create-data-registries.md

@@ -1,16 +1,16 @@
 ---
-title: Create Data Registry (preview)
+title: Create Data Registry
 titleSuffix: Azure Maps
 description: Learn how to create Data Registry.
 author: faterceros
 ms.author: aterceros
-ms.date: 2/14/2023
+ms.date: 6/14/2023
 ms.topic: how-to
 ms.service: azure-maps
 services: azure-maps
 ---
 
-# How to create data registry (preview)
+# How to create data registry
 
 The [data registry] service enables you to register data content in an Azure Storage Account with your Azure Maps account. An example of data might include a collection of Geofences used in the Azure Maps Geofencing service. Another example is ZIP files containing drawing packages (DWG) or GeoJSON files that Azure Maps Creator uses to create or update indoor maps.
 
@@ -221,7 +221,7 @@ To create a data registry:
 1. Once you have the body of your HTTP request ready, execute the following **HTTP PUT request**:
 
     ```http
-    https://us.atlas.microsoft.com/dataRegistries/{udid}?api-version=2022-12-01-preview&subscription-key={Your-Azure-Maps-Subscription-key} 
+    https://us.atlas.microsoft.com/dataRegistries/{udid}?api-version=2023-06-01&subscription-key={Your-Azure-Maps-Subscription-key} 
 
     ```
 
@@ -241,15 +241,15 @@ The value of the **Operation-Location** key is the status URL that you'll use to
 To (optionally) check the status of the data registry creation process, enter the status URL you copied in the [Create a data registry](#create-a-data-registry) section, and add your subscription key as a query string parameter. The request should look similar to the following URL:
 
 ```http
-https://us.atlas.microsoft.com/dataRegistries/operations/{udid}?api-version=2022-12-01-preview&subscription-key={Your-Azure-Maps-Primary-Subscription-key}
+https://us.atlas.microsoft.com/dataRegistries/operations/{udid}?api-version=2023-06-01&subscription-key={Your-Azure-Maps-Primary-Subscription-key}
 ```
 
 ## Get a list of all files in the data registry
 
 Use the [List][list] request to get a list of all files registered in an Azure Maps account:
 
 ```http
-https://us.atlas.microsoft.com/dataRegistries?api-version=2022-12-01-preview&subscription-key={Azure-Maps-Subscription-key}
+https://us.atlas.microsoft.com/dataRegistries?api-version=2023-06-01&subscription-key={Azure-Maps-Subscription-key}
 ```
 
 The following sample demonstrates three possible statuses, completed, running and failed:
@@ -266,7 +266,6 @@ The following sample demonstrates three possible statuses, completed, running an
         "msiClientId": "3263cad5-ed8b-4829-b72b-3d1ba556e373",
         "linkedResource": "my-storage-account",
         "blobUrl": "https://mystorageaccount.blob.core.windows.net/my-container/my/blob/path1.zip",
-        "downloadURL": "https://us.atlas.microsoft.com/dataRegistries/f6495f62-94f8-0ec2-c252-45626f82fcb2/content?api-version=2022-12-01-preview",
         "sizeInBytes": 29920,
         "contentMD5": "CsFxZ2YSfxw3cRPlqokV0w=="
       },
@@ -280,7 +279,6 @@ The following sample demonstrates three possible statuses, completed, running an
         "msiClientId": "3263cad5-ed8b-4829-b72b-3d1ba556e373",
         "linkedResource": "my-storage-account",
         "blobUrl": "https://mystorageaccount.blob.core.windows.net/my-container/my/blob/path2.geojson",
-        "downloadURL": "https://us.atlas.microsoft.com/dataRegistries/8b1288fa-1958-4a2b-b68e-13a7i5af7d7c/content?api-version=2022-12-01-preview",
         "sizeInBytes": 1339
       },
       "status": "Running"
@@ -293,7 +291,6 @@ The following sample demonstrates three possible statuses, completed, running an
         "dataFormat": "geojson",
         "linkedResource": "my-storage-account",
         "blobUrl": "https://mystorageaccount.blob.core.windows.net/my-container/my/blob/path3.geojson",
-        "downloadURL": "https://us.atlas.microsoft.com/dataRegistries/7c1288fa-2058-4a1b-b68f-13a6h5af7d7c/content?api-version=2022-12-01-preview",
         "sizeInBytes": 1650,
         "contentMD5": "rYpEfIeLbWZPyaICGEGy3A=="
       },
@@ -312,47 +309,8 @@ The data returned when running the list request is similar to the data provided
 | property    | description                       |
 |-------------|-----------------------------------|
 | contentMD5  | MD5 hash created from the contents of the file being registered. For more information, see [Data validation](#data-validation)  |
-| downloadURL | The download URL of the underlying data. Used to [Get content from a data registry](#get-content-from-a-data-registry). |
 | sizeInBytes | The size of the content in bytes. |
 
-## Get content from a data registry
-
-Once you've uploaded one or more files to an Azure storage account, created and Azure Maps datastore to link to those files, then registered them using the [register] API, you can access the data contained in the files.
-
-Use the `udid` to get the content of a file registered in an Azure Maps account:
-
- ```http
-https://us.atlas.microsoft.com/dataRegistries/{udid}/content?api-version=2022-12-01-preview&subscription-key={Your-Azure-Maps-Subscription-key} 
-```
-
-The contents of the file appear in the body of the response. For example, a text based GeoJSON file appears similar to the following example:
-
-```json
-{
-  "type": "FeatureCollection",
-  "features": [
-    {
-      "type": "Feature",
-      "geometry": {
-        "type": "Point",
-        "coordinates": [
-          -122.126986,
-          47.639754
-        ]
-      },
-      "properties": {
-        "geometryId": "001",
-        "radius": 500
-      }
-    }
-  ]
-}
-```
-
-The file type is returned in the `content-type` key of the response header.
-
-Both text and binary files can be saved to a local hard drive or used directly in other processes like importing into the Azure Maps Creator conversion process.
-
 ## Replace a data registry
 
 If you need to replace a previously registered file with another file, rerun the register request, passing in the same [AzureBlob](#the-azureblob) used to create the original registration, except for the [blobUrl](#the-bloburl-property). The `BlobUrl` needs to be modified to point to the new file.

articles/cosmos-db/continuous-backup-restore-introduction.md

@@ -39,7 +39,7 @@ Currently, you can restore an Azure Cosmos DB account (API for NoSQL or MongoDB,
 By default, Azure Cosmos DB stores continuous mode backup data in locally redundant storage blobs. For the regions that have zone redundancy configured, the backup is stored in zone-redundant storage blobs. In continuous backup mode, you can't update the backup storage redundancy.
 
 ## Different ways to restore
-Continuous backup mode supports two ways to restore deleted containers, databases. Existing restore mechanism restores into a [new account](restore-account-continuous-backup.md) as documented here. Restore into existing account is described [here](restore-account-continuous-backup.md). The choice between two depends on the scenarios and impact. Most of the deleted containers, databases can prefer in-account (existing) account restore to prevent data transfer which is required in case you restored to a new account. For scenarios where you have modified the data accidently restore into new account is the right thing to do. 
+Continuous backup mode supports two ways to restore deleted containers, databases. Existing restore mechanism restores into a [new account](restore-account-continuous-backup.md) as documented here. Restore into existing account is described [here](restore-account-continuous-backup.md). The choice between two depends on the scenarios and impact. Most of the deleted containers, databases can prefer in-account (existing) account restore to prevent data transfer which is required in case you restored to a new account. For scenarios where you have modified the data accidentally restore into new account is the right thing to do. 
 
 ## What is restored into a new account?
 

articles/service-health/resource-health-checks-resource-types.md

@@ -175,6 +175,11 @@ Below is a complete list of all the checks executed through resource health by r
 |---|
 |<ul><li>Is performance of the Application Gateway degraded?</li><li>Is the Application Gateway available?</li></ul>|
 
+## Microsoft.network/azureFirewalls
+|Executed Checks|
+|---|
+|<ul><li>Are there enough remaining available ports to perform Source NAT?</li><li>Are there enough remaining available connections?</li></ul>|
+
 ## Microsoft.network/bastionhosts
 |Executed Checks|
 |---|

articles/synapse-analytics/security/synapse-workspace-ip-firewall.md

@@ -16,7 +16,7 @@ This article will explain IP firewall rules and teach you how to configure them
 
 ## IP firewall rules
 
-IP firewall rules grant or deny access to your Azure Synapse workspace based on the originating IP address of each request. You can configure IP firewall rules for your workspace. IP firewall rules configured at the workspace level apply to all public endpoints of the workspace (dedicated SQL pools, serverless SQL pool, and development).
+IP firewall rules grant or deny access to your Azure Synapse workspace based on the originating IP address of each request. You can configure IP firewall rules for your workspace. IP firewall rules configured at the workspace level apply to all public endpoints of the workspace (dedicated SQL pools, serverless SQL pool, and development). The maximum number of IP firewall rules is limited to 128. If you have the **Allow Azure Services and resources to access this server** setting enabled, this counts as a single firewall rule for the workspace.
 
 ## Create and manage IP firewall rules