Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

articles/azure-app-configuration/enable-dynamic-configuration-java-spring-app.md

@@ -72,7 +72,7 @@ Then, open the *pom.xml* file in a text editor and add a `<dependency>` for `azu
 
     | Key | Value |
     |---|---|
-    | Sentinel | 1 |
+    | sentinel | 1 |
 
     Leave **Label** and **Content Type** empty for now.
 
@@ -103,7 +103,7 @@ Then, open the *pom.xml* file in a text editor and add a `<dependency>` for `azu
 
     | Key | Value |
     |---|---|
-    | Sentinel | 2 |
+    | sentinel | 2 |
 
 1. Refresh the browser page to see the new message displayed.
 

articles/cloud-services/cloud-services-guestos-msrc-releases.md

@@ -11,13 +11,67 @@ ms.service: cloud-services
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: tbd
-ms.date: 2/11/2022
+ms.date: 2/15/2022
 ms.author: gunnarc
 ---
 
 # Azure Guest OS
 The following tables show the Microsoft Security Response Center (MSRC) updates applied to the Azure Guest OS. Search this article to determine if a particular update applies to the Guest OS you are using. Updates always carry forward for the particular [family][family-explain] they were introduced in.
 
+## February 2022 Guest OS
+
+>[!NOTE] 
+
+>The February Guest OS is currently being rolled out to Cloud Service VMs that are configured for automatic updates. When the rollout is complete, this version will be made available for manual updates through the Azure portal and configuration files. The following patches are included in the February Guest OS. This list is subject to change. 
+>
+
+| Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |
+| --- | --- | --- | --- | --- |
+|  Rel 22-02 |  [5010351]  |  Latest Cumulative Update(LCU) | 6.41 | Feb 8, 2022 |
+|  Rel 22-02 |  [5006671]  |  IE Cumulative Updates | 2.120, 3.107, 4.100 | Oct 12, 2021 |
+|  Rel 22-02 |  [5010354]  |  Latest Cumulative Update(LCU) | 7.9 | Feb 8, 2022 |
+|  Rel 22-02 |  [5010359]  |  Latest Cumulative Update(LCU) | 5.65 | Feb 8, 2022 |
+|  Rel 22-02 |  [5008867]  |  .NET Framework 3.5 Security and Quality Rollup | 2.120 | Jan 11, 2022 |
+|  Rel 22-02 |  [5008860]  |  .NET Framework 4.5.2 Security and Quality Rollup | 2.120 | Jan 11, 2022 |
+|  Rel 22-02 |  [5008868]  |  .NET Framework 3.5 Security and Quality Rollup | 4.100 | Jan 11, 2022 |
+|  Rel 22-02 |  [5008870]  |  .NET Framework 4.5.2 Security and Quality Rollup | 4.100 | Jan 11, 2022 |
+|  Rel 22-02 |  [5008865]  |  .NET Framework 3.5 Security and Quality Rollup | 3.107 | Jan 11, 2022 |
+|  Rel 22-02 |  [5008869]  |  . NET Framework 4.5.2 Security and Quality Rollup | 3.107 | Jan 11, 2022 |
+|  Rel 22-02 |  [5008873]  |  . NET Framework 3.5 and 4.7.2 Cumulative Update | 6.41 | Jan 11, 2022 |
+|  Rel 22-02 |  [5008882]  |  .NET Framework 4.8 Security and Quality Rollup | 7.9 | Jan 11, 2022 |
+|  Rel 22-02 |  [5010404]  |  Monthly Rollup | 2.120 | Feb 8, 2022 |
+|  Rel 22-02 |  [5010392]  |  Monthly Rollup | 3.107 | Feb 8, 2022 |
+|  Rel 22-02 |  [5010419]  |  Monthly Rollup | 4.100 | Feb 8, 2022 |
+|  Rel 22-02 |  [5001401]  |  Servicing Stack update | 3.107 | Apr 13, 2021 |
+|  Rel 22-02 |  [5001403]  |  Servicing Stack update | 4.100 | Apr 13, 2021 |
+|  Rel 22-02 |  [4578013]  |  Standalone Security Update | 4.100 | Aug 19, 2020 |
+|  Rel 22-02 |  [5005698]  |  Servicing Stack update | 5.65 | Sep 14, 2021 |
+|  Rel 22-02 |  [5010451]  |  Servicing Stack update | 2.120 | Feb 8, 2022 |
+|  Rel 22-02 |  [4494175]  |  Microcode | 5.65 | Sep 1, 2020 |
+|  Rel 22-02 |  [4494174]  |  Microcode | 6.41 | Sep 1, 2020 |
+
+[5010351]: https://support.microsoft.com/kb/5010351
+[5006671]: https://support.microsoft.com/kb/5006671
+[5010354]: https://support.microsoft.com/kb/5010354
+[5010359]: https://support.microsoft.com/kb/5010359
+[5008867]: https://support.microsoft.com/kb/5008867
+[5008860]: https://support.microsoft.com/kb/5008860
+[5008868]: https://support.microsoft.com/kb/5008868
+[5008870]: https://support.microsoft.com/kb/5008870
+[5008865]: https://support.microsoft.com/kb/5008865
+[5008869]: https://support.microsoft.com/kb/5008869
+[5008873]: https://support.microsoft.com/kb/5008873
+[5008882]: https://support.microsoft.com/kb/5008882
+[5010404]: https://support.microsoft.com/kb/5010404
+[5010392]: https://support.microsoft.com/kb/5010392
+[5010419]: https://support.microsoft.com/kb/5010419
+[5001401]: https://support.microsoft.com/kb/5001401
+[5001403]: https://support.microsoft.com/kb/5001403
+[4578013]: https://support.microsoft.com/kb/4578013
+[5005698]: https://support.microsoft.com/kb/5005698
+[5010451]: https://support.microsoft.com/kb/5010451
+[4494175]: https://support.microsoft.com/kb/4494175
+[4494174]: https://support.microsoft.com/kb/4494174
 
 ## January 2022 Guest OS
 | Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |

articles/container-apps/vnet-custom.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.topic:  how-to
-ms.date: 1/28/2021
+ms.date: 2/3/2022
 ms.author: cshoe
 zone_pivot_groups: azure-cli-or-portal
 ---
@@ -21,7 +21,7 @@ As you create an Azure Container Apps [environment](environment.md), a virtual n
 - You can restrict inbound requests to the environment exclusively to the VNET by deploying the environment as internal.
 
 > [!IMPORTANT]
-> In order to ensure the environment deployment within your custom VNET is successful, configure your VNET with an "allow-all" configuration by default. The full list of traffic dependencies required to configure the VNET as "deny-all" is not yet available. Refer to the [custom VNET security sample](https://aka.ms/azurecontainerapps/customvnet) for additional details.
+> In order to ensure the environment deployment within your custom VNET is successful, configure your VNET with an "allow-all" configuration by default. The full list of traffic dependencies required to configure the VNET as "deny-all" is not yet available. Refer to [Known issues for public preview](https://github.com/microsoft/azure-container-apps/wiki/Known-Issues-for-public-preview) for additional details.
 
 :::image type="content" source="media/networking/azure-container-apps-virtual-network.png" alt-text="Azure Container Apps environments use an existing VNET, or you can provide your own.":::
 
@@ -67,6 +67,10 @@ To create an internal only environment, provide the `--internal-only` parameter
 
 ::: zone-end
 
+## Managed resources
+
+When you deploy an internal or an external environment into your own network, a new resource group prefixed with `MC_` is created in the Azure subscription where your environment is hosted. This resource group contains infrastructure components managed by the Azure Container Apps platform, and shouldn't be modified. The resource group contains Public IP addresses used specifically for outbound connectivity from your environment as well as a load balancer. As the load balancer is created in your subscription, there are additional costs associated with deploying the service to a custom virtual network.
+
 ## Example
 
 The following example shows you how to create a Container Apps environment in an existing virtual network.

articles/cosmos-db/sql/migrate-dotnet-v3.md

@@ -6,7 +6,7 @@ ms.author: esarroyo
 ms.service: cosmos-db
 ms.subservice: cosmosdb-sql
 ms.topic: how-to
-ms.date: 01/13/2022
+ms.date: 02/15/2022
 ms.devlang: csharp
 ---
 
@@ -89,6 +89,8 @@ The following classes have been replaced on the 3.0 SDK:
 
 The Microsoft.Azure.Documents.UriFactory class has been replaced by the fluent design. The fluent design builds URLs internally and allows a single `Container` object to be passed around instead of a `DocumentClient`, `DatabaseName`, and `DocumentCollection`.
 
+Because the .NET v3 SDK allows users to configure a custom serialization engine, there is no direct replacement for the `Document` type. When using Newtonsoft.Json (default serialization engine), `JObject` can be used to achieve the same functionality. When using a different serialization engine, you can use its base json document type (for example, `JsonDocument` for System.Text.Json). The recommendation is to use a C# type that reflects the schema of your items instead of relying on generic types.
+
 ### Changes to item ID generation
 
 Item ID is no longer auto populated in the .NET v3 SDK. Therefore, the Item ID must specifically include a generated ID. View the following example:

articles/expressroute/TOC.yml

@@ -181,7 +181,11 @@
   - name: Redundancy
     items:
     - name: Configure ExpressRoute and site-to-site coexisting connections
-      href: expressroute-howto-coexist-resource-manager.md
+      items:
+      - name: Azure portal
+        href: how-to-configure-coexisting-gateway-portal.md
+      - name: Azure PowerShell
+        href: expressroute-howto-coexist-resource-manager.md
     - name: Create a zone-redundant VNet gateway in Azure Availability Zones
       href: ../vpn-gateway/create-zone-redundant-vnet-gateway.md?toc=%2fazure%2fexpressroute%2ftoc.json
   - name: Plan and manage costs

articles/expressroute/expressroute-howto-coexist-resource-manager.md

@@ -49,7 +49,6 @@ You can configure a Site-to-Site VPN connection as a backup for ExpressRoute. Th
 > [!NOTE]
 > While ExpressRoute circuit is preferred over Site-to-Site VPN when both routes are the same, Azure will use the longest prefix match to choose the route towards the packet's destination.
 > 
-> 
 
 ![Diagram that shows a Site-to-Site VPN connection as a backup for ExpressRoute.](media/expressroute-howto-coexist-resource-manager/scenario1.jpg)