Merge pull request #225784 from MicrosoftDocs/main

01/31 AM Publishing

Author: v-alje

articles/active-directory/develop/msal-android-handling-exceptions.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 11/09/2021
+ms.date: 01/26/2023
 ms.author: dmwendia
 ms.reviewer: jmprieur
 ms.custom: "devx-track-csharp, aaddev, has-adal-ref"
@@ -24,7 +24,7 @@ After Microsoft Authentication Library (MSAL) [acquires a token](msal-acquire-ca
 
 The recommendation is:
 - When you're writing a desktop application, use the cross-platform token cache as explained in [Desktop apps](msal-net-token-cache-serialization.md?tabs=desktop).
-- Do nothing for [mobile and UWP apps](msal-net-token-cache-serialization.md?tabs=mobile). MSAL.NET provides secure storage for the cache.
+- Do nothing for [mobile and Universal Windows Platform (UWP) apps](msal-net-token-cache-serialization.md?tabs=mobile). MSAL.NET provides secure storage for the cache.
 - In ASP.NET Core [web apps](scenario-web-app-call-api-overview.md) and [web APIs](scenario-web-api-call-api-overview.md), use [Microsoft.Identity.Web](microsoft-identity-web.md) as a higher-level API. You'll get token caches and much more. See [ASP.NET Core web apps and web APIs](msal-net-token-cache-serialization.md?tabs=aspnetcore).
 - In the other cases of [web apps](scenario-web-app-call-api-overview.md) and [web APIs](scenario-web-api-call-api-overview.md):
   -	If you request tokens for users in a production application, use a [distributed token cache](msal-net-token-cache-serialization.md?tabs=aspnet#distributed-caches) (Redis, SQL Server, Azure Cosmos DB, distributed memory). Use token cache serializers available from [Microsoft.Identity.Web.TokenCache](https://www.nuget.org/packages/Microsoft.Identity.Web.TokenCache/).
@@ -252,7 +252,7 @@ You can specify that you don't want to have any token cache serialization and in
 
 `WithCacheOptions(CacheOptions.EnableSharedCacheOptions)` makes the internal MSAL token cache shared between MSAL client application instances. Sharing a token cache is faster than using any token cache serialization, but the internal in-memory token cache doesn't have eviction policies. Existing tokens will be refreshed in place, but fetching tokens for different users, tenants, and resources makes the cache grow accordingly. 
 
-If you use this approach and have a large number of users or tenants, be sure to monitor the memory footprint. If the memory footprint becomes a problem, consider enabling token cache serialization, which might reduce the internal cache size. Also be aware that currently, you can't use shared cache and cache serialization together.
+If you use this approach and have a large number of users or tenants, be sure to monitor the memory footprint. If the memory footprint becomes a problem, consider enabling token cache serialization, which might reduce the internal cache size. Currently, you can't use shared cache and cache serialization together.
 
 #### In-memory token cache
 

articles/active-directory/develop/msal-net-token-cache-serialization.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: multi-tenant-organizations
 ms.topic: how-to
-ms.date: 01/23/2023
+ms.date: 01/31/2023
 ms.author: rolyon
 ms.custom: it-pro
 
@@ -62,7 +62,7 @@ These steps describe how to use Microsoft Graph Explorer (recommended), but you
     Content-Type: application/json
     
     {
-      "tenantId": "3d0f5dec-5d3d-455c-8016-e2af1ae4d31a",
+      "tenantId": "3d0f5dec-5d3d-455c-8016-e2af1ae4d31a"
     }
     ```
     
@@ -94,12 +94,12 @@ These steps describe how to use Microsoft Graph Explorer (recommended), but you
     }
     ```
 
-1. Use the [Update crossTenantIdentitySyncPolicyPartner](/graph/api/crosstenantidentitysyncpolicypartner-update?view=graph-rest-beta&preserve-view=true) API to enable user synchronization in the target tenant.
+1. Use the [Create identitySynchronization](/graph/api/crosstenantaccesspolicyconfigurationpartner-put-identitysynchronization?view=graph-rest-beta&preserve-view=true) API to enable user synchronization in the target tenant.
 
     **Request**
     
     ```http
-    PATCH https://graph.microsoft.com/beta/policies/crossTenantAccessPolicy/partners/3d0f5dec-5d3d-455c-8016-e2af1ae4d31a/identitySynchronization
+    PUT https://graph.microsoft.com/beta/policies/crossTenantAccessPolicy/partners/3d0f5dec-5d3d-455c-8016-e2af1ae4d31a/identitySynchronization
     Content-type: application/json
     
     {

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-configure-graph.md

@@ -13,9 +13,6 @@ ms.custom: template-how-to
 
 # How to upgrade an existing Redis 4 cache to Redis 6
 
-> [!IMPORTANT]
-> We are improving the upgrade experience and have temporarily disabled the Redis version upgrade. We recommend that you upgrade your caches starting in February 2023.
-
 Azure Cache for Redis supports upgrading the version of your Azure Cache for Redis from Redis 4 to Redis 6. Upgrading is similar to regular monthly maintenance. Upgrading follows the same pattern as maintenance: First, the Redis version on the replica node is updated, followed by an update to the primary node. Your client application should treat the upgrade operation exactly like a planned maintenance event.
 
 As a precautionary step, we recommend exporting the data from your existing Redis 4 cache and testing your client application with a Redis 6 cache in a lower environment before upgrading.
@@ -46,18 +43,37 @@ Before you upgrade, check the Redis version of a cache by selecting **Properties
 
 ## Upgrade using the Azure portal
 
-> [!IMPORTANT]
-> We are improving the upgrade experience and have temporarily disabled the Redis version upgrade. We recommend that you upgrade your caches starting in February 2023.
+1. In the Azure portal, select the Azure Cache for Redis instance that you want to upgrade from Redis 4 to Redis 6.
+
+1. On the left side of the screen, select **Advanced settings**.
+
+1. If your cache instance is eligible to be upgraded, you should see the following blue banner. If you want to proceed, select the text in the banner.
+
+    :::image type="content" source="media/cache-how-to-upgrade/blue-banner-upgrade-cache.png" alt-text="Screenshot informing you that you can upgrade your cache to Redis 6 with additional features. Upgrading your cache instance cannot be reversed.":::
+
+1. A dialog box displays a popup notifying you that upgrading is permanent and might cause a brief connection blip. Select **Yes** if you would like to upgrade your cache instance.
+
+    :::image type="content" source="media/cache-how-to-upgrade/dialog-version-upgrade.png" alt-text="Screenshot showing a dialog with more information about upgrading your cache with Yes selected.":::
+
+1. To check on the status of the upgrade, navigate to **Overview**.
+
+    :::image type="content" source="media/cache-how-to-upgrade/upgrade-status.png" alt-text="Screenshot showing Overview in the Resource menu. Status shows cache is being upgraded."::: 
 
 ## Upgrade using Azure CLI
 
-> [!IMPORTANT]
-> We are improving the upgrade experience and have temporarily disabled the Redis version upgrade. We recommend that you upgrade your caches starting in February 2023.
+To upgrade a cache from 4 to 6 using the Azure CLI, use the following command:
+
+```azurecli-interactive
+az redis update --name cacheName --resource-group resourceGroupName --set redisVersion=6
+```
 
 ## Upgrade using PowerShell
 
-> [!IMPORTANT]
-> We are improving the upgrade experience and have temporarily disabled the Redis version upgrade. We recommend that you upgrade your caches starting in February 2023.
+To upgrade a cache from 4 to 6 using PowerShell, use the following command:
+
+```powershell-interactive
+Set-AzRedisCache -Name "CacheName" -ResourceGroupName "ResourceGroupName" -RedisVersion "6"
+``` 
 
 ## Next steps
 

articles/azure-cache-for-redis/cache-how-to-upgrade.md

@@ -8,6 +8,9 @@ ms.reviewer: damendo
 
 # Syslog collection with Container Insights (preview)
 
+>[!NOTE]
+> During the ongoing public preview, only command line onboarding is available. Portal onboarding is not available and will be added in March 2023.
+
 Container Insights offers the ability to collect Syslog events from Linux nodes in your [Azure Kubernetes Service (AKS)](../../aks/intro-kubernetes.md) clusters. Customers can use Syslog for monitoring security and health events, typically by ingesting syslog into SIEM systems like [Microsoft Sentinel](https://azure.microsoft.com/products/microsoft-sentinel/#overview).  
 
 ## Prerequisites 

articles/azure-monitor/containers/container-insights-syslog.md

@@ -112,6 +112,9 @@ sections:
           For detailed description on how to switch to the correct domain, see [Switch between tenants](switch-tenants-portal.md).
   - name: Privacy Questions
     questions:
+      - question: How is network traffic encrypted by Azure Video Indexer?
+        answer: Communication between a client application and an Azure Video Indexer account is encrypted using Transport Layer Security (TLS). TLS is a standard cryptographic protocol that ensures privacy and data integrity between clients and services over the Internet. For more information about TLS, see [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security). Video Indexer enforces a minimum of TLS v1.2. Customers can't control the cipher suits, we will pick the first match between the client and server going from strong to weaker.
+      
       - question: Are video and audio files indexed by Azure Video Indexer stored?
         answer: Yes, unless you delete the file from Azure Video Indexer, either using the Azure Video Indexer website or API, your video and audio files are stored. For the trial, the video and audio files that you index are stored in the Azure region East US. Otherwise, your video and audio files are stored in the storage account of your Azure subscription.
 

articles/azure-video-indexer/faq.yml

@@ -21,7 +21,7 @@ In this article, you'll learn how to configure diagnostic logging alerts through
 ## Prerequisites
 
 - If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
-- Before you can complete the steps in this guide, you must first create a [Azure DDoS Protection plan](manage-ddos-protection.md). DDoS Network Protection must be enabled on a virtual network or DDoS IP Protection must be enabled on a public IP address.  
+- [DDoS Network Protection](manage-ddos-protection.md) must be enabled on a virtual network or [DDoS IP Protection (Preview)](manage-ddos-protection-powershell-ip.md) must be enabled on a public IP address. 
 - In order to use diagnostic logging, you must first create a [Log Analytics workspace with diagnostic settings enabled](ddos-configure-log-analytics-workspace.md). 
 - DDoS Protection monitors public IP addresses assigned to resources within a virtual network. If you don't have any resources with public IP addresses in the virtual network, you must first create a resource with a public IP address. You can monitor the public IP address of all resources deployed through Resource Manager (not classic) listed in [Virtual network for Azure services](../virtual-network/virtual-network-for-azure-services.md#services-that-can-be-deployed-into-a-virtual-network) (including Azure Load Balancers where the backend virtual machines are in the virtual network), except for Azure App Service Environments. To continue with this guide, you can quickly create a [Windows](../virtual-machines/windows/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json) or [Linux](../virtual-machines/linux/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json) virtual machine. 
 

articles/ddos-protection/ddos-diagnostic-alert-templates.md

@@ -77,25 +77,25 @@ You can offer savings to customers who commit to an annual or three-year agreeme
 Reservation pricing applies to usage-based monthly billed plans with the following price options:
 
 - Flat rate
-- Per core
-- Per core size
-
+- Per vCPU
+- Per vCPU size
+   
 Reservation pricing doesn’t apply to _Bring your own license_ plans or to plans with the following price options:
 
 - Free
-- Per market and core size price
-
+- Per market and vCPU size price
+   
 #### How prices are calculated
 
 The 1-year and 3-year prices are calculated based on the per hour usage-based price and the percentage savings you configure for a plan.
 
-In this example, we’ll configure a plan with the “Per core” price option as follows:
+In this example, we’ll configure a plan with the “Per vCPU” price option as follows:
 
-- Hourly price per core: $1.
+- Hourly price per vCPU: $1.
 - 1-year savings: 30% discount
 - 3-year savings: 50% discount
 
-All calculations are based on 8,760 hours per year. Without VM software reservation pricing, the yearly cost of a 1 core VM would be $8,760.00. If the customer purchases a VM software reservation, the price would be as follows:
+All calculations are based on 8,760 hours per year. Without VM software reservation pricing, the yearly cost of a 1 vCPU VM would be $8,760.00. If the customer purchases a VM software reservation, the price would be as follows:
 
 1-year price with 30% discount = $6,132.00
 
@@ -169,3 +169,4 @@ When creating your offer in Partner Center, you will see the **Resell through CS
 
 - If you do not yet have an image created for your offer, see [Create a virtual machine using an approved base](azure-vm-use-approved-base.md) or [Create a virtual machine using your own image](azure-vm-use-own-image.md).
 - Once you have an image ready, see [Create a virtual machine offer on Azure Marketplace](azure-vm-offer-setup.md)
+

articles/marketplace/marketplace-virtual-machines.md

@@ -23,7 +23,7 @@ You can have multiple Azure AD admin users with Azure Database for PostgreSQL -
 ## Prerequisites
 
 - An Azure account with an active subscription. If you don't already have one, [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-- One of the following roles: **Global Administrator**, **Privileged Role Administrator**, **Tenant Creator**.
+- One of the following roles: **Global Administrator**, **Privileged Role Administrator**, **Tenant Creator**,**Application Owner**.
 - Installation of the [Azure CLI](/cli/azure/install-azure-cli).
 
 ## Install the Azure AD PowerShell module
@@ -44,7 +44,7 @@ Account          Environment TenantId          TenantDomain
 <your account>   AzureCloud  <your tenant Id>  <your tenant name>.onmicrosoft.com    User
 ```
 
-Ensure that your Azure tenant has the service principal for the Azure Database for PostgreSQL Flexible Server. This only needs to be done once per Azure tenant. First, check for the existence of the service principal in your tenant with this command. The ObjectId value is for the Azure Database for PostgreSQL Flexible Server service principal.
+Ensure that your Azure tenant has the service principal for the Azure Database for PostgreSQL Flexible Server. This only needs to be done once per Azure tenant. First, check for the existence of the service principal in your tenant with this command. **The ObjectId value is for the Azure Database for PostgreSQL Flexible Server service principal.**
 
 > [!NOTE]  
 > The following script is an example of a created Azure App Registration you can use for testing. If you want to apply your ids, you need to use your own App Registration object and application id.
@@ -62,7 +62,7 @@ ObjectId                             AppId                                Displa
 ```
 
 > [!IMPORTANT]  
-> If you are not a **Global Administrator**, **Privileged Role Administrator**, **Tenant Creator** you can't proceed past this step.
+> If you are not a **Global Administrator**, **Privileged Role Administrator**, **Tenant Creator**,**Application Owner** you can't proceed past this step.
 
 ### Grant read access