Skip to content

Commit e12b28f

Browse files
authored
Merge pull request #223488 from MicrosoftDocs/main
Publish to live, Tuesday 4 AM PST, 1/10
2 parents 2fa09d6 + 14b54b8 commit e12b28f

File tree

161 files changed

+1642
-972
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

161 files changed

+1642
-972
lines changed

articles/active-directory-b2c/best-practices.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,13 @@ title: Best practices for Azure AD B2C
33
titleSuffix: Azure AD B2C
44
description: Recommendations and best practices to consider when working with Azure Active Directory B2C (Azure AD B2C).
55
services: active-directory-b2c
6-
author: vigunase
7-
ms.author: vigunase
6+
author: kengaderdus
7+
ms.author: kengaderdus
88
manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: conceptual
12-
ms.date: 12/01/2022
12+
ms.date: 12/29/2022
1313
ms.subservice: B2C
1414
---
1515

@@ -75,6 +75,7 @@ Manage your Azure AD B2C environment.
7575
| Use version control for your custom policies | Consider using GitHub, Azure Repos, or another cloud-based version control system for your Azure AD B2C custom policies. |
7676
| Use the Microsoft Graph API to automate the management of your B2C tenants | Microsoft Graph APIs:<br/>Manage [Identity Experience Framework](/graph/api/resources/trustframeworkpolicy?preserve-view=true&view=graph-rest-beta) (custom policies)<br/>[Keys](/graph/api/resources/trustframeworkkeyset?preserve-view=true&view=graph-rest-beta)<br/>[User Flows](/graph/api/resources/identityuserflow?preserve-view=true&view=graph-rest-beta) |
7777
| Integrate with Azure DevOps | A [CI/CD pipeline](deploy-custom-policies-devops.md) makes moving code between different environments easy and ensures production readiness always. |
78+
| Custom policy deployment | Azure AD B2C relies on caching to deliver performance to your end users. When you deploy a custom policy using whatever method, expect a delay of up to **30 minutes** for your users to see the changes. As a result of this behavior, consider the following practices when you deploy your custom policies: <br> - If you're deploying to a development environment, set the `DeploymentMode` attribute to `Development` in your custom policy file's `<TrustFrameworkPolicy>` element. <br> - Deploy your updated policy files to a production environment when traffic in your app is low. <br> - When you deploy to a production environment to update existing policy files, upload the updated files with new name(s), and then update your app reference to the new name(s). You can then remove the old policy files afterwards.<br> - You can set the `DeploymentMode` to `Development` in a production environment to bypass the caching behavior. However, we don't recommend this practice. If you [Collect Azure AD B2C logs with Application Insights](troubleshoot-with-application-insights.md), all claims sent to and from identity providers are collected, which is a security and performance risk. |
7879
| Integrate with Azure Monitor | [Audit log events](view-audit-logs.md) are only retained for seven days. [Integrate with Azure Monitor](azure-monitor.md) to retain the logs for long-term use, or integrate with third-party security information and event management (SIEM) tools to gain insights into your environment. |
7980
| Setup active alerting and monitoring | [Track user behavior](./analytics-with-application-insights.md) in Azure AD B2C using Application Insights. |
8081

articles/aks/azure-cni-overlay.md

Lines changed: 10 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -129,31 +129,15 @@ az provider register --namespace Microsoft.ContainerService
129129

130130
## Set up overlay clusters
131131

132-
The following steps create a new virtual network with a subnet for the cluster nodes and an AKS cluster that uses Azure CNI Overlay.
133-
134-
1. Create a virtual network with a subnet for the cluster nodes. Replace the values for the variables `resourceGroup`, `vnet` and `location`.
135-
136-
```azurecli-interactive
137-
resourceGroup="myResourceGroup"
138-
vnet="myVirtualNetwork"
139-
location="westcentralus"
140-
141-
# Create the resource group
142-
az group create --name $resourceGroup --location $location
143-
144-
# Create a VNet and a subnet for the cluster nodes
145-
az network vnet create -g $resourceGroup --location $location --name $vnet --address-prefixes 10.0.0.0/8 -o none
146-
az network vnet subnet create -g $resourceGroup --vnet-name $vnet --name nodesubnet --address-prefix 10.10.0.0/16 -o none
147-
```
148-
149-
2. Create a cluster with Azure CNI Overlay. Use the argument `--network-plugin-mode` to specify that this is an overlay cluster. If the pod CIDR is not specified then AKS assigns a default space, viz. 10.244.0.0/16. Replace the values for the variables `clusterName` and `subscription`.
150-
151-
```azurecli-interactive
152-
clusterName="myOverlayCluster"
153-
subscription="aaaaaaa-aaaaa-aaaaaa-aaaa"
154-
155-
az aks create -n $clusterName -g $resourceGroup --location $location --network-plugin azure --network-plugin-mode overlay --pod-cidr 192.168.0.0/16 --vnet-subnet-id /subscriptions/$subscription/resourceGroups/$resourceGroup/providers/Microsoft.Network/virtualNetworks/$vnet/subnets/nodesubnet
156-
```
132+
Create a cluster with Azure CNI Overlay. Use the argument `--network-plugin-mode` to specify that this is an overlay cluster. If the pod CIDR is not specified then AKS assigns a default space, viz. 10.244.0.0/16. Replace the values for the variables `clusterName`, `resourceGroup`, and `location`.
133+
134+
```azurecli-interactive
135+
clusterName="myOverlayCluster"
136+
resourceGroup="myResourceGroup"
137+
location="westcentralus"
138+
139+
az aks create -n $clusterName -g $resourceGroup --location $location --network-plugin azure --network-plugin-mode overlay --pod-cidr 192.168.0.0/16
140+
```
157141

158142
## Next steps
159143

@@ -162,4 +146,4 @@ To learn how to utilize AKS with your own Container Network Interface (CNI) plug
162146
<!-- LINKS - internal -->
163147
[az-provider-register]: /cli/azure/provider#az-provider-register
164148
[az-feature-register]: /cli/azure/feature#az-feature-register
165-
[az-feature-show]: /cli/azure/feature#az-feature-show
149+
[az-feature-show]: /cli/azure/feature#az-feature-show

articles/aks/azure-cni-powered-by-cilium.md

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,6 @@ Create the cluster using `--enable-cilium-dataplane`:
112112
```azurecli-interactive
113113
az aks create -n <clusterName> -g <resourceGroupName> -l <location> \
114114
--max-pods 250 \
115-
--node-count 2 \
116115
--network-plugin azure \
117116
--vnet-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/nodesubnet \
118117
--pod-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/podsubnet \
@@ -121,29 +120,13 @@ az aks create -n <clusterName> -g <resourceGroupName> -l <location> \
121120

122121
### Option 2: Assign IP addresses from an overlay network
123122

124-
Run these commands to create a resource group and VNet with a single subnet:
125-
126-
```azurecli-interactive
127-
# Create the resource group
128-
az group create --name <resourceGroupName> --location <location>
129-
```
130-
131-
```azurecli-interactive
132-
# Create a VNet with a subnet for nodes and a subnet for pods
133-
az network vnet create -g <resourceGroupName> --location <location> --name <vnetName> --address-prefixes <address prefix, example: 10.0.0.0/8> -o none
134-
az network vnet subnet create -g <resourceGroupName> --vnet-name <vnetName> --name nodesubnet --address-prefixes <address prefix, example: 10.240.0.0/16> -o none
135-
```
136-
137-
Then create the cluster using `--enable-cilium-dataplane`:
123+
Run this commands to create a cluster with an overlay network and Cilium. Replace the values for `<clusterName>`, `<resourceGroupName>`, and `<location>`:
138124

139125
```azurecli-interactive
140126
az aks create -n <clusterName> -g <resourceGroupName> -l <location> \
141-
--max-pods 250 \
142-
--node-count 2 \
143127
--network-plugin azure \
144128
--network-plugin-mode overlay \
145129
--pod-cidr 192.168.0.0/16 \
146-
--vnet-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/nodesubnet \
147130
--enable-cilium-dataplane
148131
```
149132

articles/aks/use-kms-etcd-encryption.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Key Management Service (KMS) etcd encryption in Azure Kubernetes Serv
33
description: Learn how to use the Key Management Service (KMS) etcd encryption with Azure Kubernetes Service (AKS)
44
services: container-service
55
ms.topic: article
6-
ms.date: 12/17/2022
6+
ms.date: 01/09/2023
77
---
88

99
# Add Key Management Service (KMS) etcd encryption to an Azure Kubernetes Service (AKS) cluster
@@ -32,6 +32,7 @@ The following limitations apply when you integrate KMS etcd encryption with AKS:
3232

3333
* Deletion of the key, Key Vault, or the associated identity isn't supported.
3434
* KMS etcd encryption doesn't work with system-assigned managed identity. The key vault access policy is required to be set before the feature is enabled. In addition, system-assigned managed identity isn't available until cluster creation, thus there's a cycle dependency.
35+
* Azure Key Vault with Firewall enabled to allow public access isn't supported because it blocks traffic from KMS plugin to the Key Vault.
3536
* The maximum number of secrets that a cluster enabled with KMS supports is 2,000.
3637
* Bring your own (BYO) Azure Key Vault from another tenant isn't supported.
3738
* With KMS enabled, you can't change associated Azure Key Vault model (public, private). To [change associated key vault mode][changing-associated-key-vault-mode], you need to disable and enable KMS again.
@@ -282,6 +283,8 @@ After changing the key ID (including key name and key version), you can use [az
282283

283284
> [!WARNING]
284285
> Remember to update all secrets after key rotation. Otherwise, the secrets will be inaccessible if the old keys are not existing or working.
286+
>
287+
> Once you rotate the key, the old key (key1) is still cached and shouldn't be deleted. If you want to delete the old key (key1) immediately, you need to rotate the key twice. Then key2 and key3 are cached, and key1 can be deleted without impacting existing cluster.
285288
286289
```azurecli-interactive
287290
az aks update --name myAKSCluster --resource-group MyResourceGroup --enable-azure-keyvault-kms --azure-keyvault-kms-key-id $NewKEY_ID --azure-keyvault-kms-key-vault-network-access "Private" --azure-keyvault-kms-key-vault-resource-id $KEYVAULT_RESOURCE_ID

articles/automation/automation-role-based-access-control.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Manage role permissions and security in Azure Automation
33
description: This article describes how to use Azure role-based access control (Azure RBAC), which enables access management and role permissions for Azure resources.
44
services: automation
55
ms.subservice: shared-capabilities
6-
ms.date: 09/10/2021
6+
ms.date: 01/09/2023
77
ms.topic: how-to
88
ms.custom: devx-track-azurepowershell, subject-rbac-steps
99
#Customer intent: As an administrator, I want to understand permissions so that I use the least necessary set of permissions.
@@ -322,6 +322,9 @@ Update Management can be used to assess and schedule update deployments to machi
322322
|Create update schedule ([Software Update Configurations](/rest/api/automation/softwareupdateconfigurations)) |Microsoft.Compute/virtualMachines/write |For static VM list and resource groups |
323323
|Create update schedule ([Software Update Configurations](/rest/api/automation/softwareupdateconfigurations)) |Microsoft.OperationalInsights/workspaces/analytics/query/action |For workspace resource ID when using non-Azure dynamic list.|
324324

325+
>[!NOTE]
326+
>When you use Update management, ensure that the execution policy for scripts is *RemoteSigned*.
327+
325328
## Configure Azure RBAC for your Automation account
326329

327330
The following section shows you how to configure Azure RBAC on your Automation account through the [Azure portal](#configure-azure-rbac-using-the-azure-portal) and [PowerShell](#configure-azure-rbac-using-powershell).

articles/azure-monitor/agents/azure-monitor-agent-windows-client.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article describes the instructions to install the agent on Win
44
ms.topic: conceptual
55
author: shseth
66
ms.author: shseth
7-
ms.date: 10/18/2022
7+
ms.date: 1/9/2023
88
ms.custom: references_region
99
ms.reviewer: shseth
1010

@@ -329,20 +329,23 @@ In order to update the version, install the new version you wish to update to.
329329
3. The 'ServiceLogs' folder contains log from AMA Windows Service, which launches and manages AMA processes
330330
4. 'AzureMonitorAgent.MonitoringDataStore' contains data/logs from AMA processes.
331331

332-
### Common issues
332+
### Common installation issues
333333

334334
#### Missing DLL
335335
- Error message: "There's a problem with this Windows Installer package. A DLL required for this installer to complete could not be run. …"
336336
- Ensure you have installed [C++ Redistributable (>2015)](/cpp/windows/latest-supported-vc-redist?view=msvc-170&preserve-view=true) before installing AMA:
337337

338+
#### Not AAD joined
339+
Error message: "Tenant and device ids retrieval failed"
340+
1. Run the command `dsregcmd /status`. This should produce the output as `AzureAdJoined : YES` in the 'Device State' section. If not, join the device with an AAD tenant and try installation again.
341+
338342
#### Silent install from command prompt fails
339343
Make sure to start the installer on administrator command prompt. Silent install can only be initiated from the administrator command prompt.
340344

341345
#### Uninstallation fails due to the uninstaller being unable to stop the service
342346
- If There's an option to try again, do try it again
343347
- If retry from uninstaller doesn't work, cancel the uninstall and stop Azure Monitor Agent service from Services (Desktop Application)
344348
- Retry uninstall
345-
346349
#### Force uninstall manually when uninstaller doesn't work
347350
- Stop Azure Monitor Agent service. Then try uninstalling again. If it fails, then proceed with the following steps
348351
- Delete AMA service with "sc delete AzureMonitorAgent" from admin cmd
@@ -351,6 +354,8 @@ Make sure to start the installer on administrator command prompt. Silent install
351354
- Delete AMA data/logs. They're stored in `C:\Resources\Azure Monitor Agent` by default
352355
- Open Registry. Check `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure Monitor Agent`. If it exists, delete the key.
353356

357+
### Post installation/Operational issues
358+
Once the agent is installed successfully (i.e. you see the agent service running but don't see data as expected), you can follow standard troubleshooting steps listed here for [Windows VM](./azure-monitor-agent-troubleshoot-windows-vm.md) and [Windows Arc-enabled server](azure-monitor-agent-troubleshoot-windows-arc.md) respectively.
354359

355360
## Questions and feedback
356361
Take this [quick survey](https://forms.microsoft.com/r/CBhWuT1rmM) or share your feedback/questions regarding the client installer.

articles/azure-monitor/app/asp-net-dependencies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Dependency tracking in Application Insights | Microsoft Docs
33
description: Monitor dependency calls from your on-premises or Azure web application with Application Insights.
44
ms.topic: conceptual
5-
ms.date: 12/13/2022
5+
ms.date: 01/09/2023
66
ms.devlang: csharp
77
ms.custom: devx-track-csharp
88
ms.reviewer: casocha

articles/azure-monitor/app/availability-azure-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create and run custom availability tests by using Azure Functions
33
description: This article explains how to create an Azure function with TrackAvailability() that will run periodically according to the configuration given in a TimerTrigger function.
44
ms.topic: conceptual
5-
ms.date: 05/06/2021
5+
ms.date: 01/06/2023
66
ms.devlang: csharp
77
---
88

articles/azure-monitor/app/azure-web-apps-net-core.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Monitor Azure App Service performance in .NET Core | Microsoft Docs
33
description: Application performance monitoring for Azure App Service using ASP.NET Core. Chart load and response time, dependency information, and set alerts on performance.
44
ms.topic: conceptual
5-
ms.date: 11/15/2022
5+
ms.date: 01/09/2023
66
ms.devlang: csharp
77
ms.custom: devx-track-dotnet
88
ms.reviewer: abinetabate

articles/azure-monitor/app/codeless-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Monitor your apps without code changes - auto-instrumentation for Azure Monitor Application Insights | Microsoft Docs
33
description: Overview of auto-instrumentation for Azure Monitor Application Insights - codeless application performance management
44
ms.topic: conceptual
5-
ms.date: 10/19/2022
5+
ms.date: 01/06/2023
66
ms.reviewer: abinetabate
77
---
88

0 commit comments

Comments
 (0)