Merge pull request #197528 from MicrosoftDocs/main

5/09 AM Publish

Author: huypub

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

@@ -278,39 +278,9 @@ You can also specify options to limit the size of the in-memory token cache:
 
 #### Distributed caches
 
-If you use `app.AddDistributedTokenCache`, the token cache is an adapter against the .NET `IDistributedCache` implementation. So you can choose between a distributed memory cache, a SQL Server cache, a Redis cache, or an Azure Cosmos DB cache. For details about the `IDistributedCache` implementations, see [Distributed memory cache](/aspnet/core/performance/caching/distributed).
+If you use `app.AddDistributedTokenCache`, the token cache is an adapter against the .NET `IDistributedCache` implementation. So you can choose between a SQL Server cache, a Redis cache, an Azure Cosmos DB cache, or any other cache implementing the [IDistributedCache](https://docs.microsoft.com/dotnet/api/microsoft.extensions.caching.distributed.idistributedcache?view=dotnet-plat-ext-6.0) interface. 
 
-Here's the code for a distributed in-memory token cache:
-
-```CSharp 
-  // In-memory distributed token cache
-  app.AddDistributedTokenCache(services =>
-  {
-    // In net462/net472, requires to reference Microsoft.Extensions.Caching.Memory
-    services.AddDistributedMemoryCache();
-
-    // Distributed token caches have an L1/L2 mechanism.
-    // L1 is in memory, and L2 is the distributed cache
-    // implementation that you will choose below.
-    // You can configure them to limit the memory of the 
-    // L1 cache, encrypt, and set eviction policies.
-    services.Configure<MsalDistributedTokenCacheAdapterOptions>(options => 
-      {
-        // You can disable the L1 cache if you want
-        options.DisableL1Cache = false;
-        
-        // Or limit the memory (by default, this is 500 MB)
-        options.sizeLimit = 1024 * 1024 * 1024, // 1 GB
-
-        // You can choose to encrypt the cache or not
-        options.Encrypt = false;
-
-        // And you can set eviction policies for the distributed
-        // cache
-        options.SlidingExpiration = TimeSpan.FromHours(1);
-      });
-  });
-```
+For testing purposes only, you may want to use `services.AddDistributedMemoryCache()`, an in-memory implementation of `IDistributedCache`. 
 
 Here's the code for a SQL Server cache:
 
@@ -320,8 +290,7 @@ Here's the code for a SQL Server cache:
      {
       services.AddDistributedSqlServerCache(options =>
       {
-       // In net462/net472, requires to reference Microsoft.Extensions.Caching.Memory
-
+       
        // Requires to reference Microsoft.Extensions.Caching.SqlServer
        options.ConnectionString = @"Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=TestCache;Integrated Security=True;Connect Timeout=30;Encrypt=False;TrustServerCertificate=False;ApplicationIntent=ReadWrite;MultiSubnetFailover=False";
        options.SchemaName = "dbo";

articles/aks/azure-disk-volume.md

@@ -3,7 +3,7 @@ title: Create a static volume for pods in Azure Kubernetes Service (AKS)
 description: Learn how to manually create a volume with Azure disks for use with a pod in Azure Kubernetes Service (AKS)
 services: container-service
 ms.topic: article
-ms.date: 04/01/2019
+ms.date: 05/09/2019
 
 
 #Customer intent: As a developer, I want to learn how to manually create and attach storage to a specific pod in AKS.
@@ -20,9 +20,9 @@ For more information on Kubernetes volumes, see [Storage options for application
 
 ## Before you begin
 
-This article assumes that you have an existing AKS cluster. If you need an AKS cluster, see the AKS quickstart [using the Azure CLI][aks-quickstart-cli], [using Azure PowerShell][aks-quickstart-powershell], or [using the Azure portal][aks-quickstart-portal].
+This article assumes that you have an existing AKS cluster with 1.21 or later version. If you need an AKS cluster, see the AKS quickstart [using the Azure CLI][aks-quickstart-cli], [using Azure PowerShell][aks-quickstart-powershell], or [using the Azure portal][aks-quickstart-portal].
 
-You also need the Azure CLI version 2.0.59 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
+If you want to interact with Azure Disks on an AKS cluster with 1.20 or previous version, see the [Kubernetes plugin for Azure Disks][kubernetes-disks].
 
 ## Create an Azure disk
 
@@ -146,8 +146,6 @@ kubectl apply -f azure-disk-pod.yaml
 
 For associated best practices, see [Best practices for storage and backups in AKS][operator-best-practices-storage].
 
-For more information about AKS clusters interact with Azure disks, see the [Kubernetes plugin for Azure Disks][kubernetes-disks].
-
 <!-- LINKS - external -->
 [kubernetes-disks]: https://github.com/kubernetes/examples/blob/master/staging/volumes/azure_disk/README.md
 [kubernetes-volumes]: https://kubernetes.io/docs/concepts/storage/volumes/

articles/aks/azure-files-volume.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
 description: Learn how to manually create a volume with Azure Files for use with multiple concurrent pods in Azure Kubernetes Service (AKS)
 services: container-service
 ms.topic: article
-ms.date: 04/1/2022
+ms.date: 05/09/2022
 
 
 #Customer intent: As a developer, I want to learn how to manually create and attach storage using Azure Files to a pod in AKS.
@@ -19,9 +19,9 @@ For more information on Kubernetes volumes, see [Storage options for application
 
 ## Before you begin
 
-This article assumes that you have an existing AKS cluster. If you need an AKS cluster, see the AKS quickstart [using the Azure CLI][aks-quickstart-cli], [using Azure PowerShell][aks-quickstart-powershell], or [using the Azure portal][aks-quickstart-portal].
+This article assumes that you have an existing AKS cluster with 1.21 or later version. If you need an AKS cluster, see the AKS quickstart [using the Azure CLI][aks-quickstart-cli], [using Azure PowerShell][aks-quickstart-powershell], or [using the Azure portal][aks-quickstart-portal].
 
-You also need the Azure CLI version 2.0.59 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
+If you want to interact with Azure Files on an AKS cluster with 1.20 or previous version, see the [Kubernetes plugin for Azure Files][kubernetes-files].
 
 ## Create an Azure file share
 
@@ -68,7 +68,7 @@ kubectl create secret generic azure-secret --from-literal=azurestorageaccountnam
 
 ## Mount file share as an inline volume
 > [!NOTE]
-> Inline `azureFile` volume can only access secrets in the same namespace as the pod. To specify a different secret namespace, [please use the persistent volume example][persistent-volume-example] below instead.
+> Inline volume can only access secrets in the same namespace as the pod. To specify a different secret namespace, [please use the persistent volume example][persistent-volume-example] below instead.
 
 To mount the Azure Files share into your pod, configure the volume in the container spec. Create a new file named `azure-files-pod.yaml` with the following contents. If you changed the name of the Files share or secret name, update the *shareName* and *secretName*. If desired, update the `mountPath`, which is the path where the Files share is mounted in the pod. For Windows Server containers, specify a *mountPath* using the Windows path convention, such as *'D:'*.
 
@@ -201,8 +201,6 @@ kubectl apply -f azure-files-pod.yaml
 
 For Azure File CSI driver parameters, see [CSI driver parameters][CSI driver parameters].
 
-For information about AKS 1.20 or below clusters interact with Azure Files, see the [Kubernetes plugin for Azure Files][kubernetes-files].
-
 For associated best practices, see [Best practices for storage and backups in AKS][operator-best-practices-storage].
 
 <!-- LINKS - external -->

articles/application-gateway/ingress-controller-troubleshoot.md

@@ -55,7 +55,7 @@ spec:
     port: 80
     targetPort: 80
 ---
-apiVersion: extensions/v1beta1
+apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: test-agic-app-ingress
@@ -323,4 +323,4 @@ rbac:
 # Specify aks cluster related information. THIS IS BEING DEPRECATED.
 aksClusterConfiguration:
     apiServerAddress: <aks-api-server-address>
-```
+```

articles/automanage/TOC.yml

@@ -40,6 +40,8 @@
     href: repair-automanage-account.md
   - name: Move an Automanaged virtual machine across regions
     href: move-automanaged-vms.md
+  - name: Move an Automanaged configuration profile across regions
+    href: move-automanaged-configuration-profile.md
   - name: Windows Server VNext Datacenter Azure Edition (preview)
     href: windows-server-azure-edition-vnext.md
 - name: Resources

articles/automanage/move-automanaged-configuration-profile.md

@@ -0,0 +1,106 @@
+---
+title: Move an Azure Automanage configuration profile across regions
+description: Learn how to move an Automanage Configuration Profile across regions
+ms.service: automanage
+ms.workload: infrastructure
+ms.topic: how-to
+ms.date: 05/01/2022
+ms.custom: subject-moving-resources
+# Customer intent: As a sysadmin, I want move my Automanage Configuration Profile to a different region.
+---
+
+# Move an Azure Automanage configuration profile to a different region
+This article describes how to migrate an Automanage Configuration Profile to a different region. You might want to move your Configuration Profiles to another region for many reasons. For example, to take advantage of a new Azure region, to meet internal policy and governance requirements, or in response to capacity planning requirements. You may want to deploy Azure Automanage to some VMs that are in a new region.  Some regions may require that you use Automanage Configuration Profiles  that are local to that region.
+
+## Prerequisites
+* Ensure that your target region is [supported by Automanage](./automanage-virtual-machines.md#prerequisites).
+* Ensure that your Log Analytics workspace region, Automation account region, and your target region are all regions supported by the region mappings [here](../automation/how-to/region-mappings.md).
+
+## Download your desired Automanage configuration profile
+
+We'll begin by downloading our previous Configuration Profile using PowerShell.  First, perform a `GET` using `Invoke-RestMethod` against the Automanage Resource Provider, substituting the values for your subscription.
+
+```url
+https://management.azure.com/subscriptions/<yourSubscription>/providers/Microsoft.Automanage/configurationProfiles?api-version=2021-04-30-preview
+```
+
+The GET command will display a list of Automanage Configuration Profile information, including the settings and the ConfigurationProfile ID
+```azurepowershell-interactive
+$listConfigurationProfilesURI = "https://management.azure.com/subscriptions/<yourSubscription>/providers/Microsoft.Automanage/configurationProfiles?api-version=2021-04-30-preview"
+
+Invoke-RestMethod `
+    -URI $listConfigurationProfilesURI
+```
+
+Here are the results, edited for brevity.
+
+```json
+    {
+        "id": "/subscriptions/yourSubscription/resourceGroups/yourResourceGroup/providers/Microsoft.Automanage/configurationProfiles/testProfile1",
+        "name": "testProfile1",
+        "type": "Microsoft.Automanage/configurationProfiles",
+        "location": "westus",
+        "properties": {
+            "configuration": {
+                "Antimalware/Enable": false,
+                "Backup/Enable": true,
+                "Backup/PolicyName": "dailyBackupPolicy",
+            }
+        }
+    },
+    {
+        "id": "/subscriptions/yourSubscription/resourceGroups/yourResourceGroup/providers/Microsoft.Automanage/configurationProfiles/testProfile2",
+        "name": "testProfile2",
+        "type": "Microsoft.Automanage/configurationProfiles",
+        "location": "eastus2euap",
+        "properties": {
+            "configuration": {
+                "Antimalware/Enable": false,
+                "Backup/Enable": true,
+                "Backup/PolicyName": "dailyBackupPolicy",
+            }
+        }
+    }
+```
+
+The next step is to do another `GET`, this time to retrieve the specific profile we would like to create in a new region.  For this example, we'll retrieve 'testProfile1'.  We'll perform a `GET` against the `id` value for the desired profile.
+
+```azurepowershell-interactive
+$profileId = "https://management.azure.com/subscriptions/yourSubscription/resourceGroups/yourResourceGroup/providers/Microsoft.Automanage/configurationProfiles/testProfile1?api-version=2021-04-30-preview"
+
+$profile = Invoke-RestMethod `
+    -URI $listConfigurationProfilesURI
+```
+
+## Adjusting the location
+
+Creating the profile in a new location is as simple as changing the `Location` property to our desired Azure Region.
+
+We also will need to create a new name for this profile.  Let's change the name of the Configuration Profile `profileUk`.  We should update the `Name` property within the profile, and also in the URL.  We can use the `-replace` format operator to make this simple.
+
+```powershell
+$profile.Location = "westeurope"
+$profile.Name -replace "testProfile1", "profileUk"
+$profileId -replace "testProfile1", "profileUk"
+```
+
+Now that we have changed the Location value, this updated Configuration Profile will be created in Western Europe when we submit it. 
+
+## Creating the new profile in the desired location
+
+All that remains now is to `PUT` this new profile, using `Invoke-RestMethod` once more.
+
+```powershell
+$profile = Invoke-RestMethod `
+    -Method PUT `
+    -URI $profileId
+```
+
+## Enable Automanage on your VMs
+For details on how to move your VMs, see this [article](../resource-mover/tutorial-move-region-virtual-machines.md).
+
+Once you've moved your profile to a new region, you may use it as a custom profile for any VM.  Details are available [here](./automanage-virtual-machines.md#enabling-automanage-for-vms-in-azure-portal).
+
+## Next steps
+* [Learn more about Azure Automanage](./automanage-virtual-machines.md)
+* [View frequently asked questions about Azure Automanage](./faq.yml)

articles/availability-zones/az-region.md

@@ -66,7 +66,7 @@ In the Product Catalog, always-available services are listed as "non-regional" s
 
 | **Products**   | **Resiliency**   |
 | --- | --- |
-| [Azure Application Gateway (V2)](../application-gateway/application-gateway-autoscaling-zone-redundant.md) | ![An icon that signifies this service is zonal.](media/icon-zonal.svg)  |
+| [Azure Application Gateway (V2)](../application-gateway/application-gateway-autoscaling-zone-redundant.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) ![An icon that signifies this service is zonal.](media/icon-zonal.svg)  |
 | [Azure Backup](../backup/backup-create-rs-vault.md)  | ![An icon that signifies this service is zonal.](media/icon-zonal.svg)  |
 | [Azure Cosmos DB](../cosmos-db/high-availability.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)   |
 | [Azure DNS: Azure DNS Private Zones](../dns/private-dns-getstarted-portal.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg)  |
@@ -212,4 +212,4 @@ You can access Azure availability zones by using your Azure subscription. To lea
 
 - [Building solutions for high availability using availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability)
 - [High availability with Azure services](/azure/architecture/framework/resiliency/overview)
-- [Design patterns for high availability](/azure/architecture/framework/resiliency/app-design)
+- [Design patterns for high availability](/azure/architecture/framework/resiliency/app-design)

articles/azure-monitor/app/asp-net-troubleshoot-no-data.md

@@ -27,9 +27,11 @@ ms.date: 05/21/2020
 
 * SDK channel keeps telemetry in buffer, and sends them in batches. If the application is shutting down, you might need to explicitly call [Flush()](api-custom-events-metrics.md#flushing-data). Behavior of `Flush()` depends on the actual [channel](telemetry-channels.md#built-in-telemetry-channels) used.
 
+* Per [.NET Core/.NET Framework Console application](worker-service.md#net-corenet-framework-console-application), explicitly calling Flush() followed by sleep is required in Console Apps.
+
 ## Request count collected by Application Insights SDK doesn't match the IIS log count for my application
 
-Internet Information Services (IIS) logs counts of all request reaching IIS and inherently could differ from the total request reaching an application. Due to this, it isn't guaranteed that the request count collected by the SDKs will match the total IIS log count. 
+Internet Information Services (IIS) logs counts of all request reaching IIS and inherently could differ from the total request reaching an application. Due to this behavior, it isn't guaranteed that the request count collected by the SDKs will match the total IIS log count. 
 
 ## No data from my server
 * I installed my app on my web server, and now I don't see any telemetry from it. It worked OK on my dev machine.*
@@ -216,13 +218,13 @@ Performance data (CPU, IO rate, and so on) is available for [Java web services](
 * Have you hit your monthly quota of data points? Open the Settings/Quota and Pricing to find out. If so, you can upgrade your plan, or pay for more capacity. See the [pricing scheme](https://azure.microsoft.com/pricing/details/application-insights/).
 
 ## I don't see all the data I'm expecting
-If your application sends a lot of data and you're using the Application Insights SDK for ASP.NET version 2.0.0-beta3 or later, the [adaptive sampling](./sampling.md) feature may operate and send only a percentage of your telemetry.
+If your application sends considerable data and you're using the Application Insights SDK for ASP.NET version 2.0.0-beta3 or later, the [adaptive sampling](./sampling.md) feature may operate and send only a percentage of your telemetry.
 
-You can disable it, but doing so is not recommended. Sampling is designed so that related telemetry is correctly transmitted, for diagnostic purposes.
+You can disable it, but doing so isn't recommended. Sampling is designed so that related telemetry is correctly transmitted, for diagnostic purposes.
 
 ## Client IP address is 0.0.0.0
 
-On February 5 2018, we announced that we removed logging of the Client IP address. This doesn't affect Geo Location.
+On February 5 2018, we announced that we removed logging of the Client IP address. This recommendation doesn't affect Geo Location.
 
 > [!NOTE]
 > If you need the first 3 octets of the IP address, you can use a [telemetry initializer](./api-filtering-sampling.md#addmodify-properties-itelemetryinitializer) to add a custom attribute.
@@ -243,7 +245,7 @@ Follow these instructions to capture troubleshooting logs for your framework.
 > [!NOTE]
 > Starting in version 2.14, the [Microsoft.AspNet.ApplicationInsights.HostingStartup](https://www.nuget.org/packages/Microsoft.AspNet.ApplicationInsights.HostingStartup) package is no longer necessary, SDK logs are now collected with the [Microsoft.ApplicationInsights](https://www.nuget.org/packages/Microsoft.ApplicationInsights/) package. No additional package is required.
 
-1. Modify your applicationinsights.config file to include the following:
+1. Modify your applicationinsights.config file to include the following XML:
 
     ```xml
     <TelemetryModules>
@@ -305,7 +307,7 @@ For more information,
 
 ## Collect logs with dotnet-trace
 
-Alternatively, customers can also use a cross-platform .NET Core tool, [`dotnet-trace`](/dotnet/core/diagnostics/dotnet-trace) for collecting logs that can further help in troubleshooting. This may be helpful for linux-based environments.
+Alternatively, customers can also use a cross-platform .NET Core tool, [`dotnet-trace`](/dotnet/core/diagnostics/dotnet-trace) for collecting logs that can further help in troubleshooting. This tool may be helpful for linux-based environments.
 
 After installation of [`dotnet-trace`](/dotnet/core/diagnostics/dotnet-trace), execute the command below in bash.