Merge pull request #242339 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/hybrid/connect/reference-connect-version-history.md

@@ -37,8 +37,7 @@ Required permissions | For permissions required to apply an update, see [Azure A
 
 ## Retiring Azure AD Connect 1.x versions
 > [!IMPORTANT]
-> *As of August 31, 2022, all 1.x versions of Azure AD Connect are retired because they include SQL Server 2012 components that will no longer be supported.* Upgrade to the most recent version of Azure AD Connect (2.x version) by that date or [evaluate and switch to Azure AD cloud sync](../cloud-sync/what-is-cloud-sync.md).
-> AADConnect V1.x may stop working on December 31st, due to the retirement of the ADAL library service on that date.
+> Action required: Synchronization will stop working on October 1, 2023, for any customers still running Azure AD Connect Sync V1.  Customers using cloud sync or Azure AD Connect V2 will remain fully operational with no action required. For more information and next step guidance, see [Decommission Azure AD Connect V1](https://aka.ms/DecommissionAADConnectV1) if an upgrade is required.
 
 ## Retiring Azure AD Connect 2.x versions
 > [!IMPORTANT]
@@ -81,11 +80,11 @@ To read more about autoupgrade, see [Azure AD Connect: Automatic upgrade](how-to
 ## 2.2.1.0
 
 ### Release status
-5/23/2023: Released for autoupgrade only
+6/19/2023: Released for download and autoupgrade.
 
 ### Functional Changes
  - We have enabled Auto Upgrade for tenants with custom synchronization rules. Note that deleted (not disabled) default rules will be re-created and enabled upon Auto Upgrade.
- - We have added Microsoft Azure AD Connect Agent Updater service to the install.
+ - We have added Microsoft Azure AD Connect Agent Updater service to the install. This new service will be used for future auto upgrades.
  - We have removed the Synchronization Service WebService Connector Config program from the install.
 
 ### Bug Fixes

articles/azure-cache-for-redis/cache-best-practices-performance.md

@@ -179,7 +179,7 @@ The following tables show the GET requests per second at different capacities, u
 
 | Instance | Capacity 2 | Capacity 4 | Capacity 6 |
 |:---:| ---:| ---:| ---:|
-| E10 | 1,00,000 | 1,900,000 | 2,500,000 |
+| E10 | 1,000,000 | 1,900,000 | 2,500,000 |
 | E20 | 900,000 | 1,700,000 | 2,300,000 |
 | E50 | 1,700,000 | 3,000,000 | 3,900,000 |
 | E100 | 2,500,000 | 4,400,000 | 4,900,000|

articles/azure-maps/drawing-conversion-error-codes.md

@@ -1,8 +1,9 @@
 ---
 title: Azure Maps Drawing Conversion errors and warnings
+titleSuffix:  Microsoft Azure Maps Creator
 description: Learn about the Conversion errors and warnings you may meet while you're using the Azure Maps Conversion service. Read the recommendations on how to resolve the errors and the warnings, with some examples.
-author: eriklindeman
-ms.author: eriklind
+author: brendansco 
+ms.author: brendanc 
 ms.date: 05/21/2021
 ms.topic: conceptual
 ms.service: azure-maps

articles/azure-maps/drawing-error-visualizer.md

@@ -1,8 +1,9 @@
 ---
 title: Use Azure Maps Drawing Error Visualizer
+titleSuffix:  Microsoft Azure Maps Creator
 description: This article demonstrates how to visualize warnings and errors returned by the Creator Conversion API.
-author: eriklindeman
-ms.author: eriklind
+author: brendansco 
+ms.author: brendanc 
 ms.date: 02/17/2023
 ms.topic: conceptual
 ms.service: azure-maps

articles/azure-maps/how-to-manage-creator.md

@@ -1,8 +1,9 @@
 ---
 title: Manage Microsoft Azure Maps Creator
+titleSuffix:  Microsoft Azure Maps Creator
 description: This article demonstrates how to manage Microsoft Azure Maps Creator.
-author: eriklindeman
-ms.author: eriklind
+author: brendansco
+ms.author: brendanc
 ms.date: 01/20/2022
 ms.topic: how-to
 ms.service: azure-maps

articles/azure-maps/how-to-use-indoor-module.md

@@ -1,8 +1,9 @@
 ---
 title: Use the Azure Maps Indoor Maps module with Microsoft Creator services with custom styles (preview)
+titleSuffix:  Microsoft Azure Maps Creator
 description: Learn how to use the Microsoft Azure Maps Indoor Maps module to render maps by embedding the module's JavaScript libraries.
-author: eriklindeman
-ms.author: eriklind
+author: brendansco
+ms.author: brendanc
 ms.date: 09/23/2022
 ms.topic: how-to
 ms.service: azure-maps

articles/azure-maps/indoor-map-dynamic-styling.md

@@ -1,5 +1,6 @@
 ---
 title: Implement dynamic styling for Azure Maps Creator indoor maps
+titleSuffix:  Microsoft Azure Maps Creator
 description: Learn how to Implement dynamic styling for Creator indoor maps 
 author: brendansco
 ms.author: Brendanc

articles/azure-maps/schema-stateset-stylesobject.md

@@ -1,13 +1,12 @@
 ---
 title:  StylesObject Schema reference guide for Dynamic Azure Maps
 description: Reference guide to the dynamic Azure Maps StylesObject schema and syntax.
-author: eriklindeman
-ms.author: eriklind
+author: brendansco 
+ms.author: brendanc 
 ms.date: 02/17/2023
 ms.topic: reference
 ms.service: azure-maps
 services: azure-maps
-
 ---
 
 # StylesObject Schema reference guide for dynamic Maps
@@ -18,14 +17,12 @@ services: azure-maps
 
 A `StyleObject` is one of the following style rules:
 
- * [`BooleanTypeStyleRule`](#booleantypestylerule)
- * [`NumericTypeStyleRule`](#numerictypestylerule)
- * [`StringTypeStyleRule`](#stringtypestylerule)
+* [`BooleanTypeStyleRule`](#booleantypestylerule)
+* [`NumericTypeStyleRule`](#numerictypestylerule)
+* [`StringTypeStyleRule`](#stringtypestylerule)
 
 The JSON below shows example usage of each of the three style types.  The `BooleanTypeStyleRule` is used to determine the dynamic style for features whose `occupied` property is true and false.  The `NumericTypeStyleRule` is used to determine the style for features whose `temperature` property falls within a certain range. Finally, the `StringTypeStyleRule` is used to match specific styles to `meetingType`.
 
-
-
 ```json
  "styles": [
      {

articles/data-factory/quickstart-create-data-factory-python.md

@@ -196,7 +196,7 @@ You define a dataset that represents the source data in Azure Blob. This Blob da
 ```python
     # Create an Azure blob dataset (input)
     ds_name = 'ds_in'
-    ds_ls = LinkedServiceReference(reference_name=ls_name)
+    ds_ls = LinkedServiceReference(type="LinkedServiceReference",reference_name=ls_name)
     blob_path = '<container>/<folder path>'
     blob_filename = '<file name>'
     ds_azure_blob = DatasetResource(properties=AzureBlobDataset(
@@ -370,7 +370,7 @@ def main():
 
     # Create an Azure blob dataset (input)
     ds_name = 'ds_in'
-    ds_ls = LinkedServiceReference(reference_name=ls_name)
+    ds_ls = LinkedServiceReference(type="LinkedServiceReference",reference_name=ls_name)
     blob_path = '<container>/<folder path>'
     blob_filename = '<file name>'
     ds_azure_blob = DatasetResource(properties=AzureBlobDataset(

articles/defender-for-cloud/how-to-manage-attack-path.md

@@ -20,7 +20,7 @@ You can check out the full list of [Attack path names and descriptions](attack-p
 | Aspect | Details |
 |--|--|
 | Release state | GA (General Availability) |
-| Prerequisites | - [Enable agentless scanning](enable-vulnerability-assessment-agentless.md), or [Enable Defender for Server P1 (which includes MDVM)](defender-for-servers-introduction.md) or [Defender for Server P2 (which includes MDVM and Qualys)](defender-for-servers-introduction.md). <br> - [Enable Defender CSPM](enable-enhanced-security.md) <br> - [Enable Defender for Containers](defender-for-containers-enable.md), and install the relevant agents in order to view attack paths that are related to containers. This also gives you the ability to [query](how-to-manage-cloud-security-explorer.md#build-a-query-with-the-cloud-security-explorer) containers data plane workloads in security explorer. |
+| Prerequisites | - [Enable agentless scanning](enable-vulnerability-assessment-agentless.md), or [Enable Defender for Server P1 (which includes MDVM)](defender-for-servers-introduction.md) or [Defender for Server P2 (which includes MDVM and Qualys)](defender-for-servers-introduction.md). <br> - [Enable Defender CSPM](enable-enhanced-security.md) <br> - Enable agentless container posture extension in Defender CSPM, or [Enable Defender for Containers](defender-for-containers-enable.md), and install the relevant agents in order to view attack paths that are related to containers. This also gives you the ability to [query](how-to-manage-cloud-security-explorer.md#build-a-query-with-the-cloud-security-explorer) containers data plane workloads in security explorer. |
 | Required plans | - Defender Cloud Security Posture Management (CSPM) enabled |
 | Required roles and permissions: | - **Security Reader** <br> - **Security Admin** <br> - **Reader** <br> - **Contributor** <br> - **Owner** |
 | Clouds: | :::image type="icon" source="./media/icons/yes-icon.png"::: Commercial clouds (Azure, AWS) <br>:::image type="icon" source="./media/icons/no-icon.png"::: Commercial clouds (GCP) <br>:::image type="icon" source="./media/icons/no-icon.png"::: National (Azure Government, Azure China 21Vianet) |