Merge branch 'MicrosoftDocs:main' into main

Author: tejaswikolli-web

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 11/04/2022
+ms.date: 02/22/2023
 ms.author: kenwith
 ms.reviewer: arvinh
 ---
@@ -74,7 +74,7 @@ The following table lists an example of required attributes:
 |lastName|name.familyName|surName|
 |workMail|emails[type eq “work”].value|Mail|
 |manager|manager|manager|
-|tag|urn:ietf:params:scim:schemas:extension:CustomExtensionName:2.0:User:tag|extensionAttribute1|
+|tag|`urn:ietf:params:scim:schemas:extension:CustomExtensionName:2.0:User:tag`|extensionAttribute1|
 |status|active|isSoftDeleted (computed value not stored on user)|
 
 The following JSON payload shows an example SCIM schema:
@@ -117,7 +117,7 @@ It helps to categorize between `/User` and `/Group` to map any default user attr
 
 The following table lists an example of user attributes:
 
-| Azure AD user | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User |
+| Azure AD user | `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User` |
 | --- | --- |
 | IsSoftDeleted |active |
 |department| `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department`|
@@ -140,7 +140,7 @@ The following table lists an example of user attributes:
 
 The following table lists an example of group attributes:
 
-| Azure AD group | urn:ietf:params:scim:schemas:core:2.0:Group |
+| Azure AD group | `urn:ietf:params:scim:schemas:core:2.0:Group` |
 | --- | --- |
 | displayName |displayName |
 | members |members |

articles/azure-functions/durable/durable-functions-overview.md

@@ -20,7 +20,7 @@ Durable Functions is designed to work with all Azure Functions programming langu
 
 | Language stack | Azure Functions Runtime versions | Language worker version | Minimum bundles version |
 | - | - | - | - |
-| .NET / C# / F# | Functions 1.0+ | In-process (GA) <br/> Out-of-process ([preview](https://github.com/microsoft/durabletask-dotnet#usage-with-azure-functions)) | n/a |
+| .NET / C# / F# | Functions 1.0+ | In-process <br/> Out-of-process| n/a |
 | JavaScript/TypeScript | Functions 2.0+ | Node 8+ | 2.x bundles |
 | Python | Functions 2.0+ | Python 3.7+ | 2.x bundles |
 | PowerShell | Functions 3.0+ | PowerShell 7+ | 2.x bundles |

articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md

@@ -4,7 +4,7 @@ description: This article describes the version details for the Azure Monitor ag
 ms.topic: conceptual
 author: shseth
 ms.author: shseth
-ms.date: 1/30/2023
+ms.date: 2/22/2023
 ms.custom: references_region
 ms.reviewer: shseth
 
@@ -20,7 +20,7 @@ We strongly recommended to update to the latest version at all times, or opt in
 ## Version details
 | Release Date | Release notes | Windows | Linux |
 |:---|:---|:---|:---|
-| Jan 2023 | <ul><li>Fixed issue related to incorrect *EventLevel* and *Task* values for Log Analytics *Event* table, to match Windows Event Viewer values</li><li>Added missing columns for IIS logs - *TimeGenerated, Time, Date, Computer, SourceSystem, AMA, W3SVC, SiteName*</li><li>Reliability improvements for metrics collection</li><li>Fixed machine restart issues on for Arc-enabled servers related to repeated calls to HIMDS service</li></ul> | 1.12.0.0 | None |
+| Jan 2023 | **Linux** <ul><li>RHEL 9 and Amazon Linux 2 support</li><li>Update to OpenSSL 1.1.1s and require TLS 1.2 or higher</li><li>Performance improvements</li><li>Improvements in Garbage Collection for persisted disk cache and handling corrupted cache files better</li><li>**Fixes** <ul><li>Set agent service memory limit for CentOS/RedHat 7 distros. Resolved MemoryMax parsing error</li><li>Fixed modifying rsyslog system-wide log format caused by installer on RedHat/Centos 7.3</li><li>Fixed permissions to config directory</li><li>Installation reliability improvements</li><li>Fixed permissions on default file so rpm verification doesn't fail</li><li>Added traceFlags setting to enable trace logs for agent</li></ul></li></ul> **Windows** <ul><li>Fixed issue related to incorrect *EventLevel* and *Task* values for Log Analytics *Event* table, to match Windows Event Viewer values</li><li>Added missing columns for IIS logs - *TimeGenerated, Time, Date, Computer, SourceSystem, AMA, W3SVC, SiteName*</li><li>Reliability improvements for metrics collection</li><li>Fixed machine restart issues on for Arc-enabled servers related to repeated calls to HIMDS service</li></ul> | 1.12.0.0 | 1.25.1 |
 | Nov-Dec 2022 | <ul><li>Support for air-gapped clouds added for [Windows MSI installer for clients](./azure-monitor-agent-windows-client.md) </li><li>Reliability improvements for using AMA with Custom Metrics destination</li><li>Performance and internal logging improvements</li></ul> | 1.11.0.0 | None | 
 | Oct 2022 | **Windows** <ul><li>Increased reliability of data uploads</li><li>Data quality improvements</li></ul> **Linux** <ul><li>Support for `http_proxy` and `https_proxy` environment variables for [network proxy configurations](./azure-monitor-agent-data-collection-endpoint.md#proxy-configuration) for the agent</li><li>[Text logs](./data-collection-text-log.md) <ul><li>Network proxy support enabled</li><li>Fixed missing `_ResourceId`</li><li>Increased maximum line size support to 1MB</li></ul></li><li>Support ingestion of syslog events whose timestamp is in the future</li><li>Performance improvements</li><li>Fixed `diskio` metrics instance name dimension to use the disk mount path(s) instead of the device name(s)</li><li>Fixed world writable file issue to lockdown write access to certain agent logs and configuration files stored locally on the machine</li></ul>  | 1.10.0.0 | 1.24.2 | 
 | Sep 2022 | Reliability improvements | 1.9.0.0 | None | 

articles/azure-monitor/app/opencensus-python-request.md

@@ -28,7 +28,8 @@ First, instrument your Python application with latest [OpenCensus Python SDK](./
     )
     ```
 
-3. Make sure AzureExporter is properly configured in your `settings.py` under `OPENCENSUS`. For requests from urls that you don't wish to track, add them to `EXCLUDELIST_PATHS`.
+3. Make sure AzureExporter is configured properly in your `settings.py` under `OPENCENSUS`. For requests from urls that you don't wish to track, add them to `EXCLUDELIST_PATHS`.
+
 
     ```python
     OPENCENSUS = {
@@ -149,8 +150,7 @@ OpenCensus doesn't have an extension for FastAPI. To write your own FastAPI midd
     HTTP_URL = COMMON_ATTRIBUTES['HTTP_URL']
     HTTP_STATUS_CODE = COMMON_ATTRIBUTES['HTTP_STATUS_CODE']
 
-    APPINSIGHTS_CONNECTION_STRING='<your-appinsights_connection-string-here>'
-    exporter=AzureExporter(connection_string=f'{APPINSIGHTS_CONNECTION_STRING}')
+    exporter=AzureExporter(connection_string='<your-appinsights-connection-string-here>')
     sampler=ProbabilitySampler(1.0)
 
     # fastapi middleware for opencensus

articles/azure-percept/includes/retire.md

@@ -10,8 +10,8 @@ ROBOTS: NOINDEX
 > [!IMPORTANT]
 > **Retirement of Azure Percept DK:**
 > 
-> **Update November 9, 2022**: A firmware update that enables the Vision SoM and Audio SOM to retain their functionality with the DK beyond the retirement date, will be made available before the retirement date.
+>**Update February 22, 2023**: A firmware update that enables the Vision SoM and Audio SOM to retain their functionality with the DK beyond the retirement date, is now available [here](https://aka.ms/audio_vision_som_update).
 >
->The [Azure Percept](https://azure.microsoft.com/products/azure-percept/) public preview will be evolving to support new edge device platforms and developer experiences.  As part of this evolution the Azure Percept DK and Audio Accessory and associated supporting Azure services for the Percept DK will be retired March 30th, 2023. 
+>The Azure Percept preview including the Percept DK, Audio Accessory, and associated supporting Azure services will be retired March 30th, 2023.
 >
 >Effective March 30th, 2023, the Azure Percept DK and Audio Accessory will no longer be supported by any Azure services including Azure Percept Studio, OS updates, containers updates, view web stream, and Custom Vision integration.  Microsoft will no longer provide customer success support and any associated supporting services. For more information, please visit the [Retirement Notice Blog Post](https://azure.microsoft.com/updates/azure-percept-dk-retirement-announcement). 

articles/azure-percept/retirement-of-azure-percept-dk.md

@@ -11,15 +11,15 @@ ROBOTS: NOINDEX
 
 # Retirement of Azure Percept DK
 
-**Update November 9, 2022**: A firmware update that enables the Vision SoM and Audio SOM to retain their functionality with the DK beyond the retirement date, will be made available before the retirement date.
+**Update February 22, 2023**: A firmware update that enables the Vision SoM and Audio SOM to retain their functionality with the DK beyond the retirement date, is now available [here](https://aka.ms/audio_vision_som_update).
 
-The [Azure Percept](https://azure.microsoft.com/products/azure-percept/) public preview will be evolving to support new edge device platforms and developer experiences. As part of this evolution the Azure Percept DK and Audio Accessory and associated supporting Azure services for the Percept DK will be retired March 30, 2023.
+The Azure Percept preview including the Percept DK, Audio Accessory, and associated supporting Azure services will be retired March 30th, 2023.
 
 ## How does this change affect me?
 
 - After March 30, 2023, the Azure Percept DK and Audio Accessory will no longer be supported by any Azure services including Azure Percept Studio, OS updates, containers updates, view web stream, and Custom Vision integration. 
 - Microsoft will no longer provide customer success support for the Azure Percept DK and Audio Accessory and any associated supporting services for the Percept DK.
-- Existing Custom Vision and Custom Speech projects created using Percept Studio for the Percept DK will not be deleted and billing if applicable will continue. You can no longer modify or use your project with Percept Studio. 
+- Existing Custom Vision and Custom Speech projects created using Percept Studio for the Percept DK will not be deleted and billing if applicable will continue for any backend services utilized after the retirement date. You can no longer modify or use your project with Percept Studio. 
 
 ## Recommended action
 
@@ -36,5 +36,5 @@ If you have questions regarding Azure Percept DK, please refer to the below **FA
 | What is changing?                              | Azure Percept DK and Audio Accessory will no longer be supported by any Azure services including Azure Percept Studio and Updates.    | 
 | When is this change occurring?                 | On March 30, 2023. Until this date your DK and Studio will function as-is and updates and customer support will be offered. After this date, all updates and customer support will stop.    | 
 | Will my projects be deleted?                   | Your projects remain in the underlying Azure Services they were created in (example: Custom Vision, Speech Studio, etc.). They won't be deleted due to this retirement. You can no longer modify or use your project with Percept Studio.   | 
-| Do I need to do anything before March 30, 2023?    | Yes, you will need to close the resources and projects associated with the Azure Percept Studio and DK to avoid future billing, as these backend resources and projects will continue to bill after retirement.    | 
+| Do I need to do anything before March 30, 2023?    | Yes, you will need to close the resources and projects associated with the Azure Percept Studio and DK to avoid future billing, as these backend resources and projects will continue to bill after retirement. For SoMs to continue having functionality, you will need to apply a firmware update that enables the Vision SoM and Audio SoM to retain functionality that is now available [here](https://aka.ms/audio_vision_som_update).    | 
 

articles/azure-resource-manager/management/move-limitations/cloud-services-extended-support.md

@@ -0,0 +1,35 @@
+---
+title: Move Azure Cloud Services (extended support) deployment resources
+description: Use Azure Resource Manager to move Cloud Services (extended support) deployment resources to a new resource group or subscription.
+ms.topic: conceptual
+ms.date: 02/14/2023
+ms.custom: hirshah
+---
+
+# Move guidance for Cloud Services (extended support) deployment model resources
+
+The steps to move resources deployed through the Cloud Services (extended support) model differ based on whether you're moving the resources within a subscription or to a new subscription.
+
+## Move in the same subscription
+
+When moving Cloud Services (extended support) resources from one resource group to another resource group within the same subscription, the following restrictions apply:
+
+- Cloud Service must not be in manual mode
+- Cloud Service must not be VIP Swappable
+- Cloud Service must not have any pending operations
+- Cloud Service must not be in migration
+- Cloud Service must not be in failed state
+- Ensure the Cloud Service has an unexpired SAS blob URI pointing to the cloud service package
+
+> [!NOTE]
+> Cloud Services and associated networking resources (for example, PublicIPs and network security groups) can be move independently. Load balancers must always exist in the same resource group
+
+To move classic resources to a new resource group within the same subscription, use the [standard move operations](../move-resource-group-and-subscription.md) through the portal, Azure PowerShell, Azure CLI, or REST API. You use the same operations as you use for moving Resource Manager resources.
+
+## Move across subscriptions
+
+When moving Cloud Services (extended support) deployments to a new subscription, the following restrictions apply:
+
+- When performing a cross subscription move, all associated cloud service resources such key vault and network resources must move together.
+- If faced with a Move Resource operation error saying that the cloud service can't be moved because of a prior failed operation, create a ticket to resolve the issue. 
+- Cloud Service must not have any cross-subscription references.

articles/azure-resource-manager/management/toc.yml

@@ -53,6 +53,8 @@
           href: ../../automation/how-to/move-account.md?toc=/azure/azure-resource-manager/management/toc.json
         - name: Classic deployment
           href: ./move-limitations/classic-model-move-limitations.md
+        - name: Cloud Services (extended support)
+          href: ./move-limitations/cloud-services-extended-support.md
         - name: Networking
           href: ./move-limitations/networking-move-limitations.md
         - name: Recovery Services

articles/azure-resource-manager/templates/template-expressions.md

@@ -2,7 +2,7 @@
 title: Template syntax and expressions
 description: Describes the declarative JSON syntax for Azure Resource Manager templates (ARM templates).
 ms.topic: conceptual
-ms.date: 02/09/2023
+ms.date: 02/22/2023
 ms.custom: devx-track-azurepowershell
 ---
 
@@ -67,6 +67,23 @@ To escape double quotes in an expression, such as adding a JSON object in the te
 },
 ```
 
+To escape single quotes in an ARM expression output, double up the single quotes. The output of the following template will result in JSON value `{"abc":"'quoted'"}`.
+
+```json
+{
+  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+  "contentVersion": "1.0.0.0",
+  "parameters": {},
+  "resources": [],
+  "outputs": {
+    "foo": {
+      "type": "object",
+      "value": "[createObject('abc', '''quoted''')]"
+    }
+  }
+}
+```
+
 When passing in parameter values, the use of escape characters depends on where the parameter value is specified. If you set a default value in the template, you need the extra left bracket.
 
 ```json

articles/cosmos-db/mongodb/introduction.md

@@ -19,6 +19,8 @@ ms.custom: ignite-2022
 
 Azure Cosmos DB for MongoDB makes it easy to use Azure Cosmos DB as if it were a MongoDB database. You can use your existing MongoDB skills and continue to use your favorite MongoDB drivers, SDKs, and tools by pointing your application to the connection string for your account using the API for MongoDB.
 
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RWXr4T]
+
 > [!TIP]
 > Want to try the API for MongoDB with no commitment? Create an Azure Cosmos DB account using [Try Azure Cosmos DB](../try-free.md) for free.