Merge pull request #221399 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/defender-for-cloud/defender-for-containers-vulnerability-assessment-azure.md

@@ -169,6 +169,12 @@ Yes. The results are under [Sub-Assessments REST API](/rest/api/defenderforcloud
 
 Some images may reuse tags from an image that was already scanned. For example, you may reassign the tag “Latest” every time you add an image to a digest. In such cases, the ‘old’ image does still exist in the registry and may still be pulled by its digest. If the image has security findings and is pulled, it will expose security vulnerabilities.
 
+### Does Defender for Containers scan images in Microsoft Container Registry?
+
+Currently, Defender for Containers can scan images in Azure Container Registry (ACR) and AWS Elastic Container Registry (ECR) only.
+Docker Registry, Microsoft Artifact Registry/Microsoft Container Registry, and Microsoft Azure Red Hat OpenShift (ARO) built-in container image registry are not supported.
+Images should first be imported to ACR. Learn more about [importing container images to an Azure container registry](/azure/container-registry/container-registry-import-images?tabs=azure-cli).
+
 ## Next steps
 
 Learn more about the [advanced protection plans of Microsoft Defender for Cloud](enhanced-security-features-overview.md).

articles/defender-for-iot/organizations/workbooks.md

@@ -16,7 +16,7 @@ Each workbook graph or chart is based on an Azure Resource Graph (ARG) query run
 - Gather sensor statuses
 - Identify new devices in your network
 - Find alerts related to specific IP addresses
-- Understand which alerts are seen by each sensor.
+- Understand which alerts are seen by each sensor
 
 ## View workbooks
 

articles/machine-learning/how-to-access-azureml-behind-firewall.md

@@ -97,7 +97,7 @@ These rule collections are described in more detail in [What are some Azure Fire
     | **\*.anaconda.org** | Used to get repo data. |
     | **pypi.org** | Used to list dependencies from the default index, if any, and the index isn't overwritten by user settings. If the index is overwritten, you must also allow **\*.pythonhosted.org**. |
     | **cloud.r-project.org** | Used when installing CRAN packages for R development. |
-    | **ghcr.io**</br>**pkg-containers.githubusercontent.com** | Used by the Custom Applications feature on a compute instance to pull images from Github Container Repository (ghcr.io). For example, the RStudio or Posit Workbench image is hosted here. |
+    | **ghcr.io**</br>**pkg-containers.githubusercontent.com** | Used by the Custom Applications feature on a compute instance to pull images from GitHub Container Repository (ghcr.io). For example, the RStudio or Posit Workbench image is hosted here. |
     | **\*pytorch.org** | Used by some examples based on PyTorch. |
     | **\*.tensorflow.org** | Used by some examples based on Tensorflow. |
     | **\*vscode.dev**</br>**\*vscode-unpkg.net**</br>**\*vscode-cdn.net**</br>**\*vscodeexperiments.azureedge.net**</br>**default.exp-tas.com** | Required to access vscode.dev (Visual Studio Code for the Web) |

articles/storage/blobs/access-tiers-overview.md

@@ -62,7 +62,8 @@ Data must remain in the archive tier for at least 180 days or be subject to an e
 
 While a blob is in the archive tier, it can't be read or modified. To read or download a blob in the archive tier, you must first rehydrate it to an online tier, either hot or cool. Data in the archive tier can take up to 15 hours to rehydrate, depending on the priority you specify for the rehydration operation. For more information about blob rehydration, see [Overview of blob rehydration from the archive tier](archive-rehydrate-overview.md).
 
-An archived blob's metadata remains available for read access, so that you can list the blob and its properties, metadata, and index tags. Metadata for a blob in the archive tier is read-only, while blob index tags can be read or written. Snapshots aren't supported for archived blobs.
+An archived blob's metadata remains available for read access, so that you can list the blob and its properties, metadata, and index tags. Metadata for a blob in the archive tier is read-only, while blob index tags can be read or written. Storage costs for metadata of archived blobs will be charged on Cool tier rates.
+Snapshots aren't supported for archived blobs.
 
 The following operations are supported for blobs in the archive tier:
 

articles/synapse-analytics/sql/connection-strings.md

@@ -13,7 +13,7 @@ ms.custom: devx-track-csharp
 
 # Connection strings for Synapse SQL
 
-You can connect to Synapse SQL with several different application protocols such as, [ADO.NET](/dotnet/framework/data/adonet/), [ODBC](/sql/connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows), [PHP](/sql/connect/php/overview-of-the-php-sql-driver?f=255&MSPPError=-2147217396), and [JDBC](/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server). Below are some examples of connections strings for each protocol. 
+You can connect to Synapse SQL with several different application libraries such as, [ADO.NET](/dotnet/framework/data/adonet/), [ODBC](/sql/connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows), [PHP](/sql/connect/php/overview-of-the-php-sql-driver?f=255&MSPPError=-2147217396), and [JDBC](/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server). Below are some examples of connections strings for each library. 
 
 You can also use the Azure portal to build your connection string.  To build your connection string using the Azure portal, navigate to your database blade, under *Essentials* select *Show database connection strings*.
 
@@ -26,7 +26,7 @@ Server=tcp:{your_server}.sql.azuresynapse.net,1433;Database={your_database};User
 ## Sample ODBC connection string
 
 ```csharp
-Driver={SQL Server Native Client 11.0};Server=tcp:{your_server}.sql.azuresynapse.net,1433;Database={your_database};Uid={your_user_name};Pwd={your_password_here};Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;
+Driver={ODBC Driver 18 for SQL Server};Server=tcp:{your_server}.sql.azuresynapse.net,1433;Database={your_database};Uid={your_user_name};Pwd={your_password_here};Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;
 ```
 
 ## Sample PHP connection string
@@ -42,12 +42,12 @@ jdbc:sqlserver://yourserver.sql.azuresynapse.net:1433;database=yourdatabase;user
 ```
 
 > [!NOTE]
-> Consider setting the connection timeout to 300 seconds to allow the connection to survive short periods of unavailability.
+> Consider setting the connection timeout to 300 seconds to allow the connection to survive short periods of unavailability and provide enough time for paused instances to resume.
 
 ## Recommendations
 
 For executing **serverless SQL pool** queries, recommended tools are [Azure Data Studio](get-started-azure-data-studio.md) and Azure Synapse Studio.
 
 ## Next steps
 
-To start querying your analytics with Visual Studio and other applications, see [Query with Visual Studio](../sql-data-warehouse/sql-data-warehouse-query-visual-studio.md?context=/azure/synapse-analytics/context/context).
+To start querying your analytics with Visual Studio and other applications, see [Query with Visual Studio](../sql-data-warehouse/sql-data-warehouse-query-visual-studio.md?context=/azure/synapse-analytics/context/context).