Updates from: 04/10/2023 01:53:52
Service Microsoft Docs article Related commit history on GitHub Change details
active-directory-b2c Manage Custom Policies Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory-b2c/manage-custom-policies-powershell.md
+ Last updated 02/14/2020
active-directory-domain-services Ad Auth No Join Linux Vm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory-domain-services/ad-auth-no-join-linux-vm.md
Currently Linux distribution can work as member of Active Directory domains, whi
To complete the authentication flow we assume, you already have: * An Active Directory Domain Services already configured.
-* A Linux VM (for the test we use CentosOS based machine).
+* A Linux VM (**for the test we use CentosOS based machine**).
* A network infrastructure that allows communication between Active Directory and the Linux VM. * A dedicated User Account for read AD objects. * The Linux VM need to have these packages installed:
Review the information that you provided, and if everything is correct, click Fi
On your Linux VM, install the following packages: *sssd sssd-tools sssd-ldap openldap-client*:
-```console
-yum install -y sssd sssd-tools sssd-ldap openldap-clients
+```bash
+sudo dnf install -y sssd sssd-tools sssd-ldap openldap-clients
``` After the installation check if LDAP search works. In order to check it try an LDAP search following the example below:
-```console
-ldapsearch -H ldaps://contoso.com -x \
+```bash
+sudo ldapsearch -H ldaps://contoso.com -x \
-D CN=ReadOnlyUser,CN=Users,DC=contoso,DC=com -w Read0nlyuserpassword \ -b CN=Users,DC=contoso,DC=com ``` If the LDAP query works fine, you will obtain an output with some information like follow:
-```console
+```config
extended LDIF LDAPv3
dSCorePropagationData: 16010101000000.0Z
> [!NOTE] > If your get and error run the following command: >
-> ldapsearch -H ldaps://contoso.com -x \
+> sudo ldapsearch -H ldaps://contoso.com -x \
> -D CN=ReadOnlyUser,CN=Users,DC=contoso,DC=com -w Read0nlyuserpassword \ > -b CN=Users,DC=contoso,DC=com -d 3 >
Create */etc/sssd/sssd.conf* with a content like the following. Remember to upda
Command for file creation:
-```console
-vi /etc/sssd/sssd.conf
+```bash
+sudo vi /etc/sssd/sssd.conf
``` Example sssd.conf:
-```bash
+```config
[sssd] config_file_version = 2 domains = default
Save the file with *ESC + wq!* command.
Set the permission to sssd.conf to 600 with the following command:
-```console
-chmod 600 /etc/sssd/sssd.conf
+```bash
+sudo chmod 600 /etc/sssd/sssd.conf
``` After that create an obfuscated password for the Bind DN account. You must insert the Domain password for ReadOnlyUser:
-```console
-sss_obfuscate --domain default
+```bash
+sudo sss_obfuscate --domain default
``` The password will be placed automatically in the configuration file.
The password will be placed automatically in the configuration file.
Start the sssd service:
-```console
-service sssd start
+```bash
+sudo systemctl start sssd
``` Now configure the service with the *authconfig* tool:
-```console
-authconfig --enablesssd --enablesssdauth --enablemkhomedir --updateall
+```bash
+sudo authconfig --enablesssd --enablesssdauth --enablemkhomedir --updateall
``` At this point restart the service:
-```console
-systemctl restart sssd
+```bash
+sudo systemctl restart sssd
``` ## Test the configuration The final step is to check that the flow works properly. To check this, try logging in with one of your AD users in Active Directory. We tried with a user called *ADUser*. If the configuration is correct, you will get the following result:
-```console
+```output
[centosuser@centos8 ~]su - ADUser@contoso.com Last login: Wed Oct 12 15:13:39 UTC 2022 on pts/0 [ADUser@Centos8 ~]$ exit
active-directory-domain-services Join Windows Vm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory-domain-services/join-windows-vm-template.md
ms.assetid: 4eabfd8e-5509-4acd-86b5-1318147fddb5
+ Last updated 01/29/2023
active-directory-domain-services Template Create Instance https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory-domain-services/template-create-instance.md
+ Last updated 01/29/2023
active-directory Howto Create Service Principal Portal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/develop/howto-create-service-principal-portal.md
Last updated 02/01/2023 -+ # Create an Azure Active Directory application and service principal that can access resources
To configure access policies:
- Learn how to use [Azure PowerShell](howto-authenticate-service-principal-powershell.md) or [Azure CLI](/cli/azure/create-an-azure-service-principal-azure-cli) to create a service principal. - To learn about specifying security policies, see [Azure role-based access control (Azure RBAC)](../../role-based-access-control/role-assignments-portal.md). - For a list of available actions that can be granted or denied to users, see [Azure Resource Manager Resource Provider operations](../../role-based-access-control/resource-provider-operations.md).-- For information about working with app registrations by using **Microsoft Graph**, see the [Applications](/graph/api/resources/application) API reference.
+- For information about working with app registrations by using **Microsoft Graph**, see the [Applications](/graph/api/resources/application) API reference.
active-directory Migrate From Federation To Cloud Authentication https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/hybrid/migrate-from-federation-to-cloud-authentication.md
Modern authentication clients (Office 2016 and Office 2013, iOS, and Android app
To plan for rollback, use the [documented current federation settings](#document-current-federation-settings) and check the [federation design and deployment documentation](/windows-server/identity/ad-fs/deployment/windows-server-2012-r2-ad-fs-deployment-guide).
-The rollback process should include converting managed domains to federated domains by using the [Convert-MSOLDomainToFederated](/powershell/module/msonline/convert-msoldomaintofederated) cmdlet. If necessary, configuring extra claims rules.
+The rollback process should include converting managed domains to federated domains by using the [Convert-MSOLDomainToFederated](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true) cmdlet. If necessary, configuring extra claims rules.
## Migration considerations
The following table explains the behavior for each option. For more information,
| rejectMfaByFederatedIdp | Azure AD always performs MFA and rejects MFA that federated identity provider performs. | >[!NOTE]
-> The **federatedIdpMfaBehavior** setting is an evolved version of the **SupportsMfa** property of the [Set-MsolDomainFederationSettings MSOnline v1 PowerShell cmdlet](/powershell/module/msonline/set-msoldomainfederationsettings).
+> The **federatedIdpMfaBehavior** setting is an evolved version of the **SupportsMfa** property of the [Set-MsolDomainFederationSettings MSOnline v1 PowerShell cmdlet](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true).
For domains that have already set the **SupportsMfa** property, these rules determine how **federatedIdpMfaBehavior** and **SupportsMfa** work together:
Sign in to the [Azure portal](https://portal.azure.com/), browse to **Azure Acti
4. On the **User sign-in** page:
- - If you select **Pass-through authentication** option button, check **Enable single sign-on**, and then select **Next**.
+ - If you select **Pass-through authentication** option button, and if SSO is needed for Windows 7 and 8.1 devices, check **Enable single sign-on**, and then select **Next**.
- - If you select the **Password hash synchronization** option button, make sure to select the **Do not convert user accounts** check box. The option is deprecated. Check **Enable single sign-on**, and then select **Next**.
+ - If you select the **Password hash synchronization** option button, make sure to select the **Do not convert user accounts** check box. The option is deprecated. If SSO is needed for Windows 7 and 8.1 devices, check **Enable single sign-on**, and then select **Next**.
![Check enable single sign-on on User sign-in page](media/deploy-cloud-user-authentication/user-sign-in.png)
+ Learn more: [Enable seamless SSO by using PowerShell](how-to-connect-staged-rollout.md#pre-work-for-seamless-sso).
5. On the **Enable single sign-on** page, enter the credentials of a Domain Administrator account, and then select **Next**. ![Enable single sign-on page](media/deploy-cloud-user-authentication/enable-single-sign-on.png)
Sign in to the [Azure portal](https://portal.azure.com/), browse to **Azure Acti
The domain administrator credentials aren't stored in Azure AD Connect or Azure AD and get discarded when the process successfully finishes. They are used to turn ON this feature.
+ Learn more: [Seamless SSO technical deep dive.](how-to-connect-sso-how-it-works.md)
+ 6. On the **Ready to configure** page, make sure that the **Start the synchronization process when configuration completes** check box is selected. Then, select **Configure**. ![Ready to configure page](media/deploy-cloud-user-authentication/ready-to-configure.png)
active-directory Create Service Principal Cross Tenant https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/manage-apps/create-service-principal-cross-tenant.md
Last updated 07/26/2022 -+ zone_pivot_groups: enterprise-apps-cli-- #Customer intent: As an administrator of an Azure AD tenant, I want to create an enterprise application using client ID for a multi-tenant application provided by a service provider or independent software vendor.
You can use an API client such as [Graph Explorer](https://aka.ms/ge) to work wi
## Next steps - [Add RBAC role to the enterprise application](../../role-based-access-control/role-assignments-portal.md)-- [Assign users to your application](add-application-portal-assign-users.md)
+- [Assign users to your application](add-application-portal-assign-users.md)
active-directory How To Use Vm Sign In https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/how-to-use-vm-sign-in.md
ms.tool: azure-cli, azure-powershell ms.devlang: azurecli+ # How to use managed identities for Azure resources on an Azure VM for sign-in
active-directory Msi Tutorial Linux Vm Access Arm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/msi-tutorial-linux-vm-access-arm.md
na+ Last updated 01/11/2022
active-directory Qs Configure Template Windows Vm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/qs-configure-template-windows-vm.md
Last updated 01/11/2022 -+ # Configure managed identities for Azure resources on an Azure VM using templates
active-directory Qs Configure Template Windows Vmss https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/qs-configure-template-windows-vmss.md
Last updated 01/11/2022 -+ # Configure managed identities for Azure resources on an Azure virtual machine scale using a template
active-directory Tutorial Linux Vm Access Arm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-arm.md
Last updated 01/11/2022 -+ # Use a Linux VM system-assigned managed identity to access Azure Resource Manager
active-directory Tutorial Linux Vm Access Nonaad https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-nonaad.md
na+ Last updated 01/11/2022
active-directory Tutorial Linux Vm Access Storage Access Key https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-storage-access-key.md
documentationcenter: ''
editor: daveba--+
active-directory Tutorial Linux Vm Access Storage Sas https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-storage-sas.md
documentationcenter: '' -+
active-directory Tutorial Vm Managed Identities Cosmos https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-vm-managed-identities-cosmos.md
Last updated 03/31/2023 -+ ms.tool: azure-cli, azure-powershell ms.devlang: azurecli #Customer intent: As an administrator, I want to know how to access Azure Cosmos DB from a virtual machine using a managed identity
active-directory Tutorial Windows Vm Access Arm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-arm.md
documentationcenter: ''
editor: daveba-+
active-directory Tutorial Windows Vm Access Storage Sas https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-storage-sas.md
Last updated 01/11/2022 -+ # Tutorial: Use a Windows VM system-assigned managed identity to access Azure Storage via a SAS credential
active-directory Tutorial Windows Vm Ua Arm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-ua-arm.md
Last updated 01/11/2022 -+ # Tutorial: Use a user-assigned managed identity on a Windows VM to access Azure Resource Manager
active-directory Reference Azure Ad Sla Performance https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md
The SLA attainment is truncated at three places after the decimal. Numbers are n
| | | | | | January | | 99.998% | 99.998% | | February | 99.999% | 99.999% | 99.999% |
-| March | 99.568% | 99.998% | |
+| March | 99.568% | 99.998% | 99.999% |
| April | 99.999% | 99.999% | | | May | 99.999% | 99.999% | | | June | 99.999% | 99.999% | |
active-directory Assign Roles Different Scopes https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/roles/assign-roles-different-scopes.md
# Assign Azure AD roles at different scopes
-In Azure Active Directory (Azure AD), you typically assign Azure AD roles so that they apply to the entire tenant. However, you can also assign Azure AD roles for different resources, such as administrative units or application registrations. For example, you could assign the Helpdesk Administrator role so that it just applies to a particular administrative unit and not the entire tenant. The resources that a role assignment applies to is also call the scope. This article describes how to assign Azure AD roles at tenant, administrative unit, and application registration scopes. For more information about scope, see [Overview of RBAC in Azure AD](custom-overview.md#scope).
+In Azure Active Directory (Azure AD), you typically assign Azure AD roles so that they apply to the entire tenant. However, you can also assign Azure AD roles for different resources, such as administrative units or application registrations. For example, you could assign the Helpdesk Administrator role so that it just applies to a particular administrative unit and not the entire tenant. The resources that a role assignment applies to is also called the scope. This article describes how to assign Azure AD roles at tenant, administrative unit, and application registration scopes. For more information about scope, see [Overview of RBAC in Azure AD](custom-overview.md#scope).
## Prerequisites
This section describes how to assign roles at the tenant scope.
1. Select **Azure Active Directory** > **Roles and administrators** to see the list of all available roles.
- ![Roles and administrators page in Azure Active Directory.](./media/manage-roles-portal/roles-and-administrators.png)
+ ![Roles and administrators page in Azure Active Directory.](./media/common/roles-and-administrators.png)
1. Select a role to see its assignments. To help you find the role you need, use **Add filters** to filter the roles.
active-directory Custom Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/roles/custom-overview.md
Previously updated : 10/06/2021 Last updated : 04/10/2023
# Overview of role-based access control in Azure Active Directory
-This article describes how to understand Azure Active Directory (Azure AD) role-based access control. Azure AD roles allow you to grant granular permissions to your admins, abiding by the principle of least privilege. Azure AD built-in and custom roles operate on concepts similar to those you will find in [the role-based access control system for Azure resources](../../role-based-access-control/overview.md) (Azure roles). The [difference between these two role-based access control systems](../../role-based-access-control/rbac-and-directory-admin-roles.md) is:
+This article describes how to understand Azure Active Directory (Azure AD) role-based access control. Azure AD roles allow you to grant granular permissions to your admins, abiding by the principle of least privilege. Azure AD built-in and custom roles operate on concepts similar to those you find in [the role-based access control system for Azure resources](../../role-based-access-control/overview.md) (Azure roles). The [difference between these two role-based access control systems](../../role-based-access-control/rbac-and-directory-admin-roles.md) is:
- Azure AD roles control access to Azure AD resources such as users, groups, and applications using the Microsoft Graph API - Azure roles control access to Azure resources such as virtual machines or storage using Azure Resource Management
This article describes how to understand Azure Active Directory (Azure AD) role-
Both systems contain similarly used role definitions and role assignments. However, Azure AD role permissions can't be used in Azure custom roles and vice versa. ## Understand Azure AD role-based access control
-Azure AD supports 2 types of roles definitions:
+
+Azure AD supports two types of roles definitions:
+ * [Built-in roles](./permissions-reference.md) * [Custom roles](./custom-create.md)
The following diagram shows an example of a role assignment. In this example, Ch
### Security principal
-A security principal represents a user, group, or service principal that is assigned access to Azure AD resources. A user is an individual who has a user profile in Azure Active Directory. A group is a new Microsoft 365 or security group with the isAssignableToRole property set to true (currently in preview). A service principal is an identity created for use with applications, hosted services, and automated tools to access Azure AD resources.
+A security principal represents a user, group, or service principal that is assigned access to Azure AD resources. A user is an individual who has a user profile in Azure Active Directory. A group is a new Microsoft 365 or security group that has been set as a [role-assignable group](groups-concept.md). A service principal is an identity created for use with applications, hosted services, and automated tools to access Azure AD resources.
### Role definition
If you specify an Azure AD resource as a scope, it can be one of the following:
For more information, see [Assign Azure AD roles at different scopes](assign-roles-different-scopes.md).
+## Role assignment options
+
+Azure AD provides multiple options for assigning roles:
+
+- You can assign roles to users directly, which is the default way to assign roles. Both built-in and custom Azure AD roles can be assigned to users, based on access requirements. For more information, see [Assign Azure AD roles to users](manage-roles-portal.md).
+- With Azure AD Premium P1, you can create role-assignable groups and assign roles to these groups. Assigning roles to a group instead of individuals allows for easy addition or removal of users from a role and creates consistent permissions for all members of the group. For more information, see [Assign Azure AD roles to groups](groups-assign-role.md).
+- With Azure AD Premium P2, you can use Azure AD Privileged Identity Management (Azure AD PIM) to provide just-in-time access to roles. This feature allows you to grant time-limited access to a role to users who require it, rather than granting permanent access. It also provides detailed reporting and auditing capabilities. For more information, see [Assign Azure AD roles in Privileged Identity Management](../privileged-identity-management/pim-how-to-add-role-to-user.md).
+ ## License requirements
-Using built-in roles in Azure AD is free, while custom roles requires an Azure AD Premium P1 license. To find the right license for your requirements, see [Comparing generally available features of the Free and Premium editions](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
+Using built-in roles in Azure AD is free, while custom roles require an Azure AD Premium P1 license. To find the right license for your requirements, see [Comparing generally available features of the Free and Premium editions](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
## Next steps
active-directory Groups Assign Role https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/roles/groups-assign-role.md
Title: Assign Azure AD roles to groups
-description: Assign Azure AD roles to role-assignable groups in the Azure portal, PowerShell, or Graph API.
+description: Assign Azure AD roles to role-assignable groups in the Azure portal, PowerShell, or Microsoft Graph API.
Previously updated : 02/04/2022 Last updated : 04/10/2023
# Assign Azure AD roles to groups
-This section describes how an IT admin can assign Azure Active Directory (Azure AD) role to an Azure AD group.
+To simplify role management, you can assign Azure AD roles to a group instead of individuals. This article describes how to assign Azure AD roles to [role-assignable groups](groups-concept.md) using the Azure portal, PowerShell, or Microsoft Graph API.
## Prerequisites -- Azure AD Premium P1 or P2 license-- Privileged Role Administrator or Global Administrator-- AzureAD module when using PowerShell
+- Azure AD Premium P1 license
+- [Privileged Role Administrator](./permissions-reference.md#privileged-role-administrator) role
+- Microsoft.Graph module when using [Microsoft Graph PowerShell](/powershell/microsoftgraph/installation?branch=main)
+- AzureAD module when using [Azure AD PowerShell](/powershell/azure/active-directory/overview?branch=main)
- Admin consent when using Graph explorer for Microsoft Graph API For more information, see [Prerequisites to use PowerShell or Graph Explorer](prerequisites.md). ## Azure portal
-Assigning a group to an Azure AD role is similar to assigning users and service principals except that only groups that are role-assignable can be used. In the Azure portal, only groups that are role-assignable are displayed.
+Assigning an Azure AD role to a group is similar to assigning users and service principals except that only groups that are role-assignable can be used.
-1. Sign in to the [Azure portal](https://portal.azure.com).
+> [!TIP]
+> These steps apply to customers that have an Azure AD Premium P1 license. If you have an Azure AD Premium P2 license in your tenant, you should instead follow steps in [Assign Azure AD roles in Privileged Identity Management](../privileged-identity-management/pim-how-to-add-role-to-user.md).
-1. Select **Azure Active Directory** > **Roles and administrators** and select the role you want to assign.
+1. Sign in to the [Azure portal](https://portal.azure.com) or [Microsoft Entra admin center](https://entra.microsoft.com).
-1. On the ***role name*** page, select > **Add assignment**.
+1. Select **Azure Active Directory** > **Roles and administrators** to see the list of all available roles.
- ![Add the new role assignment](./media/groups-assign-role/add-assignment.png)
+ :::image type="content" source="media/common/roles-and-administrators.png" alt-text="Screenshot of Roles and administrators page in Azure Active Directory." lightbox="media/common/roles-and-administrators.png":::
-1. Select the group. Only the groups that can be assigned to Azure AD roles are displayed.
+1. Select the role name to open the role. Don't add a check mark next to the role.
- [![Only groups that are assignable are shown for a new role assignment.](./media/groups-assign-role/eligible-groups.png "Only groups that are assignable are shown for a new role assignment.")](./media/groups-assign-role/eligible-groups.png#lightbox)
+ :::image type="content" source="media/common/role-select-mouse.png" alt-text="Screenshot that shows selecting a role." lightbox="media/common/role-select-mouse.png":::
-1. Select **Add**.
+1. Select **Add assignments**.
-For more information on assigning role permissions, see [Assign administrator and non-administrator roles to users](../fundamentals/active-directory-users-assign-role-azure-portal.md).
+ If you see something different from the following screenshot, you might have Azure AD Premium P2. For more information, see [Assign Azure AD roles in Privileged Identity Management](../privileged-identity-management/pim-how-to-add-role-to-user.md).
+
+ :::image type="content" source="media/groups-assign-role/add-assignments.png" alt-text="Screenshot of Add assignments pane to assign role to users or groups." lightbox="media/groups-assign-role/add-assignments.png":::
+
+1. Select the group you want to assign to this role. Only role-assignable groups are displayed.
+
+ If group isn't listed, you will need to create a role-assignable group. For more information, see [Create a role-assignable group in Azure Active Directory](groups-create-eligible.md).
+
+1. Select **Add** to assign the role to the group.
## PowerShell
-### Create a group that can be assigned to role
+# [Microsoft Graph PowerShell](#tab/ms-powershell)
+
+### Create a role-assignable group
+
+Use the [New-MgGroup](/powershell/module/microsoft.graph.groups/new-mggroup?branch=main) command to create a role-assignable group.
+
+```powershell
+Connect-MgGraph -Scopes "Group.ReadWrite.All","RoleManagement.ReadWrite.Directory"
+$group = New-MgGroup -DisplayName "Contoso_Helpdesk_Administrators" -Description "This group has Helpdesk Administrator built-in role assigned to it in Azure AD." -MailEnabled:$false -SecurityEnabled -MailNickName "contosohelpdeskadministrators" -IsAssignableToRole:$true
+```
+
+### Get the role definition you want to assign
+
+Use the [Get-MgRoleManagementDirectoryRoleDefinition](/powershell/module/microsoft.graph.devicemanagement.enrolment/get-mgrolemanagementdirectoryroledefinition?branch=main) command to get a role definition.
+
+```powershell
+$roleDefinition = Get-MgRoleManagementDirectoryRoleDefinition -Filter "displayName eq 'Helpdesk Administrator'"
+```
+
+### Create a role assignment
+
+Use the [New-MgRoleManagementDirectoryRoleAssignment](/powershell/module/microsoft.graph.devicemanagement.enrolment/new-mgrolemanagementdirectoryroleassignment?branch=main) command to assign the role.
+
+```powershell
+$roleAssignment = New-MgRoleManagementDirectoryRoleAssignment -DirectoryScopeId '/' -RoleDefinitionId $roleDefinition.Id -PrincipalId $group.Id
+```
+
+# [Azure AD PowerShell](#tab/aad-powershell)
+
+### Create a role-assignable group
+
+Use the [New-AzureADMSGroup](/powershell/module/azuread/new-azureadmsgroup?branch=main) command to create a role-assignable group.
```powershell $group = New-AzureADMSGroup -DisplayName "Contoso_Helpdesk_Administrators" -Description "This group is assigned to Helpdesk Administrator built-in role in Azure AD." -MailEnabled $false -SecurityEnabled $true -MailNickName "contosohelpdeskadministrators" -IsAssignableToRole $true ```
-### Get the role definition for the role you want to assign
+### Get the role definition you want to assign
+
+Use the [Get-AzureADMSRoleDefinition](/powershell/module/azuread/get-azureadmsroledefinition?branch=main) command to get a role definition.
```powershell $roleDefinition = Get-AzureADMSRoleDefinition -Filter "displayName eq 'Helpdesk Administrator'"
$roleDefinition = Get-AzureADMSRoleDefinition -Filter "displayName eq 'Helpdesk
### Create a role assignment
+Use the [New-AzureADMSRoleAssignment](/powershell/module/azuread/new-azureadmsroleassignment?branch=main) command to assign the role.
+ ```powershell $roleAssignment = New-AzureADMSRoleAssignment -DirectoryScopeId '/' -RoleDefinitionId $roleDefinition.Id -PrincipalId $group.Id ``` ++ ## Microsoft Graph API
-### Create a group that can be assigned Azure AD role
+### Create a role-assignable group
-Use the [Create group](/graph/api/group-post-groups) API to create a group.
+Use the [Create group](/graph/api/group-post-groups?branch=main) API to create a role-assignable group.
+
+**Request**
```http POST https://graph.microsoft.com/v1.0/groups
POST https://graph.microsoft.com/v1.0/groups
} ```
-### Get the role definition
+**Response**
+
+```http
+HTTP/1.1 201 Created
+```
+
+### Get the role definition you want to assign
+
+Use the [List unifiedRoleDefinitions](/graph/api/rbacapplication-list-roledefinitions?branch=main) API to get a role definition.
-Use the [List unifiedRoleDefinitions](/graph/api/rbacapplication-list-roledefinitions) API to get a role definition.
+**Request**
```http GET https://graph.microsoft.com/v1.0/roleManagement/directory/roleDefinitions?$filter = displayName eq 'Helpdesk Administrator' ```
+**Response**
+
+```json
+{
+ "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#roleManagement/directory/roleDefinitions",
+ "value": [
+ {
+ "id": "729827e3-9c14-49f7-bb1b-9608f156bbb8",
+ "description": "Can reset passwords for non-administrators and Helpdesk Administrators.",
+ "displayName": "Helpdesk Administrator",
+ "isBuiltIn": true,
+ "isEnabled": true,
+ "resourceScopes": [
+ "/"
+ ],
+
+ ...
+
+```
+ ### Create the role assignment
-Use the [Create unifiedRoleAssignment](/graph/api/rbacapplication-post-roleassignments) API to assign the role.
+Use the [Create unifiedRoleAssignment](/graph/api/rbacapplication-post-roleassignments?branch=main) API to assign the role.
+
+**Request**
```http POST https://graph.microsoft.com/v1.0/roleManagement/directory/roleAssignments { "@odata.type": "#microsoft.graph.unifiedRoleAssignment",
- "principalId": "<Object Id of Group>",
+ "principalId": "<Object ID of Group>",
+ "roleDefinitionId": "<ID of role definition>",
+ "directoryScopeId": "/"
+}
+```
+
+**Response**
+
+```json
+HTTP/1.1 201 Created
+Content-type: application/json
+{
+ "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#roleManagement/directory/roleAssignments/$entity",
+ "id": "<Role assignment ID>",
"roleDefinitionId": "<ID of role definition>",
+ "principalId": "<Object ID of Group>",
"directoryScopeId": "/" }+ ```+ ## Next steps - [Use Azure AD groups to manage role assignments](groups-concept.md)
active-directory Groups Concept https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/roles/groups-concept.md
Previously updated : 01/11/2023 Last updated : 04/10/2023
# Use Azure AD groups to manage role assignments
-Azure Active Directory (Azure AD) lets you target Azure AD groups for role assignments. Assigning roles to groups can simplify the management of role assignments in Azure AD with minimal effort from your Global Administrators and Privileged Role Administrators.
+With Azure AD Premium P1 or P2, you can create role-assignable groups and assign Azure AD roles to these groups. This feature simplifies role management, ensures consistent access, and makes auditing permissions more straightforward. Assigning roles to a group instead of individuals allows for easy addition or removal of users from a role and creates consistent permissions for all members of the group. You can also create custom roles with specific permissions and assign them to groups.
## Why assign roles to groups?
The following scenarios aren't supported:
The following are known issues with role-assignable groups: - *Azure AD P2 licensed customers only*: Even after deleting the group, it is still shown an eligible member of the role in PIM UI. Functionally there's no problem; it's just a cache issue in the Azure portal. -- Use the new [Exchange admin center](/exchange/exchange-admin-center) for role assignments via group membership. The old Exchange admin center doesn't support this feature. If accessing the old Exchange admin center is required, assign the eligible role directly to the user (not via role-assignable groups). Exchange PowerShell cmdlets will work as expected.
+- Use the new [Exchange admin center](/exchange/exchange-admin-center) for role assignments via group membership. The old Exchange admin center doesn't support this feature. If accessing the old Exchange admin center is required, assign the eligible role directly to the user (not via role-assignable groups). Exchange PowerShell cmdlets work as expected.
- If an administrator role is assigned to a role-assignable group instead of individual users, members of the group will not be able to access Rules, Organization, or Public Folders in the new [Exchange admin center](/exchange/exchange-admin-center). The workaround is to assign the role directly to users instead of the group.-- Azure Information Protection Portal (the classic portal) doesn't recognize role membership via group yet. You can [migrate to the unified sensitivity labeling platform](/azure/information-protection/configure-policy-migrate-labels) and then use the Microsoft Purview compliance center to use group assignments to manage roles.
+- Azure Information Protection Portal (the classic portal) doesn't recognize role membership via group yet. You can [migrate to the unified sensitivity labeling platform](/azure/information-protection/configure-policy-migrate-labels) and then use the Microsoft Purview compliance portal to use group assignments to manage roles.
## License requirements
active-directory Groups Create Eligible https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/roles/groups-create-eligible.md
Title: Create a group for assigning roles in Azure Active Directory
-description: Learn how to create a role-assignable group in Azure AD. Manage Azure roles in the Azure portal, PowerShell, or Graph API.
+ Title: Create a role-assignable group in Azure Active Directory
+description: Learn how to a role-assignable group in Azure Active Directory using the Azure portal, PowerShell, or Microsoft Graph API.
Previously updated : 07/30/2021 Last updated : 04/10/2023
# Create a role-assignable group in Azure Active Directory
-You can only assign a role to a group that was created with the ΓÇÿisAssignableToRoleΓÇÖ property set to True, or was created in the Azure portal with **Azure AD roles can be assigned to the group** turned on. This group attribute makes the group one that can be assigned to a role in Azure Active Directory (Azure AD). This article describes how to create this special kind of group. **Note:** A group with isAssignableToRole property set to true cannot be of dynamic membership type. For more information, see [Use Azure AD groups to manage role assignments](groups-concept.md).
+With Azure AD Premium P1 or P2, you can create [role-assignable groups](groups-concept.md) and assign Azure AD roles to these groups. You create a new role-assignable group by setting **Azure AD roles can be assigned to the group** to **Yes** or by setting the `isAssignableToRole` property set to `true`. A role-assignable group can't be of dynamic membership type and you can create a maximum of 500 groups in a single tenant.
+
+This article describes how to create a role-assignable group using the Azure portal, PowerShell, or Microsoft Graph API.
## Prerequisites - Azure AD Premium P1 or P2 license-- Privileged Role Administrator or Global Administrator-- AzureAD module when using PowerShell
+- [Privileged Role Administrator](./permissions-reference.md#privileged-role-administrator)
+- Microsoft.Graph module when using [Microsoft Graph PowerShell](/powershell/microsoftgraph/installation?branch=main)
+- AzureAD module when using [Azure AD PowerShell](/powershell/azure/active-directory/overview?branch=main)
- Admin consent when using Graph explorer for Microsoft Graph API For more information, see [Prerequisites to use PowerShell or Graph Explorer](prerequisites.md).
For more information, see [Prerequisites to use PowerShell or Graph Explorer](pr
1. Select **Azure Active Directory** > **Groups** > **All groups** > **New group**.
- [![Open Azure Active Directory and create a new group.](./media/groups-create-eligible/new-group.png "Open Azure Active Directory and create a new group.")](./media/groups-create-eligible/new-group.png#<lightbox>)
- 1. On the **New Group** tab, provide group type, name and description.
-1. Turn on **Azure AD roles can be assigned to the group**. This switch is visible to only Privileged Role Administrators and Global Administrators because these are only two roles that can set the switch.
+1. Set **Azure AD roles can be assigned to the group** to **Yes**.
- [![Make the new group eligible for role assignment](./media/groups-create-eligible/eligible-switch.png "Make the new group eligible for role assignment")](./media/groups-create-eligible/eligible-switch.png#<lightbox>)
+ This option is visible to only Privileged Role Administrators and Global Administrators because these are only two roles that can set this option.
+ :::image type="content" source="media/groups-create-eligible/eligible-switch.png" alt-text="Screenshot of option to make group a role-assignable group." lightbox="media/groups-create-eligible/eligible-switch.png":::
+
1. Select the members and owners for the group. You also have the option to assign roles to the group, but assigning a role isn't required here.
- [![Add members to the role-assignable group and assign roles.](./media/groups-create-eligible/specify-members.png "Add members to the role-assignable group and assign roles.")](./media/groups-create-eligible/specify-members.png#<lightbox>)
+1. Select **Create**.
+
+ You see the following message:
+
+ Creating a group to which Azure AD roles can be assigned is a setting that cannot be changed later. Are you sure you want to add this capability?
-1. After the members and owners are specified, select **Create**.
+ :::image type="content" source="media/groups-create-eligible/group-create-message.png" alt-text="Screenshot of confirm message when creating a role-assignable group." lightbox="media/groups-create-eligible/group-create-message.png":::
- [![The Create button is at the bottom of the page.](./media/groups-create-eligible/create-button.png "The Create button is at the bottom of the page.")](./media/groups-create-eligible/create-button.png#<lightbox>)
+1. Select **Yes**.
-The group is created with any roles you might have assigned to it.
+ The group is created with any roles you might have assigned to it.
## PowerShell
-### Create a group that can be assigned to role
+# [Microsoft Graph PowerShell](#tab/ms-powershell)
+
+Use the [New-MgGroup](/powershell/module/microsoft.graph.groups/new-mggroup?branch=main) command to create a role-assignable group.
+
+```powershell
+Connect-MgGraph -Scopes "Group.ReadWrite.All"
+$group = New-MgGroup -DisplayName "Contoso_Helpdesk_Administrators" -Description "This group has Helpdesk Administrator built-in role assigned to it in Azure AD." -MailEnabled:$false -SecurityEnabled -MailNickName "contosohelpdeskadministrators" -IsAssignableToRole:$true
+```
+
+# [Azure AD PowerShell](#tab/aad-powershell)
+
+Use the [New-AzureADMSGroup](/powershell/module/azuread/new-azureadmsgroup?branch=main) command to create a role-assignable group.
```powershell $group = New-AzureADMSGroup -DisplayName "Contoso_Helpdesk_Administrators" -Description "This group is assigned to Helpdesk Administrator built-in role in Azure AD." -MailEnabled $false -SecurityEnabled $true -MailNickName "contosohelpdeskadministrators" -IsAssignableToRole $true
Add-AzureADGroupMember -ObjectId $roleAssignablegroup.Id -RefObjectId $member.Ob
} ``` ++ ## Microsoft Graph API
-### Create a role-assignable group in Azure AD
+Use the [Create group](/graph/api/group-post-groups?branch=main) API to create a role-assignable group.
```http POST https://graph.microsoft.com/v1.0/groups
active-directory Groups Pim Eligible https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/roles/groups-pim-eligible.md
- Title: Assign a role to a group using Privileged Identity Management in Azure AD
-description: Learn how you can assign an Azure Active Directory (Azure AD) role to a group using Azure AD Privileged Identity Management (PIM).
------- Previously updated : 05/14/2021-----
-# Make a group an eligible member of an Azure AD role via Privileged Identity Management
--
-# Assign a role to a group using Privileged Identity Management
-
-This article describes how you can assign an Azure Active Directory (Azure AD) role to a group using Azure AD Privileged Identity Management (PIM).
-
-> [!NOTE]
-> You must be using the updated version of Privileged Identity Management to be able to assign a group to an Azure AD role using PIM. You might be on older version of PIM if your Azure AD organization leverages the Privileged Identity Management API. If so, please reach out to the alias pim_preview@microsoft.com to move your organization and update your API. Learn more at [Azure AD roles and features in PIM](../privileged-identity-management/pim-configure.md).
-
-## Prerequisites
--- Azure AD Premium P2 license-- Privileged Role Administrator or Global Administrator-- AzureADPreview module when using PowerShell-- Admin consent when using Graph explorer for Microsoft Graph API-
-For more information, see [Prerequisites to use PowerShell or Graph Explorer](prerequisites.md).
-
-## Azure portal
-
-1. Sign in to [Azure AD Privileged Identity Management](https://portal.azure.com/?Microsoft_AAD_IAM_GroupRoles=true&Microsoft_AAD_IAM_userRolesV2=true&Microsoft_AAD_IAM_enablePimIntegration=true#blade/Microsoft_Azure_PIMCommon/CommonMenuBlade/quickStart).
-
-1. Select **Privileged Identity Management** > **Azure AD roles** > **Roles** > **Add assignments**
-
-1. Select a role, and then select a group. Only groups that are eligible for role assignment (role-assignable groups) are displayed, not all groups.
-
- ![Screenshot that shows the "Add assignments" page with the "Select role" and "Select member(s)" sections highlighted.](./media/groups-pim-eligible/select-member.png)
-
-1. Select the desired membership setting. For roles requiring activation, choose **eligible**. By default, the user would be permanently eligible, but you could also set a start and end time for the user's eligibility. Once you are complete, hit Save and Add to complete the role assignment.
-
- ![select the user to whom you're assigning the role](./media/groups-pim-eligible/set-assignment-settings.png)
-
-## PowerShell
-
-### Assign a group as an eligible member of a role
-
-```powershell
-$schedule = New-Object Microsoft.Open.MSGraph.Model.AzureADMSPrivilegedSchedule
-$schedule.Type = "Once"
-$schedule.StartDateTime = "2019-04-26T20:49:11.770Z"
-$schedule.endDateTime = "2019-07-25T20:49:11.770Z"
-Open-AzureADMSPrivilegedRoleAssignmentRequest -ProviderId aadRoles -Schedule $schedule -ResourceId "[YOUR TENANT ID]" -RoleDefinitionId "9f8c1837-f885-4dfd-9a75-990f9222b21d" -SubjectId "[YOUR GROUP ID]" -AssignmentState "Eligible" -Type "AdminAdd"
-```
-
-## Microsoft Graph API
-
-```http
-POST
-https://graph.microsoft.com/beta/privilegedAccess/aadroles/roleAssignmentRequests
-{
- "roleDefinitionId": {roleDefinitionId},
- "resourceId": {tenantId},
- "subjectId": {GroupId},
- "assignmentState": "Eligible",
- "type": "AdminAdd",
- "reason": "reason string",
- "schedule": {
- "startDateTime": {DateTime},
- "endDateTime": {DateTime},
- "type": "Once"
- }
-}
-```
-
-## Next steps
--- [Use Azure AD groups to manage role assignments](groups-concept.md)-- [Troubleshoot Azure AD roles assigned to groups](groups-faq-troubleshooting.yml)-- [Configure Azure AD admin role settings in Privileged Identity Management](../privileged-identity-management/pim-how-to-change-default-settings.md)-- [Assign Azure resource roles in Privileged Identity Management](../privileged-identity-management/pim-resource-roles-assign-roles.md)
active-directory Manage Roles Portal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/roles/manage-roles-portal.md
Follow these steps to assign Azure AD roles using the Azure portal. Your experie
1. Select **Azure Active Directory** > **Roles and administrators** to see the list of all available roles.
- ![Roles and administrators page in Azure Active Directory.](./media/manage-roles-portal/roles-and-administrators.png)
+ ![Screenshot of Roles and administrators page in Azure Active Directory.](./media/common/roles-and-administrators.png)
1. Find the role you need. You can use the search box or **Add filters** to filter the roles. 1. Select the role name to open the role. Don't add a check mark next to the role.
- ![Screenshot that shows selecting a role.](./media/manage-roles-portal/role-select-mouse.png)
+ ![Screenshot that shows selecting a role.](./media/common/role-select-mouse.png)
1. Select **Add assignments** and then select the users you want to assign to this role. If you see something different from the following picture, you might have PIM enabled. See the next section.
- ![Add assignments pane for selected role.](./media/manage-roles-portal/add-assignments.png)
+ ![Screenshot of Add assignments pane for selected role.](./media/manage-roles-portal/add-assignments.png)
1. Select **Add** to assign the role.
Follow these steps to assign roles using the [Roles and administrators](https://
1. Select **Azure Active Directory** > **Roles and administrators** to see the list of all available roles.
- ![Roles and administrators page in Azure Active Directory when PIM enabled.](./media/manage-roles-portal/roles-and-administrators.png)
+ ![Screenshot of Roles and administrators page in Azure Active Directory when PIM enabled.](./media/common/roles-and-administrators.png)
1. Find the role you need. You can use the search box or **Add filters** to filter the roles. 1. Select the role name to open the role and see its eligible, active, and expired role assignments. Don't add a check mark next to the role.
- ![Screenshot that shows selecting a role.](./media/manage-roles-portal/role-select-mouse.png)
+ ![Screenshot that shows selecting a role.](./media/common/role-select-mouse.png)
1. Select **Add assignments**. 1. Select **No member selected** and then select the users you want to assign to this role.
- ![Add assignments page and Select a member pane with PIM enabled.](./media/manage-roles-portal/add-assignments-pim.png)
+ ![Screenshot of Add assignments page and Select a member pane with PIM enabled.](./media/manage-roles-portal/add-assignments-pim.png)
1. Select **Next**.
Follow these steps to assign roles using the [Roles and administrators](https://
An eligible role assignment means that the user must perform one or more actions to use the role. An active role assignment means that the user doesn't have to perform any action to use the role. For more information about what these settings mean, see [PIM terminology](../privileged-identity-management/pim-configure.md#terminology).
- ![Add assignments page and Setting tab with PIM enabled.](./media/manage-roles-portal/add-assignments-pim-setting.png)
+ ![Screenshot of Add assignments page and Setting tab with PIM enabled.](./media/manage-roles-portal/add-assignments-pim-setting.png)
1. Use the remaining options to set the duration for the assignment.
active-directory Terraform Cloud Tutorial https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/terraform-cloud-tutorial.md
+ Last updated 11/21/2022 - # Tutorial: Azure Active Directory single sign-on (SSO) integration with Terraform Cloud
active-directory Workload Identity Federation Considerations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/workload-identities/workload-identity-federation-considerations.md
Previously updated : 03/27/2023 Last updated : 04/07/2023
The creation of federated identity credentials is available on user-assigned man
- Sweden Central - East Asia - Qatar Central
+- Brazil Southeast
+- Malaysia South
+- Poland Central
+- UK North
+- UK South2
+ Support for creating federated identity credentials in these regions will be rolled out gradually except East Asia where support won't be provided.
advisor Advisor Alerts Arm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/advisor/advisor-alerts-arm.md
Title: Create Azure Advisor alerts for new recommendations using Resource Manager template description: Learn how to set up an alert for new recommendations from Azure Advisor using an Azure Resource Manager template (ARM template). -+ Last updated 06/29/2020
advisor Advisor Alerts Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/advisor/advisor-alerts-bicep.md
description: Learn how to set up an alert for new recommendations from Azure Adv
-+ Last updated 04/26/2022
advisor Advisor Performance Recommendations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/advisor/advisor-performance-recommendations.md
Title: Improve performance of Azure apps with Advisor description: Use performance recommendations in Azure Advisor to improve the speed and responsiveness of your business-critical applications. + Last updated 07/29/2020
aks Azure Cni Overlay https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/azure-cni-overlay.md
-+ Last updated 03/21/2023
Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address spa
## IP address planning -- **Cluster Nodes**: Cluster nodes go into a subnet in your VNet, so verify you have a subnet large enough to account for future scale. A simple `/24` subnet can host up to 251 nodes (the first three IP addresses in a subnet are reserved for management operations).
+- **Cluster Nodes**: Cluster nodes go into a subnet in your VNet, so verify you have a subnet large enough to account for future scale. Cluster can't scale to another subnet but you can add new nodepools in another subnet within the same VNet for expansion. A simple `/24` subnet can host up to 251 nodes (the first three IP addresses in a subnet are reserved for management operations).
- **Pods**: The overlay solution assigns a `/24` address space for pods on every node from the private CIDR that you specify during cluster creation. The `/24` size is fixed and can't be increased or decreased. You can run up to 250 pods on a node. When planning the pod address space, ensure that the private CIDR is large enough to provide `/24` address spaces for new nodes to support future cluster expansion.
aks Free Standard Pricing Tiers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/free-standard-pricing-tiers.md
Title: Azure Kubernetes Service (AKS) Free and Standard pricing tiers for cluster management description: Learn about the Azure Kubernetes Service (AKS) Free and Standard pricing tiers for cluster management Previously updated : 02/17/2023 Last updated : 04/07/2023 # Free and Standard pricing tiers for Azure Kubernetes Service (AKS) cluster management
-Azure Kubernetes Service (AKS) is now offering two pricing tiers for cluster management: the **Free tier** and the **Standard tier**.
-
-> [!IMPORTANT]
->
-> **Standard tier** is currently not available in Azure API 2023-01-01 due to a [critical bug](https://github.com/Azure/AKS/issues/3481). To enable the Uptime SLA feature in your cluster, you'll use the existing **Paid tier** and the `--uptime-sla` parameter.
->
-> Alternatively, you can select the **Standard tier** or **Free tier** on Azure portal when creating or updating an AKS cluster.
+Azure Kubernetes Service (AKS) is now offering two pricing tiers for cluster management: the **Free tier** and the **Standard tier**. Both tiers are in the **Base** sku.
| |Free tier|Standard tier| |||--|
Azure Kubernetes Service (AKS) is now offering two pricing tiers for cluster man
|**Pricing**|ΓÇó Free cluster management <br> ΓÇó Pay-as-you-go for resources you consume|ΓÇó Pay-as-you-go for resources you consume| |**Feature comparison**|ΓÇó Recommended for clusters with fewer than 10 nodes, but can support up to 1,000 nodes <br> ΓÇó Includes all current AKS features|ΓÇó Uptime SLA is enabled by default <br> ΓÇó Greater cluster reliability and resources <br> ΓÇó Can support up to 5,000 nodes in a cluster <br> ΓÇó Includes all current AKS features
+> [!IMPORTANT]
+>
+> Uptime SLA has been repositioned as a default feature included with the Standard tier.
+>
+> The repositioning will result in the following API changes:
+>
+> | |Prior to 2023-02-01 API|Starting from 2023-02-01 API|
+> |-|--||
+> |ManagedClusterSKUName|"Basic"|"Base"|
+> |ManagedClusterSKUTier|"Free" <br> "Paid"|"Free" <br> "Standard"|
+>
+> "Basic" and "Paid" are removed in the 2023-02-01 and 2023-02-02 Preview API version, and this will be a breaking change in API versions 2023-02-01 and 2023-02-02 Preview or newer. If you use automated scripts, CD pipelines, ARM templates, Terraform, or other third-party tooling that relies on the above parameters, please be sure to update the API parameters to use "Base" with "Free" or "Base" with "Standard" before upgrading to the 2023-02-01 and 2023-02-02 Preview API or newer API versions.
+ For more information on pricing, see the [AKS pricing details](https://azure.microsoft.com/pricing/details/kubernetes-service/). ## Uptime SLA terms and conditions
-The Uptime SLA feature is included in the Paid tier and is enabled per cluster. For more information on pricing, see the [AKS pricing details](https://azure.microsoft.com/pricing/details/kubernetes-service/).
+In the Standard tier, the Uptime SLA feature is enabled by default per cluster. For more information, see [SLA for AKS](https://azure.microsoft.com/support/legal/sla/kubernetes-service/v1_1/).
## Region availability
-* Uptime SLA is available in public regions and Azure Government regions where [AKS is supported](https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service).
-* Uptime SLA is available for [private AKS clusters][private-clusters] in all public regions where AKS is supported.
+* Free tier and Standard tier are available in public regions and Azure Government regions where [AKS is supported](https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service).
+* Free tier and Standard tier are available for [private AKS clusters][private-clusters] in all public regions where AKS is supported.
## Before you begin
-[Azure CLI](/cli/azure/install-azure-cli) version 2.8.0 or later and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
+[Azure CLI](/cli/azure/install-azure-cli) version 2.47.0 or later and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
## Create a new cluster in the Free tier or Paid tier
-> [!IMPORTANT]
-> `--tier standard` and `--tier free` are currently unavailable in Azure CLI 2.46.0 due to a [critical bug](https://github.com/Azure/AKS/issues/3481). To enable the Uptime SLA feature, use the commands below.
- Use the Azure CLI to create a new cluster on an AKS pricing tier. You can create your cluster in an existing resource group or create a new one. To learn more about resource groups and working with them, see [managing resource groups using the Azure CLI][manage-resource-group-cli]. Use the [`az aks create`][az-aks-create] command to create an AKS cluster. The commands below show you how to create a new resource group named *myResourceGroup* and a cluster named *myAKSCluster* in that resource group in each tier.
Use the [`az aks create`][az-aks-create] command to create an AKS cluster. The c
```azurecli-interactive # Create a new AKS cluster in the Free tier
-az aks create --resource-group myResourceGroup --name myAKSCluster --no-uptime-sla
+az aks create --resource-group myResourceGroup --name myAKSCluster --tier free
-# Create a new AKS cluster in the Paid tier
+# Create a new AKS cluster in the Standard tier
-az aks create --resource-group myResourceGroup --name myAKSCluster --uptime-sla
+az aks create --resource-group myResourceGroup --name myAKSCluster --tier standard
``` Once the deployment completes, it returns JSON-formatted information about your cluster: ```output
-# Sample output for --no-uptime-sla
+# Sample output for --tier free
}, "sku": {
- "name": "Basic",
+ "name": "Base",
"tier": "Free" },
-# Sample output for --uptime-sla
+# Sample output for --tier standard
}, "sku": { "name": "Base",
- "tier": "Paid"
+ "tier": "Standard"
}, ```
-## Update the tier of an existing cluster
+## Update the tier of an existing AKS cluster
The following example uses the [`az aks update`][az-aks-update] command to update the existing cluster. ```azurecli-interactive # Update an existing cluster to the Free tier
-az aks update --resource-group myResourceGroup --name myAKSCluster --no-uptime-sla
+az aks update --resource-group myResourceGroup --name myAKSCluster --tier free
# Update an existing cluster to the Standard tier
-az aks update --resource-group myResourceGroup --name myAKSCluster --uptime-sla
+az aks update --resource-group myResourceGroup --name myAKSCluster --tier standard
```
-This process takes several minutes to complete. When finished, the following example JSON snippet shows the Paid tier for the SKU, indicating your cluster is enabled with Uptime SLA.
+This process takes several minutes to complete. When finished, the following example JSON snippet shows updating the existing cluster to the Standard tier in the Base SKU.
```output }, "sku": { "name": "Base",
- "tier": "Paid"
+ "tier": "Standard"
}, ```
aks Http Proxy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/http-proxy.md
Title: Configuring Azure Kubernetes Service (AKS) nodes with an HTTP proxy description: Use the HTTP proxy configuration feature for Azure Kubernetes Service (AKS) nodes. + Last updated 02/01/2023
aks Keda Deploy Add On Arm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/keda-deploy-add-on-arm.md
Title: Install the Kubernetes Event-driven Autoscaling (KEDA) add-on by using an
description: Use an ARM template to deploy the Kubernetes Event-driven Autoscaling (KEDA) add-on to Azure Kubernetes Service (AKS). -+ Last updated 10/10/2022
aks Quick Kubernetes Deploy Bicep Extensibility Kubernetes Provider https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md
Title: Quickstart - Deploy Azure applications to Azure Kubernetes Service clusters using Bicep extensibility Kubernetes provider description: Learn how to quickly create a Kubernetes cluster and deploy Azure applications in Azure Kubernetes Service (AKS) using Bicep extensibility Kubernetes provider. + Last updated 02/21/2023 #Customer intent: As a developer or cluster operator, I want to quickly create an AKS cluster and deploy an application so that I can see how to run applications using the managed Kubernetes service in Azure.
aks Quick Kubernetes Deploy Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/learn/quick-kubernetes-deploy-bicep.md
Title: Quickstart - Create an Azure Kubernetes Service (AKS) cluster by using Bi
description: Learn how to quickly create a Kubernetes cluster using a Bicep file and deploy an application in Azure Kubernetes Service (AKS) Last updated 11/01/2022-+ #Customer intent: As a developer or cluster operator, I want to quickly create an AKS cluster and deploy an application so that I can see how to run applications using the managed Kubernetes service in Azure.
aks Quick Kubernetes Deploy Rm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/learn/quick-kubernetes-deploy-rm-template.md
Title: Quickstart - Create an Azure Kubernetes Service (AKS) cluster
description: Learn how to quickly create a Kubernetes cluster using an Azure Resource Manager template and deploy an application in Azure Kubernetes Service (AKS) Last updated 11/01/2022-+ #Customer intent: As a developer or cluster operator, I want to quickly create an AKS cluster and deploy an application so that I can see how to run applications using the managed Kubernetes service in Azure.
aks Node Upgrade Github Actions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/node-upgrade-github-actions.md
Title: Handle AKS node upgrades with GitHub Actions
description: Learn how to update AKS nodes using GitHub Actions + Last updated 11/27/2020-- #Customer intent: As a cluster administrator, I want to know how to automatically apply Linux updates and reboot nodes in AKS for security and/or compliance
aks Open Service Mesh Deploy Addon Az Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/open-service-mesh-deploy-addon-az-cli.md
Title: Install the Open Service Mesh add-on by using the Azure CLI description: Use Azure CLI commands to install the Open Service Mesh (OSM) add-on on an Azure Kubernetes Service (AKS) cluster. + Last updated 11/10/2021
aks Open Service Mesh Deploy Addon Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/open-service-mesh-deploy-addon-bicep.md
Title: Deploy the Open Service Mesh add-on by using Bicep description: Use a Bicep template to deploy the Open Service Mesh (OSM) add-on to Azure Kubernetes Service (AKS). + Last updated 9/20/2021
aks Open Service Mesh Uninstall Add On https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/open-service-mesh-uninstall-add-on.md
Title: Uninstall the Open Service Mesh (OSM) add-on description: Deploy Open Service Mesh on Azure Kubernetes Service (AKS) using Azure CLI + Last updated 11/10/2021
osm uninstall cluster-wide-resources
> [!IMPORTANT] > You must remove these additional resources after you disable the OSM add-on. Leaving these resources on your cluster may cause issues if you enable the OSM add-on again in the future.-
aks Trusted Access Feature https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/trusted-access-feature.md
Title: Enable Azure resources to access Azure Kubernetes Service (AKS) clusters
description: Learn how to use the Trusted Access feature to enable Azure resources to access Azure Kubernetes Service (AKS) clusters. + Last updated 03/20/2023
aks Use Pod Sandboxing https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/use-pod-sandboxing.md
Title: Pod Sandboxing (preview) with Azure Kubernetes Service (AKS) description: Learn about and deploy Pod Sandboxing (preview), also referred to as Kernel Isolation, on an Azure Kubernetes Service (AKS) cluster. + Last updated 03/07/2023- # Pod Sandboxing (preview) with Azure Kubernetes Service (AKS)
aks Use Pod Security Policies https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/use-pod-security-policies.md
Title: Use pod security policies in Azure Kubernetes Service (AKS) description: Learn how to control pod admissions by using PodSecurityPolicy in Azure Kubernetes Service (AKS) + Last updated 03/25/2021
analysis-services Analysis Services Create Bicep File https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/analysis-services/analysis-services-create-bicep-file.md
tags: azure-resource-manager, bicep-+ #Customer intent: As a BI developer who is new to Azure, I want to use Azure Analysis Services to store and manage my organizations data models.
analysis-services Analysis Services Create Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/analysis-services/analysis-services-create-template.md
Last updated 01/26/2023
tags: azure-resource-manager-+ #Customer intent: As a BI developer who is new to Azure, I want to use Azure Analysis Services to store and manage my organizations data models.
api-management Developer Portal Faq https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/developer-portal-faq.md
Last updated 02/04/2022 -+ # API Management developer portal - frequently asked questions
api-management Graphql Api https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/graphql-api.md
Last updated 10/27/2022-+ # Import a GraphQL API
api-management How To Deploy Self Hosted Gateway Azure Arc https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/how-to-deploy-self-hosted-gateway-azure-arc.md
description: Enable Azure Arc to deploy your self-hosted Azure API Management ga
+ Last updated 05/25/2021
api-management Import Api From Oas https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/import-api-from-oas.md
Last updated 10/26/2022 --+ # Import an OpenAPI specification
api-management Import Soap Api https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/import-soap-api.md
Title: Import SOAP API to Azure API Management | Microsoft Docs
description: Learn how to import a SOAP API to Azure API Management as a WSDL specification using the Azure portal, Azure CLI, or Azure PowerShell. Then, test the API in the Azure portal. + Last updated 10/26/2022 - # Import SOAP API to API Management
To define a wildcard SOAP action:
## Next steps > [!div class="nextstepaction"]
-> [Transform and protect a published API](transform-api.md)
+> [Transform and protect a published API](transform-api.md)
api-management Powershell Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/powershell-samples.md
na
Last updated 10/09/2017 -+ # Azure PowerShell samples for API Management
api-management Quickstart Arm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/quickstart-arm-template.md
tags: azure-resource-manager -+ Last updated 10/09/2020
api-management Quickstart Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/api-management/quickstart-bicep.md
tags: azure-resource-manager, bicep+ Last updated 03/10/2022
app-service Deploy Complex Application Predictably https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/deploy-complex-application-predictably.md
description: Learn how to deploy multiple Azure App Service apps as a single uni
ms.assetid: bb51e565-e462-4c60-929a-2ff90121f41d Last updated 01/06/2016--+ # Provision and deploy microservices predictably in Azure This tutorial shows how to provision and deploy an application composed of [microservices](https://en.wikipedia.org/wiki/Microservices) in [Azure App Service](https://azure.microsoft.com/services/app-service/) as a single unit and in a predictable manner using JSON resource group templates and PowerShell scripting.
app-service Deploy Resource Manager Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/deploy-resource-manager-template.md
Last updated 01/03/2019 -+ # Guidance on deploying web apps by using Azure Resource Manager templates
app-service App Service App Service Environment Create Ilb Ase Resourcemanager https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/app-service-app-service-environment-create-ilb-ase-resourcemanager.md
ms.assetid: 091decb6-b0de-42a1-9f2f-c18d9b2e67df
Last updated 03/29/2022 --+ # How To Create an ILB ASEv1 Using Azure Resource Manager Templates
To get started with App Service Environments, see [Introduction to App Service E
[quickstartilbasecreate]: https://azure.microsoft.com/resources/templates/web-app-ase-ilb-create/ [examplebase64encoding]: https://powershellscripts.blogspot.com/2007/02/base64-encode-file.html [configuringDefaultSSLCertificate]: https://azure.microsoft.com/resources/templates/web-app-ase-ilb-configure-default-ssl/-
app-service App Service App Service Environment Custom Settings https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/app-service-app-service-environment-custom-settings.md
ms.assetid: 1d1d85f3-6cc6-4d57-ae1a-5b37c642d812
Last updated 11/03/2021 -+ # Custom configuration settings for App Service Environments
app-service Configure Network Settings https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/configure-network-settings.md
keywords: ASE, ASEv3, ftp, remote debug + Last updated 03/29/2022
app-service Create From Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/create-from-template.md
ms.assetid: 6eb7d43d-e820-4a47-818c-80ff7d3b6f8e
Last updated 03/27/2023 -+ # Create an ASE by using an Azure Resource Manager template
app-service Create Ilb Ase https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/create-ilb-ase.md
ms.assetid: 0f4c1fa4-e344-46e7-8d24-a25e247ae138
Last updated 03/27/2023 -+ # Create and use an Internal Load Balancer App Service Environment
app-service How To Create From Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/how-to-create-from-template.md
Title: Create an App Service Environment (ASE) v3 with Azure Resource Manager
description: Learn how to create an external or ILB App Service Environment v3 by using an Azure Resource Manager template. + Last updated 03/09/2023
app-service How To Custom Domain Suffix https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/how-to-custom-domain-suffix.md
Title: Configure custom domain suffix for App Service Environment
description: Configure a custom domain suffix for the Azure App Service Environment. + Last updated 02/09/2023 zone_pivot_groups: app-service-environment-portal-arm
app-service How To Upgrade Preference https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/how-to-upgrade-preference.md
Title: Configure upgrade preference for App Service Environment planned maintena
description: Configure the upgrade preference for the Azure App Service Environment planned maintenance. + Last updated 09/19/2022 zone_pivot_groups: app-service-cli-portal
az rest --method POST --uri "${ASE_ID}/upgrade?api-version=2022-03-01"
> [Using an App Service Environment v3](using.md) > [!div class="nextstepaction"]
-> [App Service Environment v3 Networking](networking.md)
+> [App Service Environment v3 Networking](networking.md)
app-service Migrate https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/environment/migrate.md
Title: Migrate to App Service Environment v3 by using the migration feature
description: Overview of the migration feature for migration to App Service Environment v3 Previously updated : 03/20/2023 Last updated : 04/07/2023
If your App Service Environment doesn't pass the validation checks or you try to
|`<ZoneRedundant><DedicatedHosts><ASEv3/ASE>` is not available in this location. |This error appears if you're trying to migrate an App Service Environment in a region that doesn't support one of your requested features. |Migrate using one of the [manual migration options](migration-alternatives.md) if you want to migrate immediately. Otherwise, wait for the migration feature to support this App Service Environment configuration. | |Migrate cannot be called on this ASE until the active upgrade has finished. |App Service Environments can't be migrated during platform upgrades. You can set your [upgrade preference](how-to-upgrade-preference.md) from the Azure portal. In some cases, an upgrade is initiated when visiting the migration page if your App Service Environment isn't on the current build. |Wait until the upgrade finishes and then migrate. | |App Service Environment management operation in progress. |Your App Service Environment is undergoing a management operation. These operations can include activities such as deployments or upgrades. Migration is blocked until these operations are complete. |You can migrate once these operations are complete. |
+|Migrate is not available for this subscription|Support needs to be engaged for migrating this App Service Environment.|Open a support case to engage support to resolve your issue.|
## Overview of the migration process using the migration feature
app-service Manage Scale Per App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/manage-scale-per-app.md
ms.assetid: a903cb78-4927-47b0-8427-56412c4e3e64
Last updated 05/13/2019 --+ # High-density hosting on Azure App Service using per-app scaling
Follow these steps to configure high-density hosting for your apps:
- [Azure App Service plans in-depth overview](overview-hosting-plans.md) - [Introduction to App Service Environment](environment/app-service-app-service-environment-intro.md)-- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
app-service App Gateway With Service Endpoints https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/networking/app-gateway-with-service-endpoints.md
na
Last updated 08/04/2021 -+ ms.devlang: azurecli- # Application Gateway integration
app-service Provision Resource Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/provision-resource-bicep.md
description: Create your first app to Azure App Service in seconds using Azure B
+ Last updated 11/18/2022
app-service Provision Resource Terraform https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/provision-resource-terraform.md
Last updated 10/20/2022 ms.tool: terraform-+ # Create App Service app using a Terraform template
app-service Quickstart Arm Template Uiex https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/quickstart-arm-template-uiex.md
ms.assetid: 582bb3c2-164b-42f5-b081-95bfcb7a502a Last updated 10/16/2020-+ zone_pivot_groups: app-service-platform-windows-linux
app-service Quickstart Arm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/quickstart-arm-template.md
ms.assetid: 582bb3c2-164b-42f5-b081-95bfcb7a502a Last updated 03/10/2022-+ zone_pivot_groups: app-service-platform-windows-linux adobe-target: true adobe-target-activity: DocsExpΓÇô386541ΓÇôA/BΓÇôEnhanced-Readability-QuickstartsΓÇô2.19.2021
app-service Samples Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/samples-bicep.md
tags: azure-service-management
Last updated 11/18/2022 -+ # Bicep files for App Service
app-service Samples Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/samples-powershell.md
tags: azure-service-management
ms.assetid: b48d1137-8c04-46e0-b430-101e07d7e470 Last updated 12/06/2022-+ # PowerShell samples for Azure App Service
app-service Samples Resource Manager Templates https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/samples-resource-manager-templates.md
tags: azure-service-management
Last updated 08/26/2020 -+ # Azure Resource Manager templates for App Service
app-service Samples Terraform https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/samples-terraform.md
Title: terraform samples description: Find terraform samples for some of the common App Service scenarios. Learn how to automate your App Service deployment or management tasks. tags: azure-service-management+ ms.assetid: 1e5ecfa8-4ab1-47d3-ab23-97abf723516d
The following table includes links to terraform scripts.
|**Create app**|| | [Create two apps and connect securely with Private Endpoint and VNet integration](./scripts/terraform-secure-backend-frontend.md )| Creates two App Service apps and connect apps together with Private Endpoint and VNet integration. | | [Provision App Service and use slot swap to deploy](/azure/developer/terraform/provision-infrastructure-using-azure-deployment-slots)| Provision App Service infrastructure with Azure deployment slots. |
-| | |
+| | |
app-service Template Deploy Private Endpoint https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/scripts/template-deploy-private-endpoint.md
Last updated 07/08/2020
+ # Create an App Service app and deploy a private endpoint by using an Azure Resource Manager template
app-service Terraform Secure Backend Frontend https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/scripts/terraform-secure-backend-frontend.md
Last updated 12/06/2022
+ # Create two web apps connected securely with Private Endpoint and VNet integration
resource "azurerm_private_endpoint" "privateendpoint" {
## Next steps
-> [Learn more about using Terraform in Azure](/azure/developer/terraform/)
+> [Learn more about using Terraform in Azure](/azure/developer/terraform/)
app-service Tutorial Multi Region App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/tutorial-multi-region-app.md
description: Learn how to build a multi-region app on Azure App Service that can
keywords: azure app service, web app, multiregion, multi-region, multiple regions + Last updated 2/8/2023
app-service Tutorial Secure Ntier App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/tutorial-secure-ntier-app.md
Title: 'Tutorial: Create a secure N-tier web app'
description: Learn how to securely deploy your N-tier web app to Azure App Service. + Last updated 2/25/2023
application-gateway Application Gateway Create Probe Classic Ps https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/application-gateway-create-probe-classic-ps.md
description: Learn how to create a custom probe for Application Gateway by using
+ Last updated 11/13/2019
Set-AzureApplicationGatewayConfig -Name "<application gateway name>" -Configfile
If you want to configure Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL) offload, see [Configure an application gateway for TLS offload](./tutorial-ssl-powershell.md).
-If you want to configure an application gateway to use with an internal load balancer, see [Create an application gateway with an internal load balancer (ILB)](./application-gateway-ilb-arm.md).
+If you want to configure an application gateway to use with an internal load balancer, see [Create an application gateway with an internal load balancer (ILB)](./application-gateway-ilb-arm.md).
application-gateway Application Gateway Create Probe Ps https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/application-gateway-create-probe-ps.md
Last updated 07/09/2020 --+ # Create a custom probe for Azure Application Gateway by using PowerShell for Azure Resource Manager
application-gateway Ingress Controller Install Existing https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/ingress-controller-install-existing.md
description: This article provides information on how to deploy an Application G
+ Last updated 11/4/2019
application-gateway Multiple Site Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/multiple-site-overview.md
Title: Hosting multiple sites on Azure Application Gateway
-description: This article provides an overview of the Azure Application Gateway multi-site support.
+description: This article provides an overview of the Azure Application Gateway multi-site support. Examples are provided of rule priority and the order of evaluation for rules applied to incoming requests. Conditions and limitations for using wildcard rules are described.
Previously updated : 10/03/2022 Last updated : 04/07/2023
You can also define wildcard host names in a multi-site listener and up to 5 hos
:::image type="content" source="./media/multiple-site-overview/multisite.png" alt-text="Multi-site Application Gateway"::: > [!IMPORTANT]
-> Rules are processed in the order they are listed in the portal for the v1 SKU. For v2 SKU use [rule priority](#request-routing-rules-evaluation-order) to specify the processing order. It is highly recommended to configure multi-site listeners first prior to configuring a basic listener. This will ensure that traffic gets routed to the right back end. If a basic listener is listed first and matches an incoming request, it gets processed by that listener.
+> Rules are processed in the order they are listed in the portal for the v1 SKU. For v2 SKU use [rule priority](#request-routing-rules-evaluation-order) to specify the processing order. It is highly recommended to configure multi-site listeners first prior to configuring a basic listener. This ensures that traffic gets routed to the right back end. If a basic listener is listed first and matches an incoming request, it gets processed by that listener.
Requests for `http://contoso.com` are routed to ContosoServerPool, and `http://fabrikam.com` are routed to FabrikamServerPool.
Similarly, you can host multiple subdomains of the same parent domain on the sam
## Request Routing rules evaluation order
-When you use multi-site listeners to ensure that the client traffic is routed to the accurate backend, it's important to have the request routing rules be present in the correct order.
-For example, if you have 2 listeners with associated Host name as `*.contoso.com` and `shop.contoso.com` respectively, the listener with the `shop.contoso.com` Host name would have to be processed before the listener with `*.contoso.com`. If the listener with `*.contoso.com` is processed first, then no client traffic would be received by the more specific `shop.contoso.com` listener.
+When you use multi-site listeners to ensure that the client traffic is routed to the accurate backend, it's important that the request routing rules are present in the correct order.
+For example, if you have 2 listeners with associated host names of `*.contoso.com` and `shop.contoso.com`, the listener with the `shop.contoso.com` host name must be processed before the listener with `*.contoso.com`. If the listener with `*.contoso.com` is processed first, then no client traffic is received by the more specific `shop.contoso.com` listener.
-This ordering can be established by providing a 'Priority' field value to the request routing rules associated with the listeners. You can specify an integer value from 1 to 20000 with 1 being the highest priority and 20000 being the lowest priority. In case the incoming client traffic matches with multiple listeners, the request routing rule with highest priority will be used for serving the request. Each request routing rule needs to have a unique priority value.
+The ordering of rules can be established by providing a **Priority** field value to the request routing rules associated with the listeners. You can specify an integer value from 1 to 20000 with 1 being the highest priority and 20000 being the lowest priority. If incoming client traffic matches with multiple listeners, the request routing rule with highest priority is used to serve the request. Each request routing rule must have a unique priority value.
The priority field only impacts the order of evaluation of a request routing rule, this wont change the order of evaluation of path based rules within a `PathBasedRouting` request routing rule.
->[!NOTE]
->If you wish to use rule priority, you will have to specify rule priority field values for all the existing request routing rules. Once the rule priority field is in use, any new routing rule that is created would also need to have a rule priority field value as part of its config.
-Starting with API version 2021-08-01 rule priority field would be a mandatory field as part of the request routing rules.
-From this API version, rule priority field values would be auto-populated for existing request routing rules based on current ordering of evaluation as part of the first PUT call. Any future updates to request routing rules would need to have the rule priority field provided as part of the configuration.
+> [!NOTE]
+> To use rule priority, you must specify rule priority field values for all the existing request routing rules. Once the rule priority field is in use, any new routing rule that is created must have a rule priority field value as part of its configuration.
> [!IMPORTANT]
-> Rule priority field values for existing request routing rules based on current order would be automatically populated if any configuration updates are applied using API version 2021-08-01 and above, portal, Azure PowerShell and Azure CLI. Any future updates to request routing rules would need to have the rule priority field provided as part of the configuration.
+> Starting with API version 2021-08-01, the rule priority field is a mandatory field in the request routing rules. Rule priority field values for existing request routing rules, based on current ordering of evaluation as part of the first PUT call, are automatically populated if any configuration updates are applied using API version 2021-08-01 and above, portal, Azure PowerShell and Azure CLI. Future updates to request routing rules must have the rule priority field provided as part of the configuration.
## Wildcard host names in listener Application Gateway allows host-based routing using multi-site HTTP(S) listener. Now, you can use wildcard characters like asterisk (*) and question mark (?) in the host name, and up to 5 host names per multi-site HTTP(S) listener. For example, `*.contoso.com`.
-Using a wildcard character in the host name, you can match multiple host names in a single listener. For example, `*.contoso.com` can match with `ecom.contoso.com`, `b2b.contoso.com` and `customer1.b2b.contoso.com` and so on. Using an array of host names, you can configure more than one host name for a listener, to route requests to a backend pool. For example, a listener can contain `contoso.com, fabrikam.com` which will accept requests for both the host names.
+Using a wildcard character in the host name, you can match multiple host names in a single listener. For example, `*.contoso.com` can match with `ecom.contoso.com`, `b2b.contoso.com` and `customer1.b2b.contoso.com` and so on. Using an array of host names, you can configure more than one host name for a listener, to route requests to a backend pool. For example, a listener can contain `contoso.com, fabrikam.com` which accepts requests for both the host names.
:::image type="content" source="./media/multiple-site-overview/wildcard-listener-diag.png" alt-text="Wildcard Listener":::
In the Azure portal, under the multi-site listener, you must choose the **Multip
* If it's a wildcard hostname like *.contoso.com, you must upload a wildcard certificate with CN like *.contoso.com * If multiple host names are mentioned in the same listener, you must upload a SAN certificate (Subject Alternative Names) with the CNs matching the host names mentioned. * You can't use a regular expression to mention the host name. You can only use wildcard characters like asterisk (*) and question mark (?) to form the host name pattern.
-* For backend health check, you can't associate multiple [custom probes](application-gateway-probe-overview.md) per HTTP settings. Instead, you can probe one of the websites at the backend or use "127.0.0.1" to probe the localhost of the backend server. However, when you're using wildcard or multiple host names in a listener, the requests for all the specified domain patterns will be routed to the backend pool depending on the rule type (basic or path-based).
+* For backend health check, you can't associate multiple [custom probes](application-gateway-probe-overview.md) per HTTP settings. Instead, you can probe one of the websites at the backend or use "127.0.0.1" to probe the localhost of the backend server. However, when you're using wildcard or multiple host names in a listener, the requests for all the specified domain patterns are routed to the backend pool depending on the rule type (basic or path-based).
* The "hostname" property takes one string as input, where you can mention only one non-wildcard domain name. The "hostnames" property takes an array of strings as input, where you can mention up to 5 wildcard domain names. Both these properties can't be used at once. See [create multi-site using Azure PowerShell](tutorial-multiple-sites-powershell.md) or [using Azure CLI](tutorial-multiple-sites-cli.md) for the step-by-step guide on how to configure wildcard host names in a multi-site listener.
There are three common mechanisms for enabling multiple site hosting on the same
Currently Application Gateway supports a single public IP address where it listens for traffic. So multiple applications, each with its own IP address is currently not supported.
-Application Gateway supports multiple applications each listening on different ports, but this scenario requires the applications to accept traffic on non-standard ports.
+Application Gateway supports multiple applications each listening on different ports, but this scenario requires the applications to accept traffic on nonstandard ports.
Application Gateway relies on HTTP 1.1 host headers to host more than one website on the same public IP address and port. The sites hosted on application gateway can also support TLS offload with Server Name Indication (SNI) TLS extension. This scenario means that the client browser and backend web farm must support HTTP/1.1 and TLS extension as defined in RFC 6066.
application-gateway Powershell Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/powershell-samples.md
description: This article has links to Azure PowerShell examples so you can quic
+ Last updated 11/16/2019 - # Azure PowerShell examples for Azure Application Gateway (AG)
The following table includes links to Azure PowerShell script examples for Azure
|-- | -- | | [Manage web traffic](./scripts/create-vmss-powershell.md) | Creates an Application Gateway and all related resources.| | [Restrict web traffic](./scripts/create-vmss-waf-powershell.md) | Creates an Application Gateway that restricts traffic using OWASP rules.|
-|[WAF v2 custom rules](scripts/waf-custom-rules-powershell.md)|Creates an Application Gateway Web Application Firewall v2 with custom rules.|
+|[WAF v2 custom rules](scripts/waf-custom-rules-powershell.md)|Creates an Application Gateway Web Application Firewall v2 with custom rules.|
application-gateway Quick Create Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/quick-create-bicep.md
Last updated 04/14/2022 -+ # Quickstart: Direct web traffic with Azure Application Gateway - Bicep
application-gateway Quick Create Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/quick-create-template.md
Last updated 06/10/2022 -+ # Quickstart: Direct web traffic with Azure Application Gateway - ARM template
application-gateway Resource Manager Template Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/resource-manager-template-samples.md
description: This article has links to Azure Resource Manager template examples
+ Last updated 11/16/2019
The following table includes links to Azure Resource Manager templates for Azure
| Example | Description | |-- | -- |
-| [Application Gateway v2 with Web Application Firewall](https://azure.microsoft.com/resources/templates/ag-docs-wafv2/) | Creates an Application Gateway v2 with Web Application Firewall v2.|
+| [Application Gateway v2 with Web Application Firewall](https://azure.microsoft.com/resources/templates/ag-docs-wafv2/) | Creates an Application Gateway v2 with Web Application Firewall v2.|
application-gateway Tutorial Protect Application Gateway Ddos https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/application-gateway/tutorial-protect-application-gateway-ddos.md
Title: 'Tutorial: Protect your application gateway with Azure DDoS Protection Standard'
+ Title: 'Tutorial: Protect your application gateway with Azure DDoS Network Protection'
description: Learn how to set up an application gateway and protect it with Azure DDoS protection Previously updated : 12/21/2022 Last updated : 04/06/2023
-# Tutorial: Protect your application gateway with Azure DDoS Protection Standard
+# Tutorial: Protect your application gateway with Azure DDoS Network Protection
-This article helps you create an Azure Application Gateway with a DDoS protected virtual network. Azure DDoS Protection Standard enables enhanced DDoS mitigation capabilities such as adaptive tuning, attack alert notifications, and monitoring to protect your application gateways from large scale DDoS attacks.
+This article helps you create an Azure Application Gateway with a DDoS protected virtual network. Azure DDoS Network Protection enables enhanced DDoS mitigation capabilities such as adaptive tuning, attack alert notifications, and monitoring to protect your application gateways from large scale DDoS attacks.
> [!IMPORTANT]
-> Azure DDoS Protection incurs a cost when you use the Standard SKU. Overages charges only apply if more than 100 public IPs are protected in the tenant. Ensure you delete the resources in this tutorial if you aren't using the resources in the future. For information about pricing, see [Azure DDoS Protection Pricing]( https://azure.microsoft.com/pricing/details/ddos-protection/). For more information about Azure DDoS protection, see [What is Azure DDoS Protection?](../ddos-protection/ddos-protection-overview.md).
+> Azure DDoS Protection incurs a cost when you use the Network Protection SKU. Overages charges only apply if more than 100 public IPs are protected in the tenant. Ensure you delete the resources in this tutorial if you aren't using the resources in the future. For information about pricing, see [Azure DDoS Protection Pricing]( https://azure.microsoft.com/pricing/details/ddos-protection/). For more information about Azure DDoS protection, see [What is Azure DDoS Protection?](../ddos-protection/ddos-protection-overview.md).
In this tutorial, you learn how to:
Review the settings on the **Review + create** tab, and then select **Create** t
## Enable DDoS protection
-Azure DDoS protection Standard is enabled at the virtual network where the resource you want to protect reside.
+Azure DDoS Network Protection is enabled at the virtual network where the resource you want to protect reside.
1. In the search box at the top of the portal, enter **Virtual network**. Select **Virtual networks** in the search results.
Azure DDoS protection Standard is enabled at the virtual network where the resou
5. In the pull-down box in DDoS protection plan, select **myDDoSProtectionPlan**.
- :::image type="content" source="./media/tutorial-protect-application-gateway/enable-ddos-vnet.png" alt-text="Screenshot of ddos protection.":::
+ :::image type="content" source="./media/tutorial-protect-application-gateway/enable-ddos-vnet.png" alt-text="Screenshot of D D o S network protection.":::
6. Select **Save**.
To delete the resource group:
Advance to the next article to learn how to: > [!div class="nextstepaction"]
-> [Configure an application gateway with TLS termination using the Azure portal](create-ssl-portal.md)
+> [Configure an application gateway with TLS termination using the Azure portal](create-ssl-portal.md)
applied-ai-services Whats New https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/applied-ai-services/form-recognizer/whats-new.md
Form Recognizer service is updated on an ongoing basis. Bookmark this page to st
* [**Custom template model**](concept-custom-template.md) now has an improved signature detection capability. * [**Form Recognizer Studio**](https://formrecognizer.appliedai.azure.com/studio) updates * In addition to support for all the new features like classification and query fields, the Studio now enables project sharing for custom model projects.
- * New model additions in gated preview: **Vaccination cards**, **Contracts**, **US Tax 1098**, **US Tax 1098-E**, and **US Tax 1095-T**. To request access to gated preview models, complete and submit the [**Form Recognizer private preview request form**](https://aka.ms/form-recognizer/preview/survey).
+ * New model additions in gated preview: **Vaccination cards**, **Contracts**, **US Tax 1098**, **US Tax 1098-E**, and **US Tax 1098-T**. To request access to gated preview models, complete and submit the [**Form Recognizer private preview request form**](https://aka.ms/form-recognizer/preview/survey).
* [**Receipt model updates**](concept-receipt.md) * Receipt model has added support for thermal receipts. * Receipt model now has added language support for 18 languages and three language dialects (English, French, Portuguese).
applied-ai-services How To Prepare Html https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/applied-ai-services/immersive-reader/how-to-prepare-html.md
-+ Last updated 03/04/2021
applied-ai-services Language Support https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/applied-ai-services/immersive-reader/language-support.md
-+ Last updated 11/15/2021
applied-ai-services Release Notes https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/applied-ai-services/immersive-reader/release-notes.md
-+ Last updated 11/15/2021
attestation Quickstart Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/attestation/quickstart-Bicep.md
-+ Last updated 03/08/2022
attestation Quickstart Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/attestation/quickstart-template.md
-+ Last updated 01/23/2023
automanage Arm Deploy Arc https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automanage/arm-deploy-arc.md
Title: Onboard an Azure Arc-enabled server to Azure Automanage with an ARM templ
description: Learn how to onboard an Azure Arc-enabled server to Azure Automanage with an Azure Resource Manager template. + Last updated 02/25/2022
automanage Arm Deploy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automanage/arm-deploy.md
Title: Onboard a machine to Azure Automanage with an ARM template
description: Learn how to onboard a machine to Azure Automanage with an Azure Resource Manager template. + Last updated 12/10/2021
automanage Virtual Machines Custom Profile https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automanage/virtual-machines-custom-profile.md
description: Learn how to create a custom profile in Azure Automanage and select
+ Last updated 08/01/2022
As with any ARM template, it's possible to factor out the parameters into a sepa
Get the most frequently asked questions answered in our FAQ. > [!div class="nextstepaction"]
-> [Frequently Asked Questions](faq.yml)
+> [Frequently Asked Questions](faq.yml)
automation Automation Deploy Template Runbook https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/automation-deploy-template-runbook.md
Last updated 09/23/2021 -+ #Customer intent: As a developer, I want to use Runbooks to deploy ARM templates so that I can increase efficiency.
Get-AzStorageAccount
* To learn more about Resource Manager templates, see [Azure Resource Manager overview](../azure-resource-manager/management/overview.md). * To get started with Azure Storage, see [Introduction to Azure Storage](../storage/common/storage-introduction.md).
-* To find other useful Azure Automation runbooks, see [Use runbooks and modules in Azure Automation](automation-runbook-gallery.md).
+* To find other useful Azure Automation runbooks, see [Use runbooks and modules in Azure Automation](automation-runbook-gallery.md).
automation Automation Dsc Getting Started https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/automation-dsc-getting-started.md
Title: Get started with Azure Automation State Configuration
description: This article tells how to do the most common tasks in Azure Automation State Configuration. + Last updated 01/03/2022
automation Automation Webhooks https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/automation-webhooks.md
Last updated 07/21/2021 -+ # Start a runbook from a webhook
Automation webhooks can also be created using [Azure Resource Manager](../azure-
## Next steps
-* To trigger a runbook from an alert, see [Use an alert to trigger an Azure Automation runbook](automation-create-alert-triggered-runbook.md).
+* To trigger a runbook from an alert, see [Use an alert to trigger an Azure Automation runbook](automation-create-alert-triggered-runbook.md).
automation Extension Based Hybrid Runbook Worker Install https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/extension-based-hybrid-runbook-worker-install.md
Title: Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in
description: This article provides information about deploying the extension-based User Hybrid Runbook Worker to run runbooks on Windows or Linux machines in your on-premises datacenter or other cloud environment. -+ Last updated 04/01/2023 #Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
automation Migrate Existing Agent Based Hybrid Worker To Extension Based Workers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md
Title: Migrate an existing agent-based hybrid workers to extension-based-workers
description: This article provides information on how to migrate an existing agent-based hybrid worker to extension based workers. + Last updated 04/01/2023 #Customer intent: As a developer, I want to learn about extension so that I can efficiently migrate agent based hybrid workers to extension based workers.
automation Quickstart Create Automation Account Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/quickstart-create-automation-account-template.md
Last updated 08/27/2021 -+ # Create an Azure Automation account using a Resource Manager template
automation Remove User Assigned Identity https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/remove-user-assigned-identity.md
Title: Remove user-assigned managed identity for Azure Automation account
description: This article explains how to remove a user-assigned managed identity for an Azure Automation account. -+ Last updated 10/26/2021
automation Enable From Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/update-management/enable-from-template.md
Title: Enable Update Management using Azure Resource Manager template
description: This article tells how to use an Azure Resource Manager template to enable Update Management. + Last updated 09/18/2020
automation Whats New https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/whats-new.md
description: Significant updates to Azure Automation updated each month.
Previously updated : 03/27/2023 Last updated : 04/05/2023
Azure Automation receives improvements on an ongoing basis. To stay up to date w
This page is updated monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in [Archive for What's new in Azure Automation](whats-new-archive.md). ++
+## April 2023
+
+### Public preview update: Azure Automation supports PowerShell 7.2 and Python 3.10 runbooks
+
+Azure Automation has expanded Public preview support for PowerShell 7.2 and Python 3.10 runbooks in almost all [Public regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=automation) except Australia Central2, Korea South, Sweden South, Jio India Central, Brazil Southeast, Central India, West India, UAE Central and Gov clouds. These new runtimes are now supported for both Cloud and Hybrid jobs. Learn more about [PowerShell 7.2 and Python 3.10 runbooks](automation-runbook-types.md) and [execution of Hybrid jobs](automation-hrw-run-runbooks.md#service-accounts) on new runtime versions.
+ ## March 2023 ### Retirement of Azure Automation Agent-based User Hybrid Runbook Worker
azure-app-configuration Powershell Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/powershell-samples.md
Title: PowerShell samples description: Learn about the Azure PowerShell sample scripts available for App Configuration. + Last updated 01/19/2023
azure-app-configuration Quickstart Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-bicep.md
Last updated 05/06/2022 -+ # Quickstart: Create an Azure App Configuration store using Bicep
azure-app-configuration Quickstart Resource Manager https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-resource-manager.md
Last updated 06/09/2021 -+ # Quickstart: Create an Azure App Configuration store by using an ARM template
azure-arc Create Custom Configuration Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/create-custom-configuration-template.md
description: Create custom configuration templates
+
azure-arc Delete Azure Resources https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/delete-azure-resources.md
description: Delete resources from Azure
+
azure-arc Deploy Active Directory Connector Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/deploy-active-directory-connector-cli.md
description: Tutorial to deploy an Active Directory connector using Azure CLI
+
az arcdata ad-connector delete --name arcadc --data-controller-name arcdc --reso
* [Tutorial ΓÇô Deploy AD connector in customer-managed keytab mode](deploy-customer-managed-keytab-active-directory-connector.md) * [Tutorial ΓÇô Deploy AD connector in system-managed keytab mode](deploy-system-managed-keytab-active-directory-connector.md) * [Deploy Arc-enabled SQL Managed Instance with Active Directory Authentication](deploy-active-directory-sql-managed-instance.md).-
azure-arc Deploy Active Directory Postgresql Server Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/deploy-active-directory-postgresql-server-cli.md
description: Explains how to deploy Active Directory integrated Azure Arc-enable
+
az postgres server-arc update
## Next steps - **Try it out.** Get started quickly with [Azure Arc Jumpstart](https://github.com/microsoft/azure_arc#azure-arc-enabled-data-services) on Azure Kubernetes Service (AKS), AWS Elastic Kubernetes Service (EKS), Google Cloud Kubernetes Engine (GKE) or in an Azure VM. -
azure-arc Deploy Active Directory Sql Managed Instance Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance-cli.md
description: Explains how to deploy Active Directory integrated Azure Arc-enable
+
az sql mi-arc delete --name contososqlmi --resource-group arc-rg
## Next steps * [Deploy Arc-enabled SQL Managed Instance with Active Directory Authentication](deploy-active-directory-sql-managed-instance.md). * [Connect to Active Directory integrated Azure Arc-enabled SQL Managed Instance](connect-active-directory-sql-managed-instance.md).-
azure-arc Install Arcdata Extension https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/install-arcdata-extension.md
description: Install the `arcdata` extension for Azure (`az`) CLI
+
azure-arc Install Client Tools https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/install-client-tools.md
description: Install azdata, kubectl, Azure CLI, psql, Azure Data Studio (Inside
+
azure-arc List Servers Postgresql https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/list-servers-postgresql.md
description: List the Azure Arc-enabled PostgreSQL servers created in an Azure A
+
azure-arc Rotate User Tls Certificate https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/rotate-user-tls-certificate.md
description: Rotate user-provided TLS certificate in indirectly connected Azure
+
azure-arc Uninstall Azure Arc Data Controller https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/data/uninstall-azure-arc-data-controller.md
description: Uninstall Azure Arc-enabled data services
+
azure-arc Tutorial Arc Enabled Open Service Mesh https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/kubernetes/tutorial-arc-enabled-open-service-mesh.md
Title: Azure Arc-enabled Open Service Mesh description: Open Service Mesh (OSM) extension on Azure Arc-enabled Kubernetes cluster-+ Last updated 10/12/2022
azure-arc Deploy Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/resource-bridge/deploy-cli.md
Title: Azure Arc resource bridge (preview) deployment command overview
description: Learn about the Azure CLI commands that can be used to manage your Azure Arc resource bridge (preview) deployment. Last updated 02/06/2023 +
azure-arc Manage Vm Extensions Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/servers/manage-vm-extensions-template.md
Title: Enable VM extension using Azure Resource Manager template
description: This article describes how to deploy virtual machine extensions to Azure Arc-enabled servers running in hybrid cloud environments using an Azure Resource Manager template. Last updated 06/02/2022 + # Enable Azure VM extensions by using ARM template
azure-arc Prerequisites https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-arc/servers/prerequisites.md
Title: Connected Machine agent prerequisites
description: Learn about the prerequisites for installing the Connected Machine agent for Azure Arc-enabled servers. Last updated 01/25/2023 + # Connected Machine agent prerequisites
You can also register the resource providers in the [Azure portal](../../azure-r
* Review the [networking requirements for deploying Azure Arc-enabled servers](network-requirements.md). * Before you deploy the Azure Arc-enabled servers agent and integrate with other Azure management and monitoring services, review the [Planning and deployment guide](plan-at-scale-deployment.md).* To resolve problems, review the [agent connection issues troubleshooting guide](troubleshoot-agent-onboard.md).-
azure-cache-for-redis Cache Best Practices Performance https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-best-practices-performance.md
description: Learn how to test the performance of Azure Cache for Redis.
Previously updated : 08/25/2021 Last updated : 04/06/2022 # Performance testing
-1. Start by using `redis-benchmark.exe` to check the general throughput and latency characteristics of your cache before writing your own performance tests. For more information, see [Redis-Benchmark](#redis-benchmark-utility).
+Testing the performance of a Redis instance can be a complicated task. The performance of a Redis instance can vary based on parameters such as the number of clients, the size of data values, and whether pipelining is being used. There also can be a tradeoff between optimizing throughput or latency.
-1. The client VM used for testing should be *in the same region* as your Redis cache instance.
+Fortunately, several tools exist to make benchmarking Redis easier. Two of the most popular tools are **[redis-benchmark](https://redis.io/docs/management/optimization/benchmarks/)** and **[memtier-benchmark](https://github.com/redislabs/memtier_benchmark)**. This article focuses on redis-benchmark.
-1. Make sure the client VM you use has *at least as much compute and bandwidth* as the cache being tested.
+## How to use the redis-benchmark utility
-1. It's important that you don't test the performance of your cache only under steady state conditions. *Test under failover conditions too*, and measure the CPU/Server Load on your cache during that time. You can start a failover by [rebooting the primary node](cache-administration.md#reboot). Testing under failover conditions allows you to see the throughput and latency of your application during failover conditions. Failover can happen during updates or during an unplanned event. Ideally you don't want to see CPU/Server Load peak to more than say 80% even during a failover as that can affect performance.
+1. Install open source Redis server to a client VM you can use for testing. The redis-benchmark utility is built into the open source Redis distribution. Follow the [Redis documentation](https://redis.io/docs/getting-started/#install-redis) for instructions on how to install the open source image.
-1. Consider using Premium tier Azure Cache for Redis instances. These cache sizes have better network latency and throughput because they're running on better hardware for both CPU and network.
+1. The client VM used for testing should be *in the same region* as your Azure Cache for Redis instance.
- > [!NOTE]
- > Our observed performance results are [published here](./cache-planning-faq.yml#azure-cache-for-redis-performance) for your reference. Also, be aware that SSL/TLS adds some overhead, so you may get different latencies and/or throughput if you're using transport encryption.
+1. Make sure the client VM you use has *at least as much compute and bandwidth* as the cache instance being tested.
-## Redis-benchmark utility
+1. Configure your [network isolation](cache-network-isolation.md) and [firewall](cache-configure.md#firewall) settings to ensure that the client VM is able to access your Azure Cache for Redis instance.
-**Redis-benchmark** documentation can be [found here](https://redis.io/docs/reference/optimization/benchmarks/).
+1. If you're using TLS/SSL on your cache instance, you need to add the `--tls` parameter to your redis-benchmark command or use a proxy like [stunnel](https://www.stunnel.org/https://docsupdatetracker.net/index.html).
-The `redis-benchmark.exe` doesn't support TLS. You'll have to [enable the Non-TLS port through the Portal](cache-configure.md#access-ports) before you run the test. A Windows-compatible version of redis-benchmark.exe can be found [here](https://github.com/MSOpenTech/redis/releases).
+1. `Redis-benchmark` uses port 6379 by default. Use the `-p` parameter to override this setting. You need to do use `-p`, if you're using the SSL/TLS (port 6380) or are using the Enterprise tier (port 10000).
+
+1. If you're using an Azure Cache for Redis instance that uses [clustering](cache-how-to-scale.md), you need to add the `--cluster` parameter to your `redis-benchmark` command. Enterprise tier caches using the [Enterprise clustering policy](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise) can be treated as nonclustered caches and don't need this setting.
+
+1. Launch `redis-benchmark` from the CLI or shell of the VM. For instructions on how to configure and run the tool, see the [redis-benchmark documentation](https://redis.io/docs/management/optimization/benchmarks/) and the [redis-benchmark examples](#redis-benchmark-examples) sections.
+
+## Benchmarking recommendations
+
+- It's important to not only test the performance of your cache under steady state conditions. *Test under failover conditions too*, and measure the CPU/Server Load on your cache during that time. You can start a failover by [rebooting the primary node](cache-administration.md#reboot). Testing under failover conditions allows you to see the throughput and latency of your application during failover conditions. Failover can happen during updates or during an unplanned event. Ideally, you don't want to see CPU/Server Load peak to more than say 80% even during a failover as that can affect performance.
+
+- Consider using Enterprise and Premium tier Azure Cache for Redis instances. These cache sizes have better network latency and throughput because they're running on better hardware.
+
+- The Enterprise tier generally has the best performance, as Redis Enterprise allows the core Redis process to utilize multiple vCPUs. Tiers based on open source Redis, such as Standard and Premium, are only able to utilize one vCPU for the Redis process per shard.
+
+- Benchmarking the Enterprise Flash tier can be difficult because some keys are stored on DRAM whiles some are stored on a NVMe flash disk. The keys on DRAM benchmark almost as fast as an Enterprise tier instance, but the keys on the NVMe flash disk are slower. Since the Enterprise Flash tier intelligently places the most-used keys into DRAM, ensure that your benchmark configuration matches the actual usage you expect. Consider using the `-r` parameter to randomize which keys are accessed.
+
+- Using TLS/SSL decreases throughput performance, which can be seen clearly in the example benchmarking data in the following tables.
+
+- Even though a Redis server is single-threaded, scaling up tends to improve throughput performance. System processes can use the extra vCPUs instead of sharing the vCPU being used by the Redis process. Scaling up is especially helpful on the Enterprise and Enterprise Flash tiers because Redis Enterprise isn't limited to a single thread. For more information, see [Enterprise tier best practices](cache-best-practices-enterprise-tiers.md#scaling).
+
+- On the Premium tier, scaling out, clustering, is typically recommended before scaling up. Clustering allows Redis server to use more vCPUs by sharding data. Throughput should increase roughly linearly when adding shards in this case.
## Redis-benchmark examples
Pipelined GET requests with 1k payload:
redis-benchmark -h yourcache.redis.cache.windows.net -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50 ```
+**To test throughput of a Basic, Standard, or Premium tier cache using TLS:**
+Pipelined GET requests with 1k payload:
+```dos
+redis-benchmark -h yourcache.redis.cache.windows.net -p 6380 -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50 --tls
+```
+
+**To test throughput of an Enterprise or Enterprise Flash cache without TLS using OSS Cluster Mode:**
+Pipelined GET requests with 1k payload:
+```dos
+redis-benchmark -h yourcache.region.redisenterprise.cache.azure.net -p 10000 -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50 --cluster
+```
+
+## Example performance benchmark data
+
+The following tables show the maximum throughput values that were observed while testing various sizes of Standard, Premium, Enterprise, and Enterprise Flash caches. We used `redis-benchmark` from an IaaS Azure VM against the Azure Cache for Redis endpoint. The throughput numbers are only for GET commands. Typically, SET commands have a lower throughput. These numbers are optimized for throughput. Real-world throughput under acceptable latency conditions may be lower.
+
+The following configuration was used to benchmark throughput:
+
+```dos
+redis-benchmark -h yourcache.redis.cache.windows.net -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50
+```
+
+>[!CAUTION]
+>These values aren't guaranteed and there's no SLA for these numbers. We strongly recommend that you should [perform your own performance testing](cache-best-practices-performance.md) to determine the right cache size for your application.
+>These numbers might change as we post newer results periodically.
+>
+
+### Standard tier
+
+| Instance | Size | vCPUs | Expected network bandwidth (Mbps)| GET requests per second without SSL (1-kB value size) | GET requests per second with SSL (1-kB value size) |
+| | | | | | |
+| C0 | 250 MB | Shared | 100 | 15,000 | 7,500 |
+| C1 | 1 GB | 1 | 500 | 38,000 | 20,720 |
+| C2 | 2.5 GB | 2 | 500 | 41,000 | 37,000 |
+| C3 | 6 GB | 4 | 1000 | 100,000 | 90,000 |
+| C4 | 13 GB | 2 | 500 | 60,000 | 55,000 |
+| C5 | 26 GB | 4 | 1,000 | 102,000 | 93,000 |
+| C6 | 53 GB | 8 | 2,000 | 126,000 | 120,000 |
+
+### Premium tier
+| Instance | Size | vCPUs | Expected network bandwidth (Mbps)| GET requests per second without SSL (1-kB value size) | GET requests per second with SSL (1-kB value size) |
+| | | | | | |
+| P1 | 6 GB | 2 | 1,500 | 180,000 | 172,000 |
+| P2 | 13 GB | 4 | 3,000 | 350,000 | 341,000 |
+| P3 | 26 GB | 4 | 3,000 | 350,000 | 341,000 |
+| P4 | 53 GB | 8 | 6,000 | 400,000 | 373,000 |
+| P5 | 120 GB | 32 | 6,000 | 400,000 | 373,000 |
+
+> [!Important]
+> P5 instances in the China East and China North regions use 20 cores, not 32 cores.
+
+### Enterprise & Enterprise Flash tiers
+
+The Enterprise and Enterprise Flash tiers offer a choice of cluster policy: _Enterprise_ and _OSS_. Enterprise cluster policy is a simpler configuration that doesn't require the client to support clustering. OSS cluster policy, on the other hand, uses the [Redis cluster protocol](https://redis.io/docs/management/scaling) to support higher throughputs. We recommend using OSS cluster policy in most cases. For more information, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise). Benchmarks for both cluster policies are shown in the following tables.
+
+**Enterprise Cluster Policy**
+
+| Instance | Size | vCPUs | Expected network bandwidth (Mbps)| GET requests per second without SSL (1-kB value size) | GET requests per second with SSL (1-kB value size) |
+| | | | | | |
+| E10 | 12 GB | 4 | 4,000 | 300,000 | 200,000 |
+| E20 | 25 GB | 4 | 4,000 | 550,000 | 390,000 |
+| E50 | 50 GB | 8 | 8,000 | 950,000 | 530,000 |
+| E100 | 100 GB | 16 | 10,000 | 1,300,000 | 580,000 |
+| F300 | 384 GB | 8 | 3,200 | 650,000 | 310,000 |
+| F700 | 715 GB | 16 | 6,400 | 650,000 | 350,000 |
+| F1500 | 1455 GB | 32 | 12,800 | 650,000 | 360,000 |
+
+**OSS Cluster Policy**
+
+| Instance | Size | vCPUs | Expected network bandwidth (Mbps)| GET requests per second without SSL (1-kB value size) | GET requests per second with SSL (1-kB value size) |
+| | | | | | |
+| E10 | 12 GB | 4 | 4,000 | 1,300,000 | 800,000 |
+| E20 | 25 GB | 4 | 4,000 | 1,000,000 | 710,000 |
+| E50 | 50 GB | 8 | 8,000 | 2,000,000 | 950,000 |
+| E100 | 100 GB | 16 | 10,000 | 2,000,000 | 960,000 |
+| F300 | 384 GB | 8 | 3,200 | 1,300,000 | 610,000 |
+| F700 | 715 GB | 16 | 6,400 | 1,300,000 | 680,000 |
+| F1500 | 1455 GB | 32 | 12,800 | 1,300,000 | 620,000 |
+
+### Enterprise & Enterprise Flash Tiers - Scaled Out
+
+In addition to scaling up by moving to larger cache size, you can boost performance by [scaling out](cache-how-to-scale.md#how-to-scale-up-and-outenterprise-and-enterprise-flash-tiers). In the Enterprise tiers, scaling out is called increasing the _capacity_ of the cache instance. A cache instance by default has capacity of two--meaning a primary and replica node. An Enterprise cache instance with a capacity of four indicates that the instance was scaled out by a factor of two. Scaling out provides access to more memory and vCPUs. Details on how many vCPUs are used by the core Redis process at each cache size and capacity can be found at the [Enterprise tiers best practices page](cache-best-practices-enterprise-tiers.md#sharding-and-cpu-utilization). Scaling out is most effective when using the OSS cluster policy.
+
+The following tables show the GET requests per second at different capacities, using SSL and a 1-kB value size.
+
+**Scaling out - Enterprise cluster policy**
+
+| Instance | Capacity 2 | Capacity 4 | Capacity 6 |
+| | | | |
+| E10 | 200,000 | 530,000 | 570,000 |
+| E20 | 390,000 | 520,000 | 580,000 |
+| E50 | 530,000 | 580,000 | 580,000 |
+| E100 | 580,000 | 580,000 | 580,000 |
+
+| Instance | Capacity 3 | Capacity 9 |
+| | | |
+| F300 | 310,000 | 530,000 |
+| F700 | 350,000 | 550,000 |
+| F1500 | 360,000 | 550,000 |
+
+**Scaling out - OSS cluster policy**
+
+| Instance | Capacity 2 | Capacity 4 | Capacity 6 |
+| | | | |
+| E10 | 800,000 | 720,000 | 1,280,000 |
+| E20 | 710,000 | 950,000 | 1,250,000 |
+| E50 | 950,000 | 1,260,000 | 1,300,000 |
+| E100 | 960,000 | 1,840,000 | 1,930,000|
+
+| Instance | Capacity 3 | Capacity 9 |
+| | | |
+| F300 | 610,000 | 970,000 |
+| F700 | 680,000 | 1,280,000 |
+| F1500 | 620,000 | 1,850,000 |
+ ## Next steps - [Development](cache-best-practices-development.md)
azure-cache-for-redis Cache Configure https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-configure.md
The **maxfragmentationmemory-reserved** setting configures the amount of memory
When choosing a new memory reservation value (**maxmemory-reserved** or **maxfragmentationmemory-reserved**), consider how this change might affect a cache that is already running with large amounts of data in it. For instance, if you have a 53-GB cache with 49 GB of data, then change the reservation value to 8 GB, this change drops the max available memory for the system down to 45 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the new limit of 45 GB, then the system will have to evict data until both `used_memory` and `used_memory_rss` are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](cache-how-to-monitor.md#create-your-own-metrics). > [!IMPORTANT]
-> The **maxmemory-reserved** and **maxfragmentationmemory-reserved** settings are available only for Standard and Premium caches.
+> The **maxmemory-reserved** and **maxfragmentationmemory-reserved** settings are available for Basic,Standard and Premium caches.
> #### Keyspace notifications (advanced settings)
azure-cache-for-redis Cache How To Active Geo Replication https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-how-to-active-geo-replication.md
description: Learn how to replicate your Azure Cache for Redis Enterprise instan
+ Last updated 03/23/2023 - # Configure active geo-replication for Enterprise Azure Cache for Redis instances
azure-cache-for-redis Cache How To Geo Replication https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-how-to-geo-replication.md
Yes, geo-replication of caches in VNets is supported with caveats:
- Geo-replication between caches in the same VNet is supported. - Geo-replication between caches in different VNets is also supported. - If the VNets are in the same region, you can connect them using [VNet peering](../virtual-network/virtual-network-peering-overview.md) or a [VPN Gateway VNet-to-VNet connection](../vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md).
- - If the VNets are in different regions, geo-replication using VNet peering is supported. A client VM in VNet 1 (region 1) isn't able to access the cache in VNet 2 (region 2) using its DNS name because of a constraint with Basic internal load balancers. For more information about VNet peering constraints, see [Virtual Network - Peering - Requirements and constraints](../virtual-network/virtual-network-manage-peering.md#requirements-and-constraints). We recommend using a VPN Gateway VNet-to-VNet connection.
+ - If the VNets are in different regions, geo-replication using VNet peering is not supported. A client VM in VNet 1 (region 1) isn't able to access the cache in VNet 2 (region 2) using its DNS name because of a constraint with Basic internal load balancers. For more information about VNet peering constraints, see [Virtual Network - Peering - Requirements and constraints](../virtual-network/virtual-network-manage-peering.md#requirements-and-constraints). We recommend using a VPN Gateway VNet-to-VNet connection.
To configure your VNet effectively and avoid geo-replication issues, you must configure both the inbound and outbound ports correctly. For more information on avoiding the most common VNet misconfiguration issues, see [Geo-replication peer port requirements](cache-how-to-premium-vnet.md#geo-replication-peer-port-requirements).
azure-cache-for-redis Cache How To Premium Clustering https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-how-to-premium-clustering.md
The following list contains answers to commonly asked questions about Azure Cach
* [Can I configure clustering for a basic or standard cache?](#can-i-configure-clustering-for-a-basic-or-standard-cache) * [Can I use clustering with the Redis ASP.NET Session State and Output Caching providers?](#can-i-use-clustering-with-the-redis-aspnet-session-state-and-output-caching-providers) * [I'm getting MOVE exceptions when using StackExchange.Redis and clustering, what should I do?](#im-getting-move-exceptions-when-using-stackexchangeredis-and-clustering-what-should-i-do)
+* [Does scaling out using clustering help to increase the number of supported client connections?](#Does scaling out using clustering help to increase the number of supported client connections?)
### Do I need to make any changes to my client application to use clustering?
Clustering is only available for premium caches.
If you're using StackExchange.Redis and receive `MOVE` exceptions when using clustering, ensure that you're using [StackExchange.Redis 1.1.603](https://www.nuget.org/packages/StackExchange.Redis/) or later. For instructions on configuring your .NET applications to use StackExchange.Redis, see [Configure the cache clients](cache-dotnet-how-to-use-azure-redis-cache.md#configure-the-cache-client).
+### Does scaling out using clustering help to increase the number of supported client connections?
+
+No,scaling out using clustering and increasing the number of shards doesn't help in increasing the number of supported client connections.
+ ## Next steps Learn more about Azure Cache for Redis features.
azure-cache-for-redis Cache How To Upgrade https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-how-to-upgrade.md
Last updated 12/15/2022-+
azure-cache-for-redis Cache How To Version https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-how-to-version.md
+ Last updated 09/08/2022- # Set Redis version for Azure Cache for Redis
azure-cache-for-redis Cache Managed Identity https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-managed-identity.md
description: Learn to Azure Cache for Redis
+ Last updated 08/29/2022
azure-cache-for-redis Cache Redis Cache Arm Provision https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-redis-cache-arm-provision.md
-+ Last updated 04/28/2021
azure-cache-for-redis Cache Redis Cache Bicep Provision https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-redis-cache-bicep-provision.md
-+ Last updated 05/24/2022
azure-cache-for-redis Cache Web App Arm With Redis Cache Provision https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-web-app-arm-with-redis-cache-provision.md
+ Last updated 01/06/2017
azure-cache-for-redis Cache Web App Bicep With Redis Cache Provision https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/cache-web-app-bicep-with-redis-cache-provision.md
Title: Provision Web App that uses Azure Cache for Redis using Bicep
description: Use Bicep to deploy web app with Azure Cache for Redis. + Last updated 05/24/2022
azure-cache-for-redis Quickstart Create Redis Enterprise https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-cache-for-redis/quickstart-create-redis-enterprise.md
Previously updated : 04/12/2022 Last updated : 04/07/2023 # Quickstart: Create a Redis Enterprise cache
Last updated 04/12/2022
The Azure Cache for Redis Enterprise tiers provide fully integrated and managed [Redis Enterprise](https://redislabs.com/redis-enterprise/) on Azure. These new tiers are: * Enterprise, which uses volatile memory (DRAM) on a virtual machine to store data
-* Enterprise Flash, which uses both volatile and non-volatile memory (NVMe or SSD) to store data.
+* Enterprise Flash, which uses both volatile and nonvolatile memory (NVMe or SSD) to store data.
Both Enterprise and Enterprise Flash support open-source Redis 6 and some new features that aren't yet available in the Basic, Standard, or Premium tiers. The supported features include some Redis modules that enable other features like search, bloom filters, and time series.
Azure Cache for Redis is continually expanding into new regions. To check the av
| | - | -- | | **Subscription** | Drop down and select your subscription. | The subscription under which to create this new Azure Cache for Redis instance. | | **Resource group** | Drop down and select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
- | **DNS name** | Enter a name that is unique in the region. | The cache name must be a string between 1 and 63 characters that contain only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* will be *\<DNS name\>.\<Azure region\>.redisenterprise.cache.azure.net*. |
+ | **DNS name** | Enter a name that is unique in the region. | The cache name must be a string between 1 and 63 characters that contain only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* is *\<DNS name\>.\<Azure region\>.redisenterprise.cache.azure.net*. |
| **Location** | Drop down and select a location. | Enterprise tiers are available in selected Azure regions. | | **Cache type** | Drop down and select an *Enterprise* or *Enterprise Flash* tier and a size. | The tier determines the size, performance, and features that are available for the cache. |
Azure Cache for Redis is continually expanding into new regions. To check the av
Enable **Non-TLS access only** if you plan to connect to the new cache without using TLS. Disabling TLS is **not** recommended, however.
- Set **Clustering policy** to **Enterprise** for a non-clustered cache. For more information on choosing **Clustering policy**, see [Clustering Policy](#clustering-policy).
+ Set **Clustering policy** to **Enterprise** for a nonclustered cache. For more information on choosing **Clustering policy**, see [Clustering Policy](#clustering-policy).
:::image type="content" source="media/cache-create/cache-clustering-policy.png" alt-text="Screenshot that shows the Enterprise tier Advanced tab."::: > [!NOTE]
- > Redis Enterprise supports two clustering policies. Use the **Enterprise** policy to access your cache using the regular Redis API. Use **OSS** to use the OSS Cluster API.
- >
+ > Enterprise and Enterprise Flash tiers are inherently clustered, in contrast to the Basic, Standard, and Premium tiers. Redis Enterprise supports two clustering policies.
+ >- Use the **Enterprise** policy to access your cache using the Redis API.
+ >- Use **OSS** to use the OSS Cluster API.
+ > For more information, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise).
+ >
- > [!NOTE]
+ > [!IMPORTANT]
> You can't change modules after you create the cache instance. The setting is create-only. >
Azure Cache for Redis is continually expanding into new regions. To check the av
The OSS Cluster mode allows clients to communicate with Redis using the same Redis Cluster API as open-source Redis. This mode provides optimal latency and near-linear scalability improvements when scaling the cluster. Your client library must support clustering to use the OSS Cluster mode.
-The Enterprise Cluster mode is a simpler configuration that exposes a single endpoint for client connections. This mode allows an application designed to use a standalone, or non-clustered, Redis server to seamlessly operate with a scalable, multi-node, Redis implementation. Enterprise Cluster mode abstracts the Redis Cluster implementation from the client by internally routing requests to the correct node in the cluster. Clients aren't required to support OSS Cluster mode.
+The Enterprise Cluster mode is a simpler configuration that exposes a single endpoint for client connections. This mode allows an application designed to use a standalone, or nonclustered, Redis server to seamlessly operate with a scalable, multi-node, Redis implementation. Enterprise Cluster mode abstracts the Redis Cluster implementation from the client by internally routing requests to the correct node in the cluster. Clients aren't required to support OSS Cluster mode.
## Next steps In this quickstart, you learned how to create an Enterprise tier instance of Azure Cache for Redis.
-> [!div class="nextstepaction"]
-> [Create an ASP.NET web app that uses an Azure Cache for Redis.](./cache-web-app-howto.md)
+- [Create an ASP.NET web app that uses an Azure Cache for Redis](cache-web-app-aspnet-core-howto.md)
+- [Best practices for the Enterprise tiers](cache-best-practices-enterprise-tiers.md)
azure-functions Create First Function Vs Code Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/create-first-function-vs-code-powershell.md
description: Learn how to create a PowerShell function, then publish the local p
Last updated 06/22/2022 ms.devlang: powershell-+ # Quickstart: Create a PowerShell function in Azure using Visual Studio Code
azure-functions Create Resources Azure Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/create-resources-azure-powershell.md
Title: Create function app resources in Azure using PowerShell description: Azure PowerShell scripts that show you how to create the Azure resources required to host your functions code in Azure. + Last updated 07/18/2022 # Create function app resources in Azure using PowerShell
azure-functions Deployment Zip Push https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/deployment-zip-push.md
Title: Zip push deployment for Azure Functions
description: Use the .zip file deployment facilities of the Kudu deployment service to publish your Azure Functions. + Last updated 08/12/2018- # Zip deployment for Azure Functions
azure-functions Dotnet Isolated In Process Differences https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/dotnet-isolated-in-process-differences.md
Use the following table to compare feature and functional differences between th
| [Supported .NET versions](dotnet-isolated-process-guide.md#supported-versions) | Long Term Support (LTS) versions | [All supported versions](dotnet-isolated-process-guide.md#supported-versions) + .NET Framework | | Core packages | [Microsoft.NET.Sdk.Functions](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/) | [Microsoft.Azure.Functions.Worker](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker/)<br/>[Microsoft.Azure.Functions.Worker.Sdk](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Sdk) | | Binding extension packages | [Microsoft.Azure.WebJobs.Extensions.*](https://www.nuget.org/packages?q=Microsoft.Azure.WebJobs.Extensions) | [Microsoft.Azure.Functions.Worker.Extensions.*](https://www.nuget.org/packages?q=Microsoft.Azure.Functions.Worker.Extensions) |
-| Durable Functions | [Supported](durable/durable-functions-overview.md) | [Supported (public preview)](https://github.com/microsoft/durabletask-dotnet#usage-with-azure-functions) |
+| Durable Functions | [Supported](durable/durable-functions-overview.md) | [Supported](durable/durable-functions-isolated-create-first-csharp.md?pivots=code-editor-visualstudio) |
| Model types exposed by bindings | Simple types<br/>[JSON serializable](/dotnet/api/system.text.json.jsonserializeroptions) types<br/>Arrays/enumerations<br/>Service SDK types such as [BlobClient](/dotnet/api/azure.storage.blobs.blobclient)<br/>`IAsyncCollector` (for output bindings) | Simple types<br/>JSON serializable types<br/>Arrays/enumerations<br/>[Some service-specific SDK types](dotnet-isolated-process-guide.md#sdk-types-preview) | | HTTP trigger model types| [HttpRequest](/dotnet/api/system.net.http.httpclient) / [ObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.objectresult) | [HttpRequestData](/dotnet/api/microsoft.azure.functions.worker.http.httprequestdata?view=azure-dotnet&preserve-view=true) / [HttpResponseData](/dotnet/api/microsoft.azure.functions.worker.http.httpresponsedata?view=azure-dotnet&preserve-view=true) | | Output binding interaction | Return values (single output only)<br/>`out` parameters<br/>`IAsyncCollector` | Return values (expanded model with single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)) |
azure-functions Functions Add Output Binding Storage Queue Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-add-output-binding-storage-queue-cli.md
description: Learn how to connect Azure Functions to an Azure Storage queue by a
Last updated 02/07/2020 ms.devlang: csharp, java, javascript, powershell, python, typescript-+ zone_pivot_groups: programming-languages-set-functions
azure-functions Functions Add Output Binding Storage Queue Vs Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-add-output-binding-storage-queue-vs-code.md
description: Learn how to connect Azure Functions to an Azure Queue Storage by a
Last updated 01/31/2023 ms.devlang: csharp, java, javascript, powershell, python, typescript-+ zone_pivot_groups: programming-languages-set-functions #Customer intent: As an Azure Functions developer, I want to connect my function to Azure Storage so that I can easily write data to a storage queue.
azure-functions Functions Create First Function Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-create-first-function-bicep.md
Last updated 06/12/2022 -+ # Quickstart: Create and deploy Azure Functions resources using Bicep
azure-functions Functions Create First Function Resource Manager https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-create-first-function-resource-manager.md
description: Create and deploy to Azure a simple HTTP triggered serverless funct
Last updated 07/19/2022 -+ # Quickstart: Create and deploy Azure Functions resources from an ARM template
azure-functions Functions Event Grid Blob Trigger https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-event-grid-blob-trigger.md
Title: 'Tutorial: Trigger Azure Functions on blob containers using an event subs
description: This tutorial shows how to create a low-latency, event-driven trigger on an Azure Blob Storage container using an Event Grid event subscription. + Last updated 3/1/2021 zone_pivot_groups: programming-languages-set-functions-lang-workers
azure-functions Functions Identity Based Connections Tutorial https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-identity-based-connections-tutorial.md
Whenever your app would need to add a reference to a secret, you would just need
> [!TIP] > The [Application Insights connection string](../azure-monitor/app/sdk-connection-string.md) and its included instrumentation key are not considered secrets and can be retrieved from App Insights using [Reader](../role-based-access-control/built-in-roles.md#reader) permissions. You do not need to move them into Key Vault, although you certainly can.
-## Use managed identity for AzureWebJobsStorage (Preview)
+## Use managed identity for AzureWebJobsStorage
Next you will use the system-assigned identity you configured in the previous steps for the `AzureWebJobsStorage` connection. `AzureWebJobsStorage` is used by the Functions runtime and by several triggers and bindings to coordinate between multiple running instances. It is required for your function app to operate, and like Azure Files, it is configured with a connection string by default when you create a new function app.
Similar to the steps you took before with the user-assigned identity and your ke
Next you will update your function app to use its system-assigned identity when it uses the blob service for host storage. > [!IMPORTANT]
-> The `AzureWebJobsStorage` configuration is used by some triggers and bindings, and those extensions must be able to use identity-based connections, too. Apps that use blob triggers or event hub triggers may need to update those extensions. Because no functions have been defined for this app, there isn't a concern yet. To learn more about this requirement, see [Connecting to host storage with an identity (Preview)](./functions-reference.md#connecting-to-host-storage-with-an-identity-preview).
+> The `AzureWebJobsStorage` configuration is used by some triggers and bindings, and those extensions must be able to use identity-based connections, too. Apps that use blob triggers or event hub triggers may need to update those extensions. Because no functions have been defined for this app, there isn't a concern yet. To learn more about this requirement, see [Connecting to host storage with an identity](./functions-reference.md#connecting-to-host-storage-with-an-identity).
> > Similarly, `AzureWebJobsStorage` is used for deployment artifacts when using server-side build in Linux Consumption. When you enable identity-based connections for `AzureWebJobsStorage` in Linux Consumption, you will need to deploy via [an external deployment package](run-functions-from-deployment-package.md).
azure-functions Functions Infrastructure As Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-infrastructure-as-code.md
description: Learn how to build a Bicep file or an Azure Resource Manager templa
ms.assetid: d20743e3-aab6-442c-a836-9bcea09bfd32 Last updated 08/30/2022-+ # Automate resource deployment for your function app in Azure Functions
azure-functions Functions Reference https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-reference.md
The function.json file defines the function's trigger, bindings, and other confi
For more information, see [Azure Functions triggers and bindings concepts](functions-triggers-bindings.md).
-The `bindings` property is where you configure both triggers and bindings. Each binding shares a few common settings and some settings which are specific to a particular type of binding. Every binding requires the following settings:
+The `bindings` property is where you configure both triggers and bindings. Each binding shares a few common settings and some settings, which are specific to a particular type of binding. Every binding requires the following settings:
| Property | Values | Type | Comments| |||||
The `bindings` property is where you configure both triggers and bindings. Each
| name | Function identifier.<br><br>For example, `myQueue`. | string | The name that is used for the bound data in the function. For C#, this is an argument name; for JavaScript, it's the key in a key/value list. | ## Function app
-A function app provides an execution context in Azure in which your functions run. As such, it is the unit of deployment and management for your functions. A function app is comprised of one or more individual functions that are managed, deployed, and scaled together. All of the functions in a function app share the same pricing plan, deployment method, and runtime version. Think of a function app as a way to organize and collectively manage your functions. To learn more, see [How to manage a function app](functions-how-to-use-azure-function-app-settings.md).
+A function app provides an execution context in Azure in which your functions run. As such, it is the unit of deployment and management for your functions. A function app is composed of one or more individual functions that are managed, deployed, and scaled together. All of the functions in a function app share the same pricing plan, deployment method, and runtime version. Think of a function app as a way to organize and collectively manage your functions. To learn more, see [How to manage a function app](functions-how-to-use-azure-function-app-settings.md).
> [!NOTE] > All functions in a function app must be authored in the same language. In [previous versions](functions-versions.md) of the Azure Functions runtime, this wasn't required.
For example, the `connection` property for an Azure Blob trigger definition migh
Some connections in Azure Functions can be configured to use an identity instead of a secret. Support depends on the extension using the connection. In some cases, a connection string may still be required in Functions even though the service to which you are connecting supports identity-based connections. For a tutorial on configuring your function apps with managed identities, see the [creating a function app with identity-based connections tutorial](./functions-identity-based-connections-tutorial.md).
-Identity-based connections are supported by the following components:
+The following components support identity-based connections:
| Connection source | Plans supported | Learn more | ||--|--|
Identity-based connections are supported by the following components:
| Azure Cosmos DB triggers and bindings | All | [Azure Cosmos DB extension version 4.0.0 or later][cosmosv4],<br/> [Extension bundle 4.0.2 or later][cosmosv4]| | Azure SignalR triggers and bindings | All | [Azure SignalR extension version 1.7.0 or later][signalr] <br/>[Extension bundle 3.6.1 or later][signalr] | | Durable Functions storage provider (Azure Storage) | All | [Durable Functions extension version 2.7.0 or later][durable-identity],<br/>[Extension bundle 3.3.0 or later][durable-identity] |
-| Host-required storage ("AzureWebJobsStorage") - Preview | All | [Connecting to host storage with an identity](#connecting-to-host-storage-with-an-identity-preview) |
+| Host-required storage ("AzureWebJobsStorage") | All | [Connecting to host storage with an identity](#connecting-to-host-storage-with-an-identity) |
[blobv5]: ./functions-bindings-storage-blob.md#install-extension [queuev5]: ./functions-bindings-storage-queue.md#storage-extension-5x-and-higher
Choose a tab below to learn about permissions for each component:
[!INCLUDE [functions-cosmos-permissions](../../includes/functions-cosmos-permissions.md)] # [Azure SignalR extension](#tab/signalr)
-You'll need to create a role assignment that provides access to Azure SignalR Service data plane REST APIs. We recommend you to use the built-in role [SignalR Service Owner](../role-based-access-control/built-in-roles.md#signalr-service-owner). Management roles like [Owner](../role-based-access-control/built-in-roles.md#owner) aren't sufficient.
+
+You need to create a role assignment that provides access to Azure SignalR Service data plane REST APIs. We recommend you to use the built-in role [SignalR Service Owner](../role-based-access-control/built-in-roles.md#signalr-service-owner). Management roles like [Owner](../role-based-access-control/built-in-roles.md#owner) aren't sufficient.
# [Durable Functions storage provider](#tab/durable) [!INCLUDE [functions-durable-permissions](../../includes/functions-durable-permissions.md)]
-# [Functions host storage (preview)](#tab/azurewebjobsstorage)
+# [Functions host storage](#tab/azurewebjobsstorage)
[!INCLUDE [functions-azurewebjobsstorage-permissions](../../includes/functions-azurewebjobsstorage-permissions.md)]
An identity-based connection for an Azure service accepts the following common p
| Property | Environment variable template | Description | |||||
-| Token Credential | `<CONNECTION_NAME_PREFIX>__credential` | Defines how a token should be obtained for the connection. Recommended only when specifying a user-assigned identity, when it should be set to "managedidentity". This is only valid when hosted in the Azure Functions service. |
-| Client ID | `<CONNECTION_NAME_PREFIX>__clientId` | When `credential` is set to "managedidentity", this property specifies the user-assigned identity to be used when obtaining a token. The property accepts a client ID corresponding to a user-assigned identity assigned to the application. If not specified, the system-assigned identity will be used. This property is used differently in [local development scenarios](#local-development-with-identity-based-connections), when `credential` should not be set. |
+| Token Credential | `<CONNECTION_NAME_PREFIX>__credential` | Defines how a token should be obtained for the connection. This setting is recommended only when specifying a user-assigned identity, when it should be set to "managedidentity". This value is only valid when hosted in the Azure Functions service. |
+| Client ID | `<CONNECTION_NAME_PREFIX>__clientId` | When `credential` is set to "managedidentity", this property specifies the user-assigned identity to be used when obtaining a token. The property accepts a client ID corresponding to a user-assigned identity assigned to the application. If not specified, the system-assigned identity is used. This property is used differently in [local development scenarios](#local-development-with-identity-based-connections), when `credential` should not be set. |
-Additional options may be supported for a given connection type. Please refer to the documentation for the component making the connection.
+Additional options may be supported for a given connection type. Refer to the documentation for the component making the connection.
##### Local development with identity-based connections > [!NOTE] > Local development with identity-based connections requires updated versions of the [Azure Functions Core Tools](./functions-run-local.md). You can check your currently installed version by running `func -v`. For Functions v3, use version `3.0.3904` or later. For Functions v4, use version `4.0.3904` or later.
-When running locally, the above configuration tells the runtime to use your local developer identity. The connection will attempt to get a token from the following locations, in order:
+When you are running your function project locally, the above configuration tells the runtime to use your local developer identity. The connection attempts to get a token from the following locations, in order:
- A local cache shared between Microsoft applications - The current user context in Visual Studio
Here is an example of `local.settings.json` properties required for identity-bas
} ```
-#### Connecting to host storage with an identity (Preview)
+#### Connecting to host storage with an identity
The Azure Functions host uses the "AzureWebJobsStorage" connection for core behaviors such as coordinating singleton execution of timer triggers and default app key storage. This can be configured to leverage an identity as well.
azure-functions Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/start-stop-vms/overview.md
description: This article describes version two of the Start/Stop VMs feature, w
+ Last updated 09/23/2022
azure-functions Storage Considerations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/storage-considerations.md
The storage account must be accessible to the function app. If you need to use a
### Storage account connection setting
-By default, Functions clients will configure the AzureWebJobsStorage connection as a connection string stored in the [AzureWebJobsStorage application setting](./functions-app-settings.md#azurewebjobsstorage), but you can also [configure AzureWebJobsStorage to use an identity-based connection](functions-reference.md#connecting-to-host-storage-with-an-identity-preview) without a secret.
+By default, Functions clients will configure the AzureWebJobsStorage connection as a connection string stored in the [AzureWebJobsStorage application setting](./functions-app-settings.md#azurewebjobsstorage), but you can also [configure AzureWebJobsStorage to use an identity-based connection](functions-reference.md#connecting-to-host-storage-with-an-identity) without a secret.
Function apps are configured to use Azure Files by storing a connection string in the [WEBSITE_CONTENTAZUREFILECONNECTIONSTRING application setting](./functions-app-settings.md#website_contentazurefileconnectionstring) and providing the name of the file share in the [WEBSITE_CONTENTSHARE application setting](./functions-app-settings.md#website_contentshare).
azure-functions Storage Considerations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-glossary-cloud-terminology.md
ms.assetid: d7ac12f7-24b5-4bcd-9e4d-3d76fbd8d297 + Last updated 09/17/2021
Another name for [App Service App](#app-service-app).
* [Get started with Azure](https://azure.microsoft.com/get-started/) * [Cloud resource center](https://azure.microsoft.com/resources/) * [Azure for your business application](https://azure.microsoft.com/overview/business-apps-on-azure/)
-* [Azure in your datacenter](https://azure.microsoft.com/overview/business-apps-on-azure/)
+* [Azure in your datacenter](https://azure.microsoft.com/overview/business-apps-on-azure/)
azure-government Documentation Government Ase Disa Cap https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-government/documentation-government-ase-disa-cap.md
Title: ASE deployment with DISA CAP description: This article explains the baseline App Service Environment configuration for customers who use DISA CAP to connect to Azure Government. + recommendations: false Last updated 06/27/2022
azure-maps How To Create Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-maps/how-to-create-template.md
Last updated 04/27/2021 + # Create your Azure Maps account using an ARM template
azure-maps How To Secure Sas App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-maps/how-to-secure-sas-app.md
-+ # Secure an Azure Maps account with a SAS token (preview)
azure-monitor Azure Monitor Agent Performance https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/agents/azure-monitor-agent-performance.md
+
+ Title: Performance Benchmark for forwarding Gateway using Azure Monitor Agent
+description: Performance data for the AMA running in a gateway scenario
+++ Last updated : 4/07/2023++
+#customer-intent: As a deployment engineer, I can scope the resources required to scale my gateway data colletors the use the Azure Monitor Agent.
++
+# Azure Monitor Agent Performance Benchmark
+
+The agent can handle many thousands of events per second in the gateway event forwarding scenario. The exact throughput rate depends on various factors such as the size of each event, the specific data type, and physical hardware resources. This article will describe the Microsoft internal benchmark used for testing the agent throughput of 10k Syslog events in the forwarder scenario. The benchmark results should provide a guide to size the resources that you will need in your environment.
+
+> [!NOTE]
+> The results in this article are informational about the performance of AMA in the forwarding scenario only and do not constitute any service agreement on the part of Microsoft.
+
+## Best practices for agent as a forwarder.
+
+- The forwarder should be on a dedicated system to eliminate potential interference from other workloads.
+- The forwarder system should be monitored for CPU, memory, and disk utilization to prevent overloads from causing data loss.
+- Where possible use a load balancer and redundant forwarder systems to improve reliability and scalability.
+- For other considerations for forwarders see the Log Analytics Gateway documentation.
+
+## Agent Performance
+
+The benchmark is run in a controlled environment to get repeatable, accurate, and statistically significant results. The resources consumed by the agent are measured under a load of 10,000 simulated Syslog events per second. The simulated load is run on the same physical hardware that the agent under test is on. Test trials are run for seven days. For each trial, performance metrics are sampled every second to collect CPU, memory, and network maximum and average usage. This approach provides the right information to help you estimate the resources needed for your environment.
+
+> [!NOTE]
+> The results do not measure the end-to-end throughput ingested by a Log Analytics Workspace (or other telemetry sinks), as there may be end-to-end variability due to network and backend pipeline performance.
+
+The benchmarks are run on an Azure VM Standard_F8s_v2 system using AMA Linux version 1.25.2 and 10 GB of disk space for the event cache.
+
+- vCPUΓÇÖs: 8 with HyperThreading (800% CPU is possible)
+- Memory: 16 GiB
+- Temp Storage: 64 GiB
+- Max Disk IOPS: 6400
+- Network: 12500 Mbp Max on all 4 physical NICs
+
+
+
+## Results
+
+| Perf Metric | Ave (Max) Med |
+|:|::|
+| CPU % | 51 (262) |
+| Mem RSS MB | 276 (1,017) |
+| Network KBps | 338 (18,033) |
++
+## Next steps
+
+- [Connect computers without internet access by using the Log Analytics gateway in Azure Monitor](gateway.md)
+- [Install the Azure Monitor Agent](azure-monitor-agent-manage.md) on Windows and Linux virtual machines.
+- [Create a data collection rule](data-collection-rule-azure-monitor-agent.md) to collect data from the agent and send it to Azure Monitor.
+
azure-monitor Resource Manager Agent https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/agents/resource-manager-agent.md
Title: Resource Manager template samples for agents description: Sample Azure Resource Manager templates to deploy and configure virtual machine agents in Azure Monitor. + Last updated 04/26/2022 - # Resource Manager template samples for agents in Azure Monitor
azure-monitor Resource Manager Data Collection Rules https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/agents/resource-manager-data-collection-rules.md
Title: Resource Manager template samples for data collection rules description: Sample Azure Resource Manager templates to create associations between data collection rules and virtual machines in Azure Monitor. + Last updated 06/22/2022- # Resource Manager template samples for data collection rules in Azure Monitor
azure-monitor Alerts Create New Alert Rule https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/alerts-create-new-alert-rule.md
description: This article shows you how to create a new alert rule.
-+ Last updated 03/05/2023
azure-monitor Alerts Manage Alert Rules https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/alerts-manage-alert-rules.md
description: Manage your alert rules in the Azure portal, or using the CLI or Po
+ Last updated 03/05/2023
Activity log alerts have these dedicated PowerShell cmdlets:
## Next steps - [Learn about Azure Monitor alerts](./alerts-overview.md)-- [Create a new alert rule](alerts-log.md)
+- [Create a new alert rule](alerts-log.md)
azure-monitor Alerts Troubleshoot Metric https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/alerts-troubleshoot-metric.md
Title: Frequently asked questions about Azure Monitor metric alerts description: Common issues with Azure Monitor metric alerts and possible solutions. + Last updated 8/31/2022 ms:reviwer: harelbr
azure-monitor Proactive Arm Config https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/proactive-arm-config.md
Title: Smart detection rule settings - Azure Application Insights description: Automate management and configuration of Azure Application Insights smart detection rules with Azure Resource Manager Templates + Last updated 02/14/2021
Learn more about automatically detecting:
- [Failure anomalies](./proactive-failure-diagnostics.md) - [Memory Leaks](./proactive-potential-memory-leak.md)-- [Performance anomalies](./smart-detection-performance.md)
+- [Performance anomalies](./smart-detection-performance.md)
azure-monitor Resource Manager Action Groups https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/resource-manager-action-groups.md
Title: Resource Manager template samples for action groups description: Sample Azure Resource Manager templates to deploy Azure Monitor action groups. + Last updated 04/27/2022 - # Resource Manager template samples for action groups in Azure Monitor
azure-monitor Resource Manager Alerts Activity Log https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/resource-manager-alerts-activity-log.md
Title: Resource Manager template samples for activity log alerts description: Sample Azure Resource Manager templates to deploy Azure Monitor activity log alerts. + Last updated 12/28/2022
azure-monitor Resource Manager Alerts Log https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/resource-manager-alerts-log.md
Title: Resource Manager template samples for log query alerts description: Sample Azure Resource Manager templates to deploy Azure Monitor log query alerts. + Last updated 05/11/2022- # Resource Manager template samples for log alert rules in Azure Monitor
azure-monitor Resource Manager Alerts Resource Health https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/resource-manager-alerts-resource-health.md
Title: Resource Manager template samples for resource health alerts description: Sample Azure Resource Manager templates to deploy Azure Monitor resource health alerts. + Last updated 05/11/2022- # Resource Manager template samples for resource health alert rules in Azure Monitor
azure-monitor Annotations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/app/annotations.md
Title: Release annotations for Application Insights | Microsoft Docs description: Learn how to create annotations to track deployment or other significant events with Application Insights. + Last updated 01/24/2023 - # Release annotations for Application Insights
azure-monitor Availability Azure Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/app/availability-azure-functions.md
Last updated 04/06/2023
# Review TrackAvailability() test results
-This article explains how to review TrackAvailability() test results in the Azure portal and query the data using Log Analytics.
+This article explains how to review [TrackAvailability()](/dotnet/api/microsoft.applicationinsights.telemetryclient.trackavailability) test results in the Azure portal and query the data using [Log Analytics](../logs/log-analytics-overview.md#overview-of-log-analytics-in-azure-monitor).
+ ## Prerequisites > [!div class="checklist"]
-> - [Azure subscription](https://azure.microsoft.com/free) and user account with the ability to create and delete resources
> - [Workspace-based Application Insights resource](create-workspace-resource.md) > - Custom [Azure Functions app](../../azure-functions/functions-overview.md#introduction-to-azure-functions) running [TrackAvailability()](/dotnet/api/microsoft.applicationinsights.telemetryclient.trackavailability) with your own business logic
azure-monitor Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/app/powershell.md
Title: Automate Application Insights with PowerShell | Microsoft Docs
description: Automate creating and managing resources, alerts, and availability tests in PowerShell by using an Azure Resource Manager template. Last updated 03/22/2023-+
azure-monitor Resource Manager App Resource https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/app/resource-manager-app-resource.md
Title: Resource Manager template samples for Application Insights resources
description: Sample Azure Resource Manager templates to deploy Application Insights resources in Azure Monitor. Last updated 11/14/2022-+
azure-monitor Autoscale Predictive https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/autoscale/autoscale-predictive.md
Last updated 10/12/2022-+ # Use predictive autoscale to scale out before load demands in virtual machine scale sets
azure-monitor Container Insights Cost Config https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/containers/container-insights-cost-config.md
Title: Configure Container insights cost optimization data collection rules | Microsoft Docs description: This article describes how you can configure the Container insights agent to control data collection for metric counters + Last updated 02/23/2023
azure-monitor Container Insights Enable Aks Policy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/containers/container-insights-enable-aks-policy.md
Title: Enable the AKS Monitoring Add-on by using Azure Policy description: This article describes how to enable the AKS Monitoring Add-on by using a custom Azure policy. + Last updated 08/29/2022
azure-monitor Container Insights Optout Openshift V3 https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/containers/container-insights-optout-openshift-v3.md
Title: How to stop monitoring your Azure Red Hat OpenShift v3 cluster | Microsoft Docs description: This article describes how you can stop monitoring of your Azure Red Hat OpenShift cluster with Container insights. + Last updated 05/24/2022
azure-monitor Container Insights Optout https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/containers/container-insights-optout.md
Title: Stop monitoring your Azure Kubernetes Service cluster | Microsoft Docs
description: This article describes how you can discontinue monitoring of your Azure AKS cluster with Container insights. Last updated 05/24/2022-+ ms.devlang: azurecli
azure-monitor Resource Manager Container Insights https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/containers/resource-manager-container-insights.md
Title: Resource Manager template samples for Container insights description: Sample Azure Resource Manager templates to deploy and configureContainer insights. + Last updated 05/05/2022 - # Resource Manager template samples for Container insights
resource aroResourceId_8 'Microsoft.ContainerService/openShiftManagedClusters@20
## Next steps * [Get other sample templates for Azure Monitor](../resource-manager-samples.md).
-* [Learn more about Container insights](../containers/container-insights-overview.md).
+* [Learn more about Container insights](../containers/container-insights-overview.md).
azure-monitor Collect Custom Metrics Guestos Resource Manager Vm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/essentials/collect-custom-metrics-guestos-resource-manager-vm.md
+ Last updated 05/04/2020
azure-monitor Collect Custom Metrics Guestos Resource Manager Vmss https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/essentials/collect-custom-metrics-guestos-resource-manager-vmss.md
description: Send guest OS metrics to the Azure Monitor metric store by using a
+ Last updated 09/09/2019 # Send guest OS metrics to the Azure Monitor metric store by using an Azure Resource Manager template for a Windows virtual machine scale set
You can then also choose to use the dimensions on this metric to chart it for a
## Next steps-- Learn more about [custom metrics](./metrics-custom-overview.md).
+- Learn more about [custom metrics](./metrics-custom-overview.md).
azure-monitor Metrics Store Custom Rest Api https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/essentials/metrics-store-custom-rest-api.md
Save the access token from the response for use in the following HTTP requests.
- **accessToken**: The authorization token acquired from the previous step. ```Shell
- curl -X POST 'https://<location>.monitoring.azure.com/<resourceId>/metrics' \
+ curl -X POST 'https://<location>.monitoring.azure.com<resourceId>/metrics' \
-H 'Content-Type: application/json' \ -H 'Authorization: Bearer <accessToken>' \ -d @custommetric.json
azure-monitor Resource Manager Diagnostic Settings https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/essentials/resource-manager-diagnostic-settings.md
Title: Resource Manager template samples for diagnostic settings description: Sample Azure Resource Manager templates to apply Azure Monitor diagnostic settings to an Azure resource. + Last updated 06/13/2022 - # Resource Manager template samples for diagnostic settings in Azure Monitor
azure-monitor Resource Manager Sql Insights https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/insights/resource-manager-sql-insights.md
Title: Resource Manager template samples for SQL Insights (preview) description: Sample Azure Resource Manager templates to deploy and configure SQL Insights (preview). + Last updated 03/25/2021- # Resource Manager template samples for SQL Insights (preview)
View the [parameter file on git hub](https://github.com/microsoft/Application-In
## Next steps * [Get other sample templates for Azure Monitor](../resource-manager-samples.md).
-* [Learn more about SQL Insights (preview)](/azure/azure-sql/database/sql-insights-overview).
+* [Learn more about SQL Insights (preview)](/azure/azure-sql/database/sql-insights-overview).
azure-monitor Move Workspace Region https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/move-workspace-region.md
Title: Move a Log Analytics workspace to another Azure region by using the Azure portal description: Use an Azure Resource Manager template to move a Log Analytics workspace from one Azure region to another by using the Azure portal. + Last updated 08/17/2021
azure-monitor Resource Manager Cluster https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/resource-manager-cluster.md
Title: Resource Manager template samples for Log Analytics clusters description: Sample Azure Resource Manager templates to deploy Log Analytics clusters. + Last updated 06/13/2022- # Resource Manager template samples for Log Analytics clusters in Azure Monitor
azure-monitor Resource Manager Log Queries https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/resource-manager-log-queries.md
Title: Resource Manager template samples for log queries description: Sample Azure Resource Manager templates to deploy Azure Monitor log queries. + Last updated 06/13/2022- # Resource Manager template samples for log queries in Azure Monitor
resource queryUsingFunctionSavedSearch 'Microsoft.OperationalInsights/workspaces
- [Get other sample templates for Azure Monitor](../resource-manager-samples.md). - [Learn more about log queries](../logs/log-query-overview.md).-- [Learn more about functions](../logs/functions.md).
+- [Learn more about functions](../logs/functions.md).
azure-monitor Resource Manager Workspace https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/resource-manager-workspace.md
Title: Resource Manager template samples for Log Analytics workspaces description: Sample Azure Resource Manager templates to deploy Log Analytics workspaces and configure data sources in Azure Monitor. + Last updated 06/23/2022
azure-monitor Tutorial Logs Ingestion Api https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/tutorial-logs-ingestion-api.md
Title: 'Tutorial: Send data to Azure Monitor Logs with Logs ingestion API (Resource Manager templates)' description: Tutorial on how sending data to a Log Analytics workspace in Azure Monitor using the Logs ingestion API. Supporting components configured using Resource Manager templates. + Last updated 03/20/2023
azure-monitor Resource Graph Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/resource-graph-samples.md
Title: Azure Resource Graph sample queries for Azure Monitor
-description: Sample Azure Resource Graph queries for Azure Monitor showing use of resource types and tables to access Azure Monitor related resources and properties.
+description: Sample Azure Resource Graph queries for Azure Monitor showing the use of resource types and tables to access Azure Monitor-related resources and properties.
Last updated 07/07/2022
# Azure Resource Graph sample queries for Azure Monitor This page is a collection of [Azure Resource Graph](../governance/resource-graph/overview.md) sample queries
-for Azure Monitor. For a complete list of Azure Resource Graph samples, see
-[Resource Graph samples by Category](../governance/resource-graph/samples/samples-by-category.md) and
-[Resource Graph samples by Table](../governance/resource-graph/samples/samples-by-table.md).
+for Azure Monitor. For a complete list of Azure Resource Graph samples, see:
+- [Resource Graph samples by category](../governance/resource-graph/samples/samples-by-category.md)
+- [Resource Graph samples by table](../governance/resource-graph/samples/samples-by-table.md)
## Azure Monitor
for Azure Monitor. For a complete list of Azure Resource Graph samples, see
- Learn more about the [query language](../governance/resource-graph/concepts/query-language.md). - Learn more about how to [explore resources](../governance/resource-graph/concepts/explore-resources.md).-- See samples of [Starter language queries](../governance/resource-graph/samples/starter.md).-- See samples of [Advanced language queries](../governance/resource-graph/samples/advanced.md).
+- See samples of [starter language queries](../governance/resource-graph/samples/starter.md).
+- See samples of [advanced language queries](../governance/resource-graph/samples/advanced.md).
azure-monitor Snapshot Debugger App Service https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/snapshot-debugger/snapshot-debugger-app-service.md
reviewer: cweining Last updated 01/24/2023-+ # Enable Snapshot Debugger for .NET apps in Azure App Service
azure-monitor Terminology https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/terminology.md
Title: Azure Monitor terminology updates | Microsoft Docs
-description: Describes recent terminology changes made to Azure monitoring services.
+description: This article describes terminology changes made to Azure monitoring services.
# Azure Monitor naming and terminology changes
-Significant changes have been made to Azure Monitor recently, with different services being consolidated in order to simplify monitoring for Azure customers. This article describes recent name and terminology changes in Azure Monitor documentation.
+In Azure Monitor, different services were consolidated to simplify monitoring for Azure customers. This article describes name and terminology changes in Azure Monitor documentation.
-## October 2019 - Diagnostic Log to Resource Log
-"Diagnostic logs" were changed to "resource logs" to better match what is actually being collected. The term "diagnostic settings" remains the same.
+## October 2019: Diagnostic log to resource log
+"Diagnostic logs" changed to "resource logs" to better match what's actually being collected. The term "diagnostic settings" remains the same.
-## February 2019 - Log Analytics terminology
-After the consolidation of different services under Azure Monitor, we're taking the next step by modifying terminology in our documentation to better describe the Azure Monitor service and its different components.
+## February 2019: Log Analytics terminology
+After the consolidation of different services under Azure Monitor, we modified the terminology. Now the documentation better describes the Azure Monitor service and its different components.
### Log Analytics
-Azure Monitor log data is still stored in a Log Analytics workspace and is still collected and analyzed by the same Log Analytics service, but we are changing the term _Log Analytics_ in many places to _Azure Monitor logs_. This term better reflects its role in Azure Monitor and provides better consistency with [metrics in Azure Monitor](essentials/data-platform-metrics.md).
+Azure Monitor log data is still stored in a Log Analytics workspace and is still collected and analyzed by the same Log Analytics service. We changed the term _Log Analytics_ in many places to _Azure Monitor logs_. This term better reflects its role in Azure Monitor. It also provides better consistency with [metrics in Azure Monitor](essentials/data-platform-metrics.md).
-The term _log analytics_ now primarily applies to the page in the Azure portal used to write and run queries and analyze log data. It's the functional equivalent of [metrics explorer](essentials/metrics-charts.md), which is the page in the Azure portal used to analyze metric data.
+The term _log analytics_ now primarily applies to the page in the Azure portal that's used to write and run queries and analyze log data. It's the functional equivalent of [metrics explorer](essentials/metrics-charts.md), which is the page in the Azure portal used to analyze metric data.
### Log Analytics workspaces
-[Workspaces](logs/manage-access.md) that hold log data in Azure Monitor are still referred to as Log Analytics workspaces. The **Log Analytics** menu in the Azure portal has been renamed to **Log Analytics workspaces** and is where you [create new workspaces](logs/quick-create-workspace.md) and configure data sources. Analyze your logs and other monitoring data in **Azure Monitor** and configure your workspace in **Log Analytics workspaces**.
+[Workspaces](logs/manage-access.md) that hold log data in Azure Monitor are still referred to as Log Analytics workspaces. The **Log Analytics** menu in the Azure portal was renamed to **Log Analytics workspaces**. It's where you [create new workspaces](logs/quick-create-workspace.md) and configure data sources. You analyze your logs and other monitoring data in **Azure Monitor** and configure your workspace in **Log Analytics workspaces**.
### Management solutions
-[Management solutions](/previous-versions/azure/azure-monitor/insights/solutions) have been renamed to _monitoring solutions_, which better describes their functionality.
+[Management solutions](/previous-versions/azure/azure-monitor/insights/solutions) were renamed to _monitoring solutions_, which better describes their functionality.
+## August 2018: Consolidation of monitoring services into Azure Monitor
+Log Analytics and Application Insights were consolidated into Azure Monitor to provide a single integrated experience for monitoring Azure resources and hybrid environments. No functionality was removed from these services. You can perform the same scenarios with no loss or compromise of any features.
-## August 2018 - Consolidation of monitoring services into Azure Monitor
-Log Analytics and Application Insights have been consolidated into Azure Monitor to provide a single integrated experience for monitoring Azure resources and hybrid environments. No functionality has been removed from these services, and users can perform the same scenarios that they've always completed with no loss or compromise of any features.
+Documentation for each of these services was consolidated into a single set of content for Azure Monitor. Now you can find all the content for a particular monitoring scenario in a single location instead of having to use multiple sets of content. As the consolidated service evolves, the content will become more integrated.
-Documentation for each of these services has been consolidated into a single set of content for Azure Monitor. This will assist the reader in finding all of the content for a particular monitoring scenario in a single location as opposed to having to reference multiple sets of content. As the consolidated service evolves, the content will become more integrated.
+Other features that were considered part of Log Analytics, such as agents and views, were also repositioned as features of Azure Monitor. Their functionality hasn't changed other than potential improvements to their experience in the Azure portal.
-Other features that were considered part of Log Analytics such as agents and views have also been repositioned as features of Azure Monitor. Their functionality hasn't changed other than potential improvements to their experience in the Azure portal.
--
-## April 2018 - Retirement of Operations Management Suite brand
-Operations Management Suite (OMS) was a bundling of the following Azure management services for licensing purposes:
+## April 2018: Retirement of Operations Management Suite brand
+Operations Management Suite (OMS) bundled the following Azure management services for licensing purposes:
- Application Insights - Azure Automation - Azure Backup - Log Analytics-- Site Recovery
+- Azure Site Recovery
-[New pricing has been introduced for these services](https://azure.microsoft.com/blog/introducing-a-new-way-to-purchase-azure-monitoring-services/), and the OMS bundling is no longer available for new customers. None of the services that were part of OMS have changed, except for the consolidation into Azure Monitor described above. The OMS portal was retired and is no longer available.
+[New pricing was introduced for these services](https://azure.microsoft.com/blog/introducing-a-new-way-to-purchase-azure-monitoring-services/). The OMS bundling is no longer available for new customers. None of the services that were part of OMS have changed, except for the consolidation into Azure Monitor as described. The OMS portal was retired and is no longer available.
## Next steps -- Read an [overview of Azure Monitor](overview.md) that describes its different components and features.
+Read an [overview of Azure Monitor](overview.md) that describes its different components and features.
azure-monitor Resource Manager Workbooks https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/visualize/resource-manager-workbooks.md
Title: Resource Manager template samples for workbooks description: Sample Azure Resource Manager templates to deploy Azure Monitor workbooks. + Last updated 06/13/2022- # Resource Manager template samples for workbooks in Azure Monitor
output workbookId string = workbook.id
## Next steps * [Get other sample templates for Azure Monitor](../resource-manager-samples.md).
-* [Learn more about action groups](../visualize/workbooks-overview.md).
+* [Learn more about action groups](../visualize/workbooks-overview.md).
azure-monitor Workbooks Automate https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/visualize/workbooks-automate.md
description: Simplify complex reporting with prebuilt and custom parameterized A
ibiza+ Last updated 07/05/2022
Currently, this mechanism can't be used to create workbook instances in the **Wo
## Next steps
-Explore how workbooks are being used to power the new [Storage insights experience](../../storage/common/storage-insights-overview.md?toc=%2fazure%2fazure-monitor%2ftoc.json).
+Explore how workbooks are being used to power the new [Storage insights experience](../../storage/common/storage-insights-overview.md?toc=%2fazure%2fazure-monitor%2ftoc.json).
azure-monitor Workbooks Commonly Used Components https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/visualize/workbooks-commonly-used-components.md
+ Last updated 07/05/2022
azure-monitor Workbooks Data Sources https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/visualize/workbooks-data-sources.md
+ Last updated 07/05/2022
azure-monitor Workbooks Link Actions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/visualize/workbooks-link-actions.md
Title: Azure Workbooks link actions description: This article explains how to use link actions in Azure Workbooks. + Last updated 07/05/2022
azure-monitor Workbooks Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/visualize/workbooks-samples.md
+ Last updated 07/05/2022
This article includes sample Azure Workbooks.
], "$schema": "https://github.com/Microsoft/Application-Insights-Workbooks/blob/master/schema/workbook.json" }
-```
+```
azure-monitor Resource Manager Vminsights https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/vm/resource-manager-vminsights.md
Title: Resource Manager template samples for VM insights description: Sample Azure Resource Manager templates to deploy and configureVM insights. + Last updated 06/13/2022- # Resource Manager template samples for VM insights
azure-monitor Vminsights Enable Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/vm/vminsights-enable-powershell.md
Title: Enable VM insights by using PowerShell description: This article describes how to enable VM insights for Azure virtual machines or virtual machine scale sets by using Azure PowerShell. + Last updated 06/08/2022- # Enable VM insights by using PowerShell
azure-monitor Vminsights Enable Resource Manager https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/vm/vminsights-enable-resource-manager.md
Title: Enable VM insights using Resource Manager templates description: This article describes how you enable VM insights for one or more Azure virtual machines or Virtual Machine Scale Sets by using Azure PowerShell or Azure Resource Manager templates. + Last updated 06/08/2022- # Enable VM insights using Resource Manager templates
Now that monitoring is enabled for your virtual machines, this information is av
- To view discovered application dependencies, see [View VM insights Map](vminsights-maps.md). -- To identify bottlenecks and overall utilization with your VM's performance, see [View Azure VM Performance](vminsights-performance.md).
+- To identify bottlenecks and overall utilization with your VM's performance, see [View Azure VM Performance](vminsights-performance.md).
azure-monitor Whats New https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/whats-new.md
This article lists significant changes to Azure Monitor documentation.
|Subservice| Article | Description | |||| Alerts|[Manage your alert rules](alerts/alerts-manage-alert-rules.md)|Updated article to reflect that the user can duplicate an existing alert rule.|
-Alerts|[Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Azure portal](../aks/learn/quick-kubernetes-deploy-portal.md)|You can enable recommended alert rules while creating an AKS cluster in the Azure portal. |
-Alerts|[Monitor Log Analytics workspace health](logs/log-analytics-workspace-health.md)|If you have a Log Analytics workspace without any configured alert rules, you can enable recommended alert rules from the Alerts page of a Log Analytics Workspace.|
-Alerts|[Connect Azure to ITSM tools by using IT Service Management](alerts/itsmc-definition.md)|Updated the workflow for creating ServieNow ITSM tickets from an Azure Monitor alert. The article now specifies separate workflows for ITSM actions, incidents, and events.|
-Alerts|[Manage your alert rules](alerts/alerts-manage-alert-rules.md)|Recommended alert rules are now enabled for all customers and are no longer public preview.|
-Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|The documentation was updated to reflect the updated "Create new alert rule" UI. The alert rule creation wizard clearly indicates the most commonly used resources and signals for their alerts to help users more easily create alert rules.|
-Alerts|[Understanding Azure Active Directory Application Proxy Complex application scenario (Preview)](../active-directory/app-proxy/application-proxy-configure-complex-application.md)|The documentation for the common schema used in the alerts payload has been updated to contain the detailed information about the fields in the payload of each alert type. |
+Alerts|[Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster by using the Azure portal](../aks/learn/quick-kubernetes-deploy-portal.md)|You can enable recommended alert rules when you create an AKS cluster in the Azure portal. |
+Alerts|[Monitor Log Analytics workspace health](logs/log-analytics-workspace-health.md)|If you have a Log Analytics workspace without any configured alert rules, you can enable recommended alert rules from the **Alerts** page of a Log Analytics workspace.|
+Alerts|[Connect Azure to ITSM tools by using IT Service Management](alerts/itsmc-definition.md)|Updated the workflow for creating ServiceNow ITSM tickets from an Azure Monitor alert. The article now specifies separate workflows for ITSM actions, incidents, and events.|
+Alerts|[Manage your alert rules](alerts/alerts-manage-alert-rules.md)|Recommended alert rules are now enabled for all customers and are no longer in public preview.|
+Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|Updated to reflect the updated **Create new alert rule** UI. The alert rule creation wizard clearly indicates the most commonly used resources and signals for their alerts to help users more easily create alert rules.|
+Alerts|[Understanding Azure Active Directory Application Proxy Complex application scenario (preview)](../active-directory/app-proxy/application-proxy-configure-complex-application.md)| Updated the documentation for the common schema used in the alerts payload to contain the detailed information about the fields in the payload of each alert type. |
Alerts|[Supported resources for metric alerts in Azure Monitor](alerts/alerts-metric-near-real-time.md)|Updated list of metrics supported by metric alert rules.| Alerts|[Create and manage action groups in the Azure portal](alerts/action-groups.md)|Updated the documentation explaining the retry logic used in action groups that use webhooks.| Alerts|[Create and manage action groups in the Azure portal](alerts/action-groups.md)|Added list of countries supported by voice notifications.| Alerts|[Connect ServiceNow to Azure Monitor](alerts/itsmc-secure-webhook-connections-servicenow.md)|Added Tokyo to list of supported ServiceNow webhook integrations.| Application-Insights|[Application Insights SDK support guidance](app/sdk-support-guidance.md)|Release notes are now available for each SDK.|
-Application-Insights|[What is distributed tracing and telemetry correlation?](app/distributed-tracing-telemetry-correlation.md)|We've merged our documents related to distributed tracing and telemetry correlation.|
-Application-Insights|[Application Insights availability tests](app/availability-overview.md)|We've separated and called out the two Classic Tests, which are older versions of availability tests.|
+Application-Insights|[What is distributed tracing and telemetry correlation?](app/distributed-tracing-telemetry-correlation.md)|Merged our documents related to distributed tracing and telemetry correlation.|
+Application-Insights|[Application Insights availability tests](app/availability-overview.md)|Separated and called out the two Classic Tests, which are older versions of availability tests.|
Application-Insights|[Microsoft Azure Monitor Application Insights JavaScript SDK advanced topics](app/javascript-sdk-advanced.md)|JavaScript SDK advanced topics now include npm setup, cookie configuration and management, source map un-minify support, and tree shaking optimized code.|
-Application-Insights|[Microsoft Azure Monitor Application Insights JavaScript SDK](app/javascript-sdk.md)|Our introductory article to the JavaScript SDK now provides only the fast and easy code snippet method of getting started.|
-Application-Insights|[Geolocation and IP address handling](app/ip-collection.md)|Code samples have been updated for .NET 6/7.|
-Application-Insights|[Application Insights logging with .NET](app/ilogger.md)|Code samples have been updated for .NET 6/7.|
-Application-Insights|[Azure Monitor overview](overview.md)|Azure Monitor overview graphics updated along with related content|
+Application-Insights|[Microsoft Azure Monitor Application Insights JavaScript SDK](app/javascript-sdk.md)|Our introductory article to the JavaScript SDK now provides only the fast and easy code-snippet method of getting started.|
+Application-Insights|[Geolocation and IP address handling](app/ip-collection.md)|Updated code samples for .NET 6/7.|
+Application-Insights|[Application Insights logging with .NET](app/ilogger.md)|Updated code samples for .NET 6/7.|
+Application-Insights|[Azure Monitor overview](overview.md)|Updated Azure Monitor overview graphics along with related content.|
Containers|[Metric alert rules in Container insights (preview)](containers/container-insights-metric-alerts.md)|Updated to indicate deprecation of metric alerts.|
-Containers|[Azure Monitor Container Insights for Azure Arc-enabled Kubernetes clusters](containers/container-insights-enable-arc-enabled-clusters.md)|Added option for Azure Monitor Private Link Scope (AMPLS) + Proxy.|
-Essentials|[Collect Prometheus metrics from an AKS cluster (preview)](essentials/prometheus-metrics-enable.md)|Enable windows metric collection metrics addon|
-Essentials|[Query Prometheus metrics using the API and PromQL](essentials/prometheus-api-promql.md)|New Article: Query Azure Monitor workspaces using REST and PromQL|
-Essentials|[Configure remote write for Azure Monitor managed service for Prometheus using Azure Active Directory authentication (preview)](essentials/prometheus-remote-write-active-directory.md)|Added Prometheus remote write active directory relabel|
-Essentials|[Built-in policies for Azure Monitor](essentials/diagnostics-settings-policies-deployifnotexists.md)|New builtin polices to create diagnostic settings in Azure Monitor with deploy if not exits defaults|
+Containers|[Azure Monitor Container insights for Azure Arc-enabled Kubernetes clusters](containers/container-insights-enable-arc-enabled-clusters.md)|Added option for Azure Monitor Private Link Scope (AMPLS) + Proxy.|
+Essentials|[Collect Prometheus metrics from an AKS cluster (preview)](essentials/prometheus-metrics-enable.md)|Enabled Windows metric collection metrics add-on.|
+Essentials|[Query Prometheus metrics by using the API and PromQL](essentials/prometheus-api-promql.md)|New article: Query Azure Monitor workspaces by using REST and PromQL.|
+Essentials|[Configure remote write for Azure Monitor managed service for Prometheus by using Azure Active Directory authentication (preview)](essentials/prometheus-remote-write-active-directory.md)|Added Prometheus remote write Active Directory relabel.|
+Essentials|[Built-in policies for Azure Monitor](essentials/diagnostics-settings-policies-deployifnotexists.md)|Added new built-in policies to create diagnostic settings in Azure Monitor with deploy-if-not-exists defaults.|
Logs|[Logs Ingestion API in Azure Monitor](logs/logs-ingestion-api-overview.md)|Updated to include client libraries.|
-Logs|[Tutorial: Send data to Azure Monitor using Logs ingestion API (Resource Manager templates)](logs/tutorial-logs-ingestion-api.md)|Rewritten to be more consistent with related tutorial.|
-Logs|[Sample code to send data to Azure Monitor using Logs ingestion API](logs/tutorial-logs-ingestion-code.md)|New article with sample code using Logs ingestion API, including new client ingestion libraries for Python, .NET, Java, and JavaScript.|
-Logs|[Tutorial: Send data to Azure Monitor Logs with Logs ingestion API (Azure portal)](logs/tutorial-logs-ingestion-portal.md)|Rewritten to be more consistent with related tutorial.|
-Snapshot-Debugger|[Enable Profiler for ASP.NET Core web applications hosted in Linux on App Services](profiler/profiler-aspnetcore-linux.md)|Update code snippets from .NET 5 to .NET 6|
-Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure Service Fabric, Cloud Service, and Virtual Machines](snapshot-debugger/snapshot-debugger-vm.md)|Update code snippets from .NET 5 to .NET 6|
+Logs|[Tutorial: Send data to Azure Monitor by using the Logs Ingestion API (Azure Resource Manager templates)](logs/tutorial-logs-ingestion-api.md)|Rewritten to be more consistent with related tutorial.|
+Logs|[Sample code to send data to Azure Monitor by using the Logs Ingestion API](logs/tutorial-logs-ingestion-code.md)|New article: Sample code to send data by using the Logs Ingestion API, including new client ingestion libraries for Python, .NET, Java, and JavaScript.|
+Logs|[Tutorial: Send data to Azure Monitor Logs with the Logs Ingestion API (Azure portal)](logs/tutorial-logs-ingestion-portal.md)|Rewritten to be more consistent with related tutorial.|
+Snapshot-Debugger|[Enable Profiler for ASP.NET Core web applications hosted in Linux on Azure App Service](profiler/profiler-aspnetcore-linux.md)|Updated code snippets from .NET 5 to .NET 6.|
+Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure Service Fabric, Azure Cloud Services, and Azure Virtual Machines](snapshot-debugger/snapshot-debugger-vm.md)|Updated code snippets from .NET 5 to .NET 6.|
-
-## February 2023
-
|Subservice| Article | Description | ||||
-Agents|[Azure Monitor agent extension versions](agents/azure-monitor-agent-extension-versions.md)|Added release notes for the Azure Monitor Agent Linux 1.25 release.|
-Agents|[Migrate to Azure Monitor Agent from Log Analytics agent](agents/azure-monitor-agent-migration.md)|Updated guidance for migrating from Log Analytics Agent to Azure Monitor Agent.|
-Alerts|[Manage your alert rules](alerts/alerts-manage-alert-rules.md)|Included limitation and workaround for resource health alerts. If you apply a target resource type scope filter to the alerts rules page, the alerts rules list doesnΓÇÖt include resource health alert rules.|
-Alerts|[Customize alert notifications by using Logic Apps](alerts/alerts-logic-apps.md)|Added instructions for additional customizations that you can include when using Logic Apps to create alert notifications. You can extracting information about the affected resource from resource's tags, and then include the resource tags in the alert payload and use the information in your logical expressions used for creating the notifications.|
+Agents|[Azure Monitor Agent extension versions](agents/azure-monitor-agent-extension-versions.md)|Added release notes for the Azure Monitor Agent Linux 1.25 release.|
+Agents|[Migrate to Azure Monitor Agent from the Log Analytics agent](agents/azure-monitor-agent-migration.md)|Updated guidance for migrating from Log Analytics agent to Azure Monitor Agent.|
+Alerts|[Manage your alert rules](alerts/alerts-manage-alert-rules.md)|Included limitation and workaround for resource health alerts. If you apply a target resource type scope filter to the **Alerts rules** page, the alerts rules list doesnΓÇÖt include resource health alert rules.|
+Alerts|[Customize alert notifications by using Azure Logic Apps](alerts/alerts-logic-apps.md)|Added instructions for other customizations that you can include when you use Logic Apps to create alert notifications. You can extract information about the affected resource from the resource's tags. Then you can include the resource tags in the alert payload and use the information in your logical expressions that are used for creating the notifications.|
Alerts|[Create and manage action groups in the Azure portal](alerts/action-groups-create-resource-manager-template.md)|Combined two articles about creating action groups into one article.| Alerts|[Create and manage action groups in the Azure portal](alerts/action-groups.md)|Clarified that you can't pass security certificates in a webhook action in action groups.|
-Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|Add information about adding custom properties to the alert payload when you use action groups.|
-Alerts|[Manage your alert instances](alerts/alerts-manage-alert-instances.md)|Removed option for managing alert instances using the CLI.|
-Application-Insights|[Migrate to workspace-based Application Insights resources](app/convert-classic-resource.md)|The continuous export deprecation notice has been added to this article for more visibility. It's recommended to migrate to workspace-based Application Insights resources as soon as possible to take advantage of new features.|
-Application-Insights|[Application Insights API for custom events and metrics](app/api-custom-events-metrics.md)|Client-side JavaScript SDK extensions have been consolidated into two new articles called "Framework extensions" and "Feature Extensions". We've additionally created new stand-alone Upgrade and Troubleshooting articles.|
-Application-Insights|[Monitor Azure Functions with Azure Monitor Application Insights](app/monitor-functions.md)|We've overhauled our documentation on Azure Functions integration with Application Insights.|
-Application-Insights|[Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python and Java applications](app/opentelemetry-enable.md)|Java OpenTelemetry examples have been updated.|
-Application-Insights|[Application Monitoring for Azure App Service and Java](app/azure-web-apps-java.md)|We updated and separated out the instructions to manually deploy the latest Application Insights Java version.|
-Containers|[Enable Container insights for Azure Kubernetes Service (AKS) cluster](containers/container-insights-enable-aks.md)|Added section for enabling private link without managed identity authentication.|
-Containers|[Syslog collection with Container Insights (preview)](containers/container-insights-syslog.md)|Added use of ARM templates for enabling syslog collection|
-Containers|[Enable cost optimization settings (preview)](containers/container-insights-cost-config.md)|New Article: Enable cost optimization settings|
+Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|Added information about adding custom properties to the alert payload when you use action groups.|
+Alerts|[Manage your alert instances](alerts/alerts-manage-alert-instances.md)|Removed option for managing alert instances by using the Azure CLI.|
+Application-Insights|[Migrate to workspace-based Application Insights resources](app/convert-classic-resource.md)|Added the continuous export deprecation notice to this article for more visibility. We recommend migrating to workspace-based Application Insights resources as soon as possible to take advantage of new features.|
+Application-Insights|[Application Insights API for custom events and metrics](app/api-custom-events-metrics.md)|Consolidated client-side JavaScript SDK extensions into two new articles called *Framework extensions* and *Feature extensions*. We've also created new standalone *Upgrade* and *Troubleshooting* articles.|
+Application-Insights|[Monitor Azure Functions with Azure Monitor Application Insights](app/monitor-functions.md)|Overhauled the documentation on Azure Functions integration with Application Insights.|
+Application-Insights|[Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python, and Java applications](app/opentelemetry-enable.md)|Updated Java OpenTelemetry examples.|
+Application-Insights|[Application monitoring for Azure App Service and Java](app/azure-web-apps-java.md)|Updated and separated out the instructions to manually deploy the latest Application Insights Java version.|
+Containers|[Enable Container insights for Azure Kubernetes Service (AKS) clusters](containers/container-insights-enable-aks.md)|Added a section for enabling a private link without managed identity authentication.|
+Containers|[Syslog collection with Container insights (preview)](containers/container-insights-syslog.md)|Added use of Azure Resource Manager templates for enabling Syslog collection.|
+Containers|[Enable cost-optimization settings (preview)](containers/container-insights-cost-config.md)|New article: Enable cost-optimization settings.|
Essentials|[Data collection transformations in Azure Monitor](essentials/data-collection-transformations.md)|Added section and sample for using transformations to send to multiple destinations.|
-Essentials|[Custom metrics in Azure Monitor (preview)](essentials/metrics-custom-overview.md)|Added reference to the limit of 64 KB on the combined length of all custom metrics names|
-Essentials|[Azure monitoring REST API walkthrough](essentials/rest-api-walkthrough.md)|Refresh REST API walkthrough|
-Essentials|[Collect Prometheus metrics from AKS cluster (preview)](essentials/prometheus-metrics-enable.md)|Added Enabling Prometheus metric collection using Azure policy and Bicep|
-Essentials|[Send Prometheus metrics to multiple Azure Monitor workspaces (preview)](essentials/prometheus-metrics-multiple-workspaces.md)|Updated sending metrics to multiple Azure Monitor workspaces|
-General|[Analyzing and visualize data](best-practices-analysis.md)|Revised the article about analyzing and visualizing monitoring data to provide a comparison of the different visualization tools and guide customers when they would choose each tool for their implementation. |
-Logs|[Tutorial: Send data to Azure Monitor Logs using REST API (Resource Manager templates)](logs/tutorial-logs-ingestion-api.md)|Minor fixes and updated sample data.|
+Essentials|[Custom metrics in Azure Monitor (preview)](essentials/metrics-custom-overview.md)|Added reference to the limit of 64 KB on the combined length of all custom metrics names.|
+Essentials|[Azure monitoring REST API walkthrough](essentials/rest-api-walkthrough.md)|Refreshed REST API walkthrough.|
+Essentials|[Collect Prometheus metrics from AKS cluster (preview)](essentials/prometheus-metrics-enable.md)|Added enabling Prometheus metric collection by using Azure Policy and Bicep.|
+Essentials|[Send Prometheus metrics to multiple Azure Monitor workspaces (preview)](essentials/prometheus-metrics-multiple-workspaces.md)|Updated sending metrics to multiple Azure Monitor workspaces.|
+General|[Analyze and visualize data](best-practices-analysis.md)|Revised the article about analyzing and visualizing monitoring data to provide a comparison of the different visualization tools and guide customers on when to choose each tool for their implementation. |
+Logs|[Tutorial: Send data to Azure Monitor Logs by using the REST API (Resource Manager templates)](logs/tutorial-logs-ingestion-api.md)|Made minor fixes and updated sample data.|
Logs|[Analyze usage in a Log Analytics workspace](logs/analyze-usage.md)|Added query for data that has the IsBillable indicator set incorrectly, which could result in incorrect billing.| Logs|[Add or delete tables and columns in Azure Monitor Logs](logs/create-custom-table.md)|Added custom column naming limitations.| Logs|[Enhance data and service resilience in Azure Monitor Logs with availability zones](logs/availability-zones.md)|Clarified availability zone support for data resilience and service resilience and added new supported regions.|
-Logs|[Monitor Log Analytics workspace health](logs/log-analytics-workspace-health.md)|New article that explains how to monitor the service and resource health of a Log Analytics workspace.|
+Logs|[Monitor Log Analytics workspace health](logs/log-analytics-workspace-health.md)|New article: Explains how to monitor the service and resource health of a Log Analytics workspace.|
Logs|[Feature extensions for Application Insights JavaScript SDK (Click Analytics)](app/javascript-click-analytics-plugin.md)|You can now launch Power BI and create a dataset and report connected to a Log Analytics query with one click.|
-Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Added new tables to the list of tables that support Basic logs.|
-Logs|[Manage tables in a Log Analytics workspace]()|Refreshed all Log Analytics workspace images with the new left-hand menu (ToC).|
-Security-Fundamentals|[Monitoring App Service](../../articles/app-service/monitor-app-service.md)|Revised the Azure Monitor Overview to improve usability. The article has been cleaned up and streamlined, and better reflects the product architecture as well as the customer experience. |
-Snapshot-Debugger|[host.json reference for Azure Functions 2.x and later](../../articles/azure-functions/functions-host-json.md)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Snapshot-Debugger|[Configure Bring Your Own Storage (BYOS) for Application Insights Profiler and Snapshot Debugger](profiler/profiler-bring-your-own-storage.md)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Snapshot-Debugger|[Release notes for Microsoft.ApplicationInsights.SnapshotCollector](snapshot-debugger/snapshot-collector-release-notes.md)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure App Service](snapshot-debugger/snapshot-debugger-app-service.md)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Snapshot-Debugger|[Enable Snapshot Debugger for .NET and .NET Core apps in Azure Functions](snapshot-debugger/snapshot-debugger-function-app.md)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Snapshot-Debugger|[ Troubleshoot problems enabling Application Insights Snapshot Debugger or viewing snapshots](/troubleshoot/azure/azure-monitor/app-insights/snapshot-debugger-troubleshoot)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure Service Fabric, Cloud Service, and Virtual Machines](snapshot-debugger/snapshot-debugger-vm.md)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Snapshot-Debugger|[Debug snapshots on exceptions in .NET apps](snapshot-debugger/snapshot-debugger.md)|Removing the TSG from the AzMon TOC and adding to the support TOC|
-Virtual-Machines|[Monitor virtual machines with Azure Monitor: Analyze monitoring data](vm/monitor-virtual-machine-analyze.md)|New article|
+Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Added new tables to the list of tables that support Basic Logs.|
+Logs|[Manage tables in a Log Analytics workspace]()|Refreshed all Log Analytics workspace images with the new TOC on the left.|
+Security-Fundamentals|[Monitoring Azure App Service](../../articles/app-service/monitor-app-service.md)|Revised the Azure Monitor overview to improve usability. The article is cleaned up, streamlined, and better reflects the product architecture and the customer experience. |
+Snapshot-Debugger|[host.json reference for Azure Functions 2.x and later](../../articles/azure-functions/functions-host-json.md)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Snapshot-Debugger|[Configure Bring Your Own Storage (BYOS) for Application Insights Profiler and Snapshot Debugger](profiler/profiler-bring-your-own-storage.md)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Snapshot-Debugger|[Release notes for Microsoft.ApplicationInsights.SnapshotCollector](snapshot-debugger/snapshot-collector-release-notes.md)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure App Service](snapshot-debugger/snapshot-debugger-app-service.md)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Snapshot-Debugger|[Enable Snapshot Debugger for .NET and .NET Core apps in Azure Functions](snapshot-debugger/snapshot-debugger-function-app.md)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Snapshot-Debugger|[ Troubleshoot problems enabling Application Insights Snapshot Debugger or viewing snapshots](/troubleshoot/azure/azure-monitor/app-insights/snapshot-debugger-troubleshoot)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure Service Fabric, Azure Cloud Services, and Virtual Machines](snapshot-debugger/snapshot-debugger-vm.md)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Snapshot-Debugger|[Debug snapshots on exceptions in .NET apps](snapshot-debugger/snapshot-debugger.md)|Removing the TSG from the Azure Monitor TOC and adding to the support TOC.|
+Virtual-Machines|[Monitor virtual machines with Azure Monitor: Analyze monitoring data](vm/monitor-virtual-machine-analyze.md)|New article.|
Visualizations|[Use JSONPath to transform JSON data in workbooks](visualize/workbooks-jsonpath.md)|Added information about using JSONPath to convert data types in Azure Workbooks.|
-Containers|[Configure Container insights cost optimization data collection rules]()|New article on preview of cost optimization settings.|
+Containers|[Configure Container insights cost-optimization data collection rules](containers/container-insights-cost-config.md)|New article: Preview of cost-optimization settings.|
+## January 2023
-## January 2023
-
|Subservice| Article | Description | ||||
-Agents|[Tutorial: Transform text logs during ingestion in Azure Monitor Logs](agents/azure-monitor-agent-transformation.md)|New tutorial on how to write a KQL query that transforms text log data and add the transformation to a data collection rule.|
+Agents|[Tutorial: Transform text logs during ingestion in Azure Monitor Logs](agents/azure-monitor-agent-transformation.md)|New tutorial: How to write a KQL query that transforms text log data and add the transformation to a data collection rule.|
Agents|[Azure Monitor Agent overview](agents/agents-overview.md)|SQL Best Practices Assessment now available with Azure Monitor Agent.|
-Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|Streamlined alerts documentation, added the common schema definition to the common schema article, and moving sample ARM templates for alerts to the Samples section.|
-Alerts|[Non-common alert schema definitions for Test Action Group (Preview)](alerts/alerts-non-common-schema-definitions.md)|Added a sample payload for the Actual Cost and Forecasted Budget schemas.|
-Application-Insights|[Live Metrics: Monitor and diagnose with 1-second latency](app/live-stream.md)|Updated Live Metrics troubleshooting section.|
-Application-Insights|[Application Insights for Azure VMs and Virtual Machine Scale Sets](app/azure-vm-vmss-apps.md)|Easily monitor your IIS-hosted .NET Framework and .NET Core applications running on Azure VMs and Virtual Machine Scale Sets using a new App Insights Extension.|
-Application-Insights|[Sampling in Application Insights](app/sampling.md)|We've added embedded links to assist with looking up type definitions. (Dependency, Event, Exception, PageView, Request, Trace)|
-Application-Insights|[Configuration options: Azure Monitor Application Insights for Java](app/java-standalone-config.md)|Instructions are now available on how to set the http proxy using an environment variable, which overrides the JSON configuration. We've also provided a sample to configure connection string at runtime.|
+Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|Streamlined alerts documentation, added the common schema definition to the common schema article, and moved sample Resource Manager templates for alerts to the "Samples" section.|
+Alerts|[Non-common alert schema definitions for Test Action Group (preview)](alerts/alerts-non-common-schema-definitions.md)|Added a sample payload for the Actual Cost and Forecasted Budget schemas.|
+Application-Insights|[Live Metrics: Monitor and diagnose with 1-second latency](app/live-stream.md)|Updated Live Metrics "Troubleshooting" section.|
+Application-Insights|[Application Insights for Azure Virtual Machines and Azure Virtual Machine Scale Sets](app/azure-vm-vmss-apps.md)|Easily monitor your IIS-hosted .NET Framework and .NET Core applications running on Azure Virtual Machines and Azure Virtual Machine Scale Sets by using a new App Insights extension.|
+Application-Insights|[Sampling in Application Insights](app/sampling.md)|Added embedded links to assist with looking up type definitions (dependency, event, exception, PageView, request, and trace).|
+Application-Insights|[Configuration options: Azure Monitor Application Insights for Java](app/java-standalone-config.md)|Instructions are now available on how to set the HTTP proxy by using an environment variable, which overrides the JSON configuration. We've also provided a sample to configure connection string at runtime.|
Application-Insights|[Application Insights for Java 2.x](/previous-versions/azure/azure-monitor/app/deprecated-java-2x)|The Java 2.x retirement notice is available at [https://azure.microsoft.com/updates/application-insights-java-2x-retirement](https://azure.microsoft.com/updates/application-insights-java-2x-retirement).|
-Autoscale|[Diagnostic settings in Autoscale](autoscale/autoscale-diagnostics.md)|Updated and expanded content|
-Autoscale|[Overview of common autoscale patterns](autoscale/autoscale-common-scale-patterns.md)|Clarification of weekend profiles|
-Autoscale|[Autoscale with multiple profiles](autoscale/autoscale-multiprofile.md)|Added clarifications for profile end times|
-Change-Analysis|[Scenarios for using Change Analysis in Azure Monitor](change/change-analysis-custom-filters.md)|Merged two low engagement docs into Visualizations article and removed from TOC|
-Change-Analysis|[Scenarios for using Change Analysis in Azure Monitor](change/change-analysis-query.md)|Merged two low engagement docs into Visualizations article and removed from TOC|
-Change-Analysis|[Scenarios for using Change Analysis in Azure Monitor](change/change-analysis-visualizations.md)|Merged two low engagement docs into Visualizations article and removed from TOC|
-Change-Analysis|[Track a web app outage using Change Analysis](change/tutorial-outages.md)|Added new section on virtual network changes to the tutorial|
-Containers|[Azure Monitor container insights for Azure Kubernetes Service (AKS) hybrid clusters (preview)](containers/container-insights-enable-provisioned-clusters.md)|New article.|
-Containers|[Syslog collection with Container Insights (preview)](containers/container-insights-syslog.md)|New article.|
-Essentials|[Query Prometheus metrics using Azure workbooks (preview)](essentials/prometheus-workbooks.md)|New article.|
+Autoscale|[Diagnostic settings in autoscale](autoscale/autoscale-diagnostics.md)|Updated and expanded content.|
+Autoscale|[Overview of common autoscale patterns](autoscale/autoscale-common-scale-patterns.md)|Clarification of weekend profiles.|
+Autoscale|[Autoscale with multiple profiles](autoscale/autoscale-multiprofile.md)|Added clarifications for profile end times.|
+Change-Analysis|[Scenarios for using Change Analysis in Azure Monitor](change/change-analysis-custom-filters.md)|Merged two low-engagement docs into Visualizations article and removed from TOC.|
+Change-Analysis|[Scenarios for using Change Analysis in Azure Monitor](change/change-analysis-query.md)|Merged two low-engagement docs into Visualizations article and removed from TOC.|
+Change-Analysis|[Scenarios for using Change Analysis in Azure Monitor](change/change-analysis-visualizations.md)|Merged two low-engagement docs into Visualizations article and removed from TOC.|
+Change-Analysis|[Track a web app outage by using Change Analysis](change/tutorial-outages.md)|Added new section on virtual network changes to the tutorial.|
+Containers|[Azure Monitor container insights for Azure Kubernetes Service hybrid clusters (preview)](containers/container-insights-enable-provisioned-clusters.md)|New article.|
+Containers|[Syslog collection with Container insights (preview)](containers/container-insights-syslog.md)|New article.|
+Essentials|[Query Prometheus metrics by using Azure Workbooks (preview)](essentials/prometheus-workbooks.md)|New article.|
Essentials|[Azure Workbooks data sources](visualize/workbooks-data-sources.md)|Added section for Prometheus metrics.|
-Essentials|[Query Prometheus metrics using Azure workbooks (preview)](essentials/prometheus-workbooks.md)|New article|
-Essentials|[Azure Monitor workspace (preview)](essentials/azure-monitor-workspace-overview.md)|Updated design considerations|
-Essentials|[Supported metrics with Azure Monitor](essentials/metrics-supported.md)|Updated and refreshed the list of supported metrics|
-Essentials|[Supported categories for Azure Monitor resource logs](essentials/resource-logs-categories.md)|Updated and refreshed the list of supported logs|
+Essentials|[Query Prometheus metrics by using Azure Workbooks (preview)](essentials/prometheus-workbooks.md)|New article.|
+Essentials|[Azure Monitor workspace (preview)](essentials/azure-monitor-workspace-overview.md)|Updated design considerations.|
+Essentials|[Supported metrics with Azure Monitor](essentials/metrics-supported.md)|Updated and refreshed the list of supported metrics.|
+Essentials|[Supported categories for Azure Monitor resource logs](essentials/resource-logs-categories.md)|Updated and refreshed the list of supported logs.|
General|[Multicloud monitoring with Azure Monitor](best-practices-multicloud.md)|New article.| Logs|[Set daily cap on Log Analytics workspace](logs/daily-cap.md)|Clarified special case for daily cap logic.|
-Logs|[Send custom metrics for an Azure resource to the Azure Monitor metric store by using a REST API](essentials/metrics-store-custom-rest-api.md)|Updated and refreshed how to send custom metrics|
-Logs|[Migrate from Splunk to Azure Monitor Logs](logs/migrate-splunk-to-azure-monitor-logs.md)|New article that explains how to migrate your Splunk Observability deployment to Azure Monitor Logs for logging and log data analysis.|
+Logs|[Send custom metrics for an Azure resource to the Azure Monitor metric store by using a REST API](essentials/metrics-store-custom-rest-api.md)|Updated and refreshed how to send custom metrics.|
+Logs|[Migrate from Splunk to Azure Monitor Logs](logs/migrate-splunk-to-azure-monitor-logs.md)|New article: Explains how to migrate your Splunk Observability deployment to Azure Monitor Logs for logging and log data analysis.|
Logs|[Manage access to Log Analytics workspaces](logs/manage-access.md)|Added permissions required to run a search job and restore archived data.|
-Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Added information about how to modify a table schema using the API.|
-Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure App Service](snapshot-debugger/snapshot-debugger-app-service.md)|Per customer feedback, added new note that Consumption plan isn't supported|
+Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Added information about how to modify a table schema by using the API.|
+Snapshot-Debugger|[Enable Snapshot Debugger for .NET apps in Azure App Service](snapshot-debugger/snapshot-debugger-app-service.md)|Per customer feedback, added new note that Consumption plan isn't supported.|
Virtual-Machines|[Collect IIS logs with Azure Monitor Agent](agents/data-collection-iis.md)|Added sample log queries.| Virtual-Machines|[Collect text logs with Azure Monitor Agent](agents/data-collection-text-log.md)|Added sample log queries.|
-Virtual-Machines|[Monitor virtual machines with Azure Monitor: Deploy agent](vm/monitor-virtual-machine-agent.md)|Rewritten for Azure Monitor agent.|
-Virtual-Machines|[Monitor virtual machines with Azure Monitor: Alerts](vm/monitor-virtual-machine-alerts.md)|Rewritten for Azure Monitor agent.|
-Virtual-Machines|[Monitor virtual machines with Azure Monitor: Analyze monitoring data](vm/monitor-virtual-machine-analyze.md)|Rewritten for Azure Monitor agent.|
-Virtual-Machines|[Monitor virtual machines with Azure Monitor: Collect data](vm/monitor-virtual-machine-data-collection.md)|Rewritten for Azure Monitor agent.|
-Virtual-Machines|[Monitor virtual machines with Azure Monitor: Migrate management pack logic](vm/monitor-virtual-machine-management-packs.md)|Rewritten for Azure Monitor agent.|
-Virtual-Machines|[Monitor virtual machines with Azure Monitor](vm/monitor-virtual-machine.md)|Rewritten for Azure Monitor agent.|
-Virtual-Machines|[Monitor Azure virtual machines](../../articles/virtual-machines/monitor-vm.md)|VM scenario updates for AMA|
-
-## December 2022
-
+Virtual-Machines|[Monitor virtual machines with Azure Monitor: Deploy agent](vm/monitor-virtual-machine-agent.md)|Rewritten for Azure Monitor Agent.|
+Virtual-Machines|[Monitor virtual machines with Azure Monitor: Alerts](vm/monitor-virtual-machine-alerts.md)|Rewritten for Azure Monitor Agent.|
+Virtual-Machines|[Monitor virtual machines with Azure Monitor: Analyze monitoring data](vm/monitor-virtual-machine-analyze.md)|Rewritten for Azure Monitor Agent.|
+Virtual-Machines|[Monitor virtual machines with Azure Monitor: Collect data](vm/monitor-virtual-machine-data-collection.md)|Rewritten for Azure Monitor Agent.|
+Virtual-Machines|[Monitor virtual machines with Azure Monitor: Migrate management pack logic](vm/monitor-virtual-machine-management-packs.md)|Rewritten for Azure Monitor Agent.|
+Virtual-Machines|[Monitor virtual machines with Azure Monitor](vm/monitor-virtual-machine.md)|Rewritten for Azure Monitor Agent.|
+Virtual-Machines|[Monitor Azure virtual machines](../../articles/virtual-machines/monitor-vm.md)|VM scenario updates for Azure Monitor Agent.|
+
+## December 2022
+ |Subservice| Article | Description | ||||
-General|[Azure Monitor for existing Operations Manager customers](azure-monitor-operations-manager.md)|Updated for AMA and SCOM managed instance.|
-Application-Insights|[Create an Application Insights resource](/previous-versions/azure/azure-monitor/app/create-new-resource)|Classic Application Insights resources are deprecated and support will end on February 29, 2024. Migrate to workspace-based resources to take advantage of new capabilities.|
+General|[Azure Monitor for existing Operations Manager customers](azure-monitor-operations-manager.md)|Updated for Azure Monitor Agent and System Center Operations Manager managed instance.|
+Application-Insights|[Create an Application Insights resource](/previous-versions/azure/azure-monitor/app/create-new-resource)|Classic Application Insights resources are deprecated. Support ends on February 29, 2024. Migrate to workspace-based resources to take advantage of new capabilities.|
Application-Insights|[Enable Azure Monitor OpenTelemetry for .NET, Node.js, and Python applications (preview)](app/opentelemetry-enable.md)|Updated Node.js sample code for JavaScript and TypeScript.| Application-Insights|[System performance counters in Application Insights](app/performance-counters.md)|Updated code samples for .NET 6/7.| Application-Insights|[Sampling in Application Insights](app/sampling.md)|Updated code samples for .NET 6/7.|
-Application-Insights|[Availability alerts](app/availability-alerts.md)|This article has been rewritten with new guidance and screenshots.|
-Change-Analysis|[Tutorial: Track a web app outage using Change Analysis](change/tutorial-outages.md)|Change tutorial content to reflect changes to repo; remove and replace a few sections.|
-Containers|[Configure Azure CNI networking in Azure Kubernetes Service (AKS)](../../articles/aks/configure-azure-cni.md)|Added steps to enable IP subnet usage|
-Containers|[Reports in Container insights](containers/container-insights-reports.md)|Updated the documents to reflect the steps to enable IP subnet Usage|
-Essentials|[Best practices for data collection rule creation and management in Azure Monitor](essentials/data-collection-rule-best-practices.md)|New article|
-Essentials|[Configure self-managed Grafana to use Azure Monitor managed service for Prometheus (preview) with Azure Active Directory.](essentials/prometheus-self-managed-grafana-azure-active-directory.md)|New Article: Configure self-managed Grafana to use Azure Monitor managed service for Prometheus (preview) with Azure Active Directory.|
-Logs|[Azure Monitor SCOM Managed Instance (preview)](vm/scom-managed-instance-overview.md)|New article|
-Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Updated the list of tables that support Basic logs.|
-Virtual-Machines|[Tutorial: Create availability alert rule for Azure virtual machine (preview)](vm/tutorial-monitor-vm-alert-availability.md)|New article|
-Virtual-Machines|[Tutorial: Enable recommended alert rules for Azure virtual machine](vm/tutorial-monitor-vm-alert-recommended.md)|New article|
-Virtual-Machines|[Tutorial: Enable monitoring with VM insights for Azure virtual machine](vm/tutorial-monitor-vm-enable-insights.md)|New article|
-Virtual-Machines|[Monitor Azure virtual machines](../../articles/virtual-machines/monitor-vm.md)|Updated for AMA and availability metric.|
+Application-Insights|[Availability alerts](app/availability-alerts.md)|Rewritten with new guidance and screenshots.|
+Change-Analysis|[Tutorial: Track a web app outage by using Change Analysis](change/tutorial-outages.md)|Changed tutorial content to reflect changes to repo and removed and replaced sections.|
+Containers|[Configure Azure CNI networking in Azure Kubernetes Service](../../articles/aks/configure-azure-cni.md)|Added steps to enable IP subnet usage.|
+Containers|[Reports in Container insights](containers/container-insights-reports.md)|Updated to reflect the steps to enable IP subnet usage.|
+Essentials|[Best practices for data collection rule creation and management in Azure Monitor](essentials/data-collection-rule-best-practices.md)|New article.|
+Essentials|[Configure self-managed Grafana to use Azure Monitor managed service for Prometheus (preview) with Azure Active Directory](essentials/prometheus-self-managed-grafana-azure-active-directory.md)|New article: Configured self-managed Grafana to use Azure Monitor managed service for Prometheus (preview) with Azure Active Directory.|
+Logs|[Azure Monitor SCOM Managed Instance (preview)](vm/scom-managed-instance-overview.md)|New article.|
+Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Updated the list of tables that support Basic Logs.|
+Virtual-Machines|[Tutorial: Create availability alert rule for Azure virtual machine (preview)](vm/tutorial-monitor-vm-alert-availability.md)|New article.|
+Virtual-Machines|[Tutorial: Enable recommended alert rules for Azure virtual machine](vm/tutorial-monitor-vm-alert-recommended.md)|New article.|
+Virtual-Machines|[Tutorial: Enable monitoring with VM insights for Azure virtual machine](vm/tutorial-monitor-vm-enable-insights.md)|New article.|
+Virtual-Machines|[Monitor Azure virtual machines](../../articles/virtual-machines/monitor-vm.md)|Updated for Azure Monitor Agent and availability metric.|
Virtual-Machines|[Enable VM insights by using Azure Policy](vm/vminsights-enable-policy.md)|Updated flow for enabling VM insights with Azure Monitor Agent by using Azure Policy.|
-Visualizations|[Creating an Azure Workbook](visualize/workbooks-create-workbook.md)|added Tutorial - resource centric logs queries in workbooks|
+Visualizations|[Creating an Azure Workbook](visualize/workbooks-create-workbook.md)|Added tutorial on resource-centric log queries in workbooks.|
+
+## November 2022
-## November 2022
-
-
-
|Subservice| Article | Description | ||||
-General|[Cost optimization and Azure Monitor](best-practices-cost.md)|Complete rewrite to align with Well Architected Framework. Detailed content moved to other articles and linked from here.|
-Agents|[Collect SNMP trap data with Azure Monitor Agent](agents/data-collection-snmp-data.md)|New tutorial that explains how to collect Simple Network Management Protocol (SNMP) traps using Azure Monitor Agent.|
-Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|Resource Health alerts and Service Health alerts are created using the same simplified workflow as all other alert types.|
-Alerts|[Manage your alert rules](alerts/alerts-manage-alert-rules.md)|Recommended alert rules are enabled for AKS and Log Analytics workspace resources in addition to VMs.|
-Application-insights|[Sampling in Application Insights](app/sampling.md)|ASP.NET Core applications may be configured in code or through the `appsettings.json` file. Conflicting information was removed.|
-Application-insights|[How many Application Insights resources should I deploy?](app/separate-resources.md)|Clarification has been added on setting iKey dynamically in code.|
-Application-insights|[Application Map: Triage distributed applications](app/app-map.md)|App Map Filters, an exciting new feature, has been documented.|
+General|[Cost optimization and Azure Monitor](best-practices-cost.md)|Rewritten to align with Azure Well-Architected Framework. Moved detailed content to other articles and linked from here.|
+Agents|[Collect SNMP trap data with Azure Monitor Agent](agents/data-collection-snmp-data.md)|New tutorial: Explains how to collect Simple Network Management Protocol (SNMP) traps by using Azure Monitor Agent.|
+Alerts|[Create a new alert rule](alerts/alerts-create-new-alert-rule.md)|Resource Health alerts and Service Health alerts are created by using the same simplified workflow as all other alert types.|
+Alerts|[Manage your alert rules](alerts/alerts-manage-alert-rules.md)|Recommended alert rules are enabled for Azure Kubernetes Service and Log Analytics workspace resources in addition to VMs.|
+Application-insights|[Sampling in Application Insights](app/sampling.md)|ASP.NET Core applications can be configured in code or through the `appsettings.json` file. Removed conflicting information.|
+Application-insights|[How many Application Insights resources should I deploy?](app/separate-resources.md)|Added clarification on setting iKey dynamically in code.|
+Application-insights|[Application Map: Triage distributed applications](app/app-map.md)|Documented App Map Filters, an exciting new feature.|
Application-insights|[Enable Application Insights for ASP.NET Core applications](app/tutorial-asp-net-core.md)|The Azure Café sample app is now hosted and linked on Git.|
-Application-insights|[What is auto-instrumentation for Azure Monitor Application Insights?](app/codeless-overview.md)|Our auto-instrumentation supported languages chart has been updated.|
-Application-insights|[Application Monitoring for Azure App Service and ASP.NET](app/azure-web-apps-net.md)|Links to check versions have been corrected.|
+Application-insights|[What is auto-instrumentation for Azure Monitor Application Insights?](app/codeless-overview.md)|Updated the auto-instrumentation supported languages chart.|
+Application-insights|[Application monitoring for Azure App Service and ASP.NET](app/azure-web-apps-net.md)|Corrected links to check versions.|
Application-insights|[Sampling overrides (preview) - Azure Monitor Application Insights for Java](app/java-standalone-sampling-overrides.md)|Updated OpenTelemetry Span information for Java.|
-Autoscale|[Understand autoscale settings](autoscale/autoscale-understanding-settings.md)|Refresh and update|
+Autoscale|[Understand autoscale settings](autoscale/autoscale-understanding-settings.md)|Refreshed and updated.|
Autoscale|[Overview of common autoscale patterns](autoscale/autoscale-common-scale-patterns.md)|Refreshed and updated.|
-Essentials|[Azure Monitor managed service for Prometheus (preview)](essentials/prometheus-metrics-scrape-default.md)|General restructure of Prometheus content.|
-Essentials|[Configure remote write for Azure Monitor managed service for Prometheus using Azure Active Directory authentication (preview)](essentials/prometheus-remote-write.md)|New article|
+Essentials|[Azure Monitor managed service for Prometheus (preview)](essentials/prometheus-metrics-scrape-default.md)|Restructured Prometheus content.|
+Essentials|[Configure remote write for Azure Monitor managed service for Prometheus by using Azure Active Directory authentication (preview)](essentials/prometheus-remote-write.md)|New article.|
Essentials|[Azure Monitor workspace (preview)](essentials/azure-monitor-workspace-overview.md)|Added Bicep example.|
-Essentials|[Migrate from diagnostic settings storage retention to Azure Storage lifecycle management](essentials/migrate-to-azure-storage-lifecycle-policy.md)|Deprecation note added|
+Essentials|[Migrate from diagnostic settings storage retention to Azure Storage lifecycle management](essentials/migrate-to-azure-storage-lifecycle-policy.md)|Added deprecation note.|
Essentials|[Diagnostic settings in Azure Monitor](essentials/diagnostic-settings.md)|All destination endpoints support TLS 1.2.| Logs|[Cost optimization and Azure Monitor](best-practices-cost.md)|Added cost information and removed preview label.| Logs|[Diagnostic settings in Azure Monitor](essentials/diagnostic-settings.md)|Added section on controlling costs with transformations.|
-Logs|[Analyze usage in a Log Analytics workspace](logs/analyze-usage.md)|Added KQL query that retrieves data volumes for charged data types.|
-Logs|[Access the Azure Monitor Log Analytics API](logs/api/timeouts.md)|Refresh and update|
-Logs|[Collect text logs with the Log Analytics agent in Azure Monitor](agents/data-sources-custom-logs.md)|New table management section with new articles on table configuration options, schema management, and custom table creation.|
+Logs|[Analyze usage in a Log Analytics workspace](logs/analyze-usage.md)|Added Kusto Query Language query that retrieves data volumes for charged data types.|
+Logs|[Access the Azure Monitor Log Analytics API](logs/api/timeouts.md)|Refreshed and updated.|
+Logs|[Collect text logs with the Log Analytics agent in Azure Monitor](agents/data-sources-custom-logs.md)|Added new table management section with new articles on table configuration options, schema management, and custom table creation.|
Logs|[Azure Monitor Metrics overview](essentials/data-platform-metrics.md)| Added a new Azure SDK client library for Go.|
-Logs|[Azure Monitor Log Analytics API Overview](logs/api/overview.md)| Added a new Azure SDK client library for Go.|
+Logs|[Azure Monitor Log Analytics API overview](logs/api/overview.md)| Added a new Azure SDK client library for Go.|
Logs|[Azure Monitor Logs overview](logs/data-platform-logs.md)| Added a new Azure SDK client library for Go.| Logs|[Log queries in Azure Monitor](logs/log-query-overview.md)| Added a new Azure SDK client library for Go.|
-Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Added new tables to the list of tables that support the Basic log data plan.|
-Visualizations|[Monitor your Azure services in Grafana](visualize/grafana-plugin.md)|The Grafana integration is GA, and is no longer in preview.|
-Visualizations|[Get started with Azure Workbooks](visualize/workbooks-getting-started.md)|Added instructions for how to share Workbooks.|
+Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Added new tables to the list of tables that support the Basic Log data plan.|
+Visualizations|[Monitor your Azure services in Grafana](visualize/grafana-plugin.md)|The Grafana integration is generally available and is no longer in preview.|
+Visualizations|[Get started with Azure Workbooks](visualize/workbooks-getting-started.md)|Added instructions for how to share workbooks.|
-
+## October 2022
-## October 2022
-
-
-
-|Sub-service| Article | Description |
+|Subservice| Article | Description |
||||
-|General|Table of contents|We have updated the Azure Monitor Table of Contents. The new TOC structure better reflects the customer experience and makes it easier for users to navigate and discover our content.|
+|General|Table of contents|Updated the Azure Monitor table of contents (TOC). The new TOC structure better reflects the customer experience and makes it easier for users to navigate and discover our content.|
Alerts|[Connect Azure to ITSM tools by using IT Service Management](./alerts/itsmc-definition.md)|Deprecating support for sending ITSM actions and events to ServiceNow. Instead, use ITSM actions in action groups based on Azure alerts to create work items in your ITSM tool.| Alerts|[Create a new alert rule](./alerts/alerts-create-new-alert-rule.md)|New PowerShell commands to create and manage log alerts.| Alerts|[Types of Azure Monitor alerts](alerts/alerts-types.md)|Updated to include Prometheus alerts.|
-Alerts|[Customize alert notifications using Logic Apps](./alerts/alerts-logic-apps.md)|New: How to use alerts to send emails or Teams posts using logic apps|
-Application-insights|[Sampling in Application Insights](./app/sampling.md)|The "When to use sampling" and "How sampling works" sections have been prioritized as prerequisite information for the rest of the article.|
-Application-insights|[What is auto-instrumentation for Azure Monitor Application Insights?](./app/codeless-overview.md)|The auto-instrumentation overview has been visually overhauled with links and footnotes.|
+Alerts|[Customize alert notifications by using Logic Apps](./alerts/alerts-logic-apps.md)|New article: Use alerts to send emails or Teams posts by using Logic Apps.|
+Application-insights|[Sampling in Application Insights](./app/sampling.md)|Prioritized the "When to use sampling" and "How sampling works" sections as prerequisite information for the article.|
+Application-insights|[What is auto-instrumentation for Azure Monitor Application Insights?](./app/codeless-overview.md)|Overhauled the auto-instrumentation overview with links and footnotes.|
Application-insights|[Enable Azure Monitor OpenTelemetry for .NET, Node.js, and Python applications (preview)](./app/opentelemetry-enable.md)|Open Telemetry Metrics are now available for .NET, Node.js and Python applications.|
-Application-insights|[Find and diagnose performance issues with Application Insights](./app/tutorial-performance.md)|The URL Ping (Classic) Test has been replaced with the Standard Test step-by-step instructions.|
-Application-insights|[Application Insights API for custom events and metrics](./app/api-custom-events-metrics.md)|Flushing information was added to the FAQ.|
-Application-insights|[Azure AD authentication for Application Insights](./app/azure-ad-authentication.md)|We updated the `TelemetryConfiguration` code sample using .NET.|
-Application-insights|[Using Azure Monitor Application Insights with Spring Boot](./app/java-spring-boot.md)|Spring Boot information was updated to 3.4.2.|
-Application-insights|[Configuration options: Azure Monitor Application Insights for Java](./app/java-standalone-config.md)|New features include Capture Log4j Markers and Logback Markers as custom properties on the corresponding trace (log message) telemetry.|
-Application-insights|[Create custom KPI dashboards using Application Insights](./app/tutorial-app-dashboards.md)|This article has been refreshed with new screenshots and instructions.|
-Application-insights|[Share Azure dashboards by using Azure role-based access control](../azure-portal/azure-portal-dashboard-share-access.md)|This article has been refreshed with new screenshots and instructions.|
-Application-insights|[Application Monitoring for Azure App Service and ASP.NET](./app/azure-web-apps-net.md)|Important notes added regarding System.IO.FileNotFoundException after 2.8.44 auto-instrumentation upgrade.|
-Application-insights|[Geolocation and IP address handling](./app/ip-collection.md)| Geolocation lookup information has been updated.|
-Containers|[Metric alert rules in Container insights (preview)](./containers/container-insights-metric-alerts.md)|Container insights metric Alerts|
+Application-insights|[Find and diagnose performance issues with Application Insights](./app/tutorial-performance.md)|Replaced the URL Ping (Classic) Test with Standard Test step-by-step instructions.|
+Application-insights|[Application Insights API for custom events and metrics](./app/api-custom-events-metrics.md)|Added flushing information to the FAQ.|
+Application-insights|[Azure AD authentication for Application Insights](./app/azure-ad-authentication.md)|Updated the `TelemetryConfiguration` code sample by using .NET.|
+Application-insights|[Using Azure Monitor Application Insights with Spring Boot](./app/java-spring-boot.md)|Updated the Spring Boot information to 3.4.2.|
+Application-insights|[Configuration options: Azure Monitor Application Insights for Java](./app/java-standalone-config.md)|Added new features on Capture Log4j Markers and Logback Markers as custom properties on the corresponding trace (log message) telemetry.|
+Application-insights|[Create custom KPI dashboards by using Application Insights](./app/tutorial-app-dashboards.md)|Refreshed with new screenshots and instructions.|
+Application-insights|[Share Azure dashboards by using Azure role-based access control](../azure-portal/azure-portal-dashboard-share-access.md)|Refreshed with new screenshots and instructions.|
+Application-insights|[Application monitoring for Azure App Service and ASP.NET](./app/azure-web-apps-net.md)|Added important notes about System.IO.FileNotFoundException after an 2.8.44 auto-instrumentation upgrade.|
+Application-insights|[Geolocation and IP address handling](./app/ip-collection.md)| Updated geolocation lookup information.|
+Containers|[Metric alert rules in Container insights (preview)](./containers/container-insights-metric-alerts.md)|Updated to include Container insights metric alerts.|
Containers|[Custom metrics collected by Container insights](containers/container-insights-custom-metrics.md?tabs=portal)|New article.| Containers|[Overview of Container insights in Azure Monitor](containers/container-insights-overview.md)|Rewritten to simplify onboarding options.|
-Containers|[Enable Container insights for Azure Kubernetes Service (AKS) cluster](containers/container-insights-enable-aks.md?tabs=azure-cli)|Updated to combine new and existing clusters.|
-Containers Prometheus|[Query logs from Container insights](containers/container-insights-log-query.md)|Now includes log queries for Prometheus data.|
+Containers|[Enable Container insights for Azure Kubernetes Service cluster](containers/container-insights-enable-aks.md?tabs=azure-cli)|Updated to combine new and existing clusters.|
+Containers Prometheus|[Query logs from Container insights](containers/container-insights-log-query.md)|Updated to include log queries for Prometheus data.|
Containers Prometheus|[Collect Prometheus metrics with Container insights](containers/container-insights-prometheus.md?tabs=cluster-wide)|Updated to include Azure Monitor managed service for Prometheus.|
-Essentials Prometheus|[Metrics in Azure Monitor](essentials/data-platform-metrics.md)|Updated to include Azure Monitor managed service for Prometheus|
-Essentials Prometheus|<ul> <li> [Azure Monitor workspace overview (preview)](essentials/azure-monitor-workspace-overview.md?tabs=azure-portal) </li><li> [Overview of Azure Monitor Managed Service for Prometheus (preview)](essentials/prometheus-metrics-overview.md) </li><li>[Rule groups in Azure Monitor Managed Service for Prometheus (preview)](essentials/prometheus-rule-groups.md)</li><li>[Remote-write in Azure Monitor Managed Service for Prometheus (preview)](essentials/prometheus-remote-write-managed-identity.md) </li><li>[Use Azure Monitor managed service for Prometheus (preview) as data source for Grafana](essentials/prometheus-grafana.md)</li><li>[Troubleshoot collection of Prometheus metrics in Azure Monitor (preview)](essentials/prometheus-metrics-troubleshoot.md)</li><li>[Default Prometheus metrics configuration in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-default.md)</li><li>[Scrape Prometheus metrics at scale in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-scale.md)</li><li>[Customize scraping of Prometheus metrics in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-configuration.md)</li><li>[Create, validate and troubleshoot custom configuration file for Prometheus metrics in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-validate.md)</li><li>[Minimal Prometheus ingestion profile in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-configuration-minimal.md)</li><li>[Collect Prometheus metrics from AKS cluster (preview)](essentials/prometheus-metrics-enable.md)</li><li>[Send Prometheus metrics to multiple Azure Monitor workspaces (preview)](essentials/prometheus-metrics-multiple-workspaces.md) </li></ul> |New articles. Public preview of Azure Monitor managed service for Prometheus|
-Essentials Prometheus|[Azure Monitor managed service for Prometheus remote write - managed identity (preview)](./essentials/prometheus-remote-write-managed-identity.md)|Addition: Verify Prometheus remote write is working correctly|
-Essentials|[Azure resource logs](./essentials/resource-logs.md)|Clarification: Which blobs logs are written to, and when|
+Essentials Prometheus|[Metrics in Azure Monitor](essentials/data-platform-metrics.md)|Updated to include Azure Monitor managed service for Prometheus.|
+Essentials Prometheus|<ul> <li> [Azure Monitor workspace overview (preview)](essentials/azure-monitor-workspace-overview.md?tabs=azure-portal) </li><li> [Overview of Azure Monitor managed service for Prometheus (preview)](essentials/prometheus-metrics-overview.md) </li><li>[Rule groups in Azure Monitor managed service for Prometheus (preview)](essentials/prometheus-rule-groups.md)</li><li>[Remote-write in Azure Monitor managed service for Prometheus (preview)](essentials/prometheus-remote-write-managed-identity.md) </li><li>[Use Azure Monitor managed service for Prometheus (preview) as data source for Grafana](essentials/prometheus-grafana.md)</li><li>[Troubleshoot collection of Prometheus metrics in Azure Monitor (preview)](essentials/prometheus-metrics-troubleshoot.md)</li><li>[Default Prometheus metrics configuration in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-default.md)</li><li>[Scrape Prometheus metrics at scale in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-scale.md)</li><li>[Customize scraping of Prometheus metrics in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-configuration.md)</li><li>[Create, validate, and troubleshoot custom configuration file for Prometheus metrics in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-validate.md)</li><li>[Minimal Prometheus ingestion profile in Azure Monitor (preview)](essentials/prometheus-metrics-scrape-configuration-minimal.md)</li><li>[Collect Prometheus metrics from AKS cluster (preview)](essentials/prometheus-metrics-enable.md)</li><li>[Send Prometheus metrics to multiple Azure Monitor workspaces (preview)](essentials/prometheus-metrics-multiple-workspaces.md) </li></ul> |New articles: Public preview of Azure Monitor managed service for Prometheus.|
+Essentials Prometheus|[Azure Monitor managed service for Prometheus remote write - managed identity (preview)](./essentials/prometheus-remote-write-managed-identity.md)|Added information that verifies Prometheus remote write is working correctly.|
+Essentials|[Azure resource logs](./essentials/resource-logs.md)|Clarified which blob's logs are written to, and when.|
Essentials|[Resource Manager template samples for Azure Monitor](resource-manager-samples.md?tabs=portal)|Added template deployment methods.|
-Essentials|[Azure Monitor service limits](service-limits.md)|Added Azure Monitor managed service for Prometheus|
-Logs|[Manage access to Log Analytics workspaces](./logs/manage-access.md)|Table-level role-based access control (RBAC) lets you give specific users or groups read access to particular tables.|
-Logs|[Configure Basic Logs in Azure Monitor](./logs/basic-logs-configure.md)|General availability of the Basic Logs data plan, retention and archiving, search job, and the table management user experience in the Azure portal.|
-Logs|[Guided project - Analyze logs in Azure Monitor with KQL - Training](/training/modules/analyze-logs-with-kql/)|New Learn module. Learn to write KQL queries to retrieve and transform log data to answer common business and operational questions.|
-Logs|[Detect and analyze anomalies with KQL in Azure Monitor](logs/kql-machine-learning-azure-monitor.md)|New tutorial. Walkthrough of how to use KQL for time series analysis and anomaly detection in Azure Monitor Log Analytics. |
+Essentials|[Azure Monitor service limits](service-limits.md)|Added Azure Monitor managed service for Prometheus.|
+Logs|[Manage access to Log Analytics workspaces](./logs/manage-access.md)|Table-level role-based access control lets you give specific users or groups read access to particular tables.|
+Logs|[Configure Basic Logs in Azure Monitor](./logs/basic-logs-configure.md)|Added information on general availability of the Basic Logs data plan, retention and archiving, search job, and the table management user experience in the Azure portal.|
+Logs|[Guided project - Analyze logs in Azure Monitor with KQL - Training](/training/modules/analyze-logs-with-kql/)|New Learn module: Learn to write KQL queries to retrieve and transform log data to answer common business and operational questions.|
+Logs|[Detect and analyze anomalies with KQL in Azure Monitor](logs/kql-machine-learning-azure-monitor.md)|New tutorial: Walkthrough of how to use KQL for time-series analysis and anomaly detection in Azure Monitor Log Analytics. |
Virtual-machines|[Enable VM insights for a hybrid virtual machine](./vm/vminsights-enable-hybrid.md)|Updated versions of standalone installers.|
-Visualizations|[Retrieve legacy Application Insights workbooks](./visualize/workbooks-retrieve-legacy-workbooks.md)|New article about how to access legacy workbooks in the Azure portal.|
+Visualizations|[Retrieve legacy Application Insights workbooks](./visualize/workbooks-retrieve-legacy-workbooks.md)|New article: Access legacy workbooks in the Azure portal.|
Visualizations|[Azure Workbooks](./visualize/workbooks-overview.md)|New video to see how you can use Azure Workbooks to get insights and visualize your data. | ## September 2022 - ### Agents | Article | Description | |||
-|[Azure Monitor Agent overview](./agents/agents-overview.md)|Added Azure Monitor Agent support for ARM64-based virtual machines for a number of distributions. <br><br>Azure Monitor Agent and legacy agents don't support machines and appliances that run heavily customized or stripped-down versions of operating system distributions. <br><br>Azure Monitor Agent versions 1.15.2 and higher now support syslog RFC formats, including Cisco Meraki, Cisco ASA, Cisco FTD, Sophos XG, Juniper Networks, Corelight Zeek, CipherTrust, NXLog, McAfee, and Common Event Format (CEF).|
+|[Azure Monitor Agent overview](./agents/agents-overview.md)|Added Azure Monitor Agent support for ARM64-based virtual machines for a number of distributions. <br><br>Azure Monitor Agent and legacy agents don't support machines and appliances that run heavily customized or stripped-down versions of operating system distributions. <br><br>Azure Monitor Agent versions 1.15.2 and higher now support Syslog RFC formats, including Cisco Meraki, Cisco ASA, Cisco FTD, Sophos XG, Juniper Networks, Corelight Zeek, CipherTrust, NXLog, McAfee, and Common Event Format (CEF).|
### Alerts | Article | Description | |||
-|[Convert ITSM actions that send events to ServiceNow to secure webhook actions](./alerts/itsm-convert-servicenow-to-webhook.md)|As of September 2022, we're starting the 3-year process of deprecating support of using ITSM actions to send events to ServiceNow. Learn how to convert ITSM actions that send events to ServiceNow to secure webhook actions|
-|[Create a new alert rule](./alerts/alerts-create-new-alert-rule.md)|Added description of all available monitoring services to create a new alert rule and alert processing rules pages. <br><br>Added support for regional processing for metric alert rules that monitor a custom metric with the scope defined as one of the supported regions. <br><br> Clarified that selecting the **Automatically resolve alerts** setting makes log alerts stateful.<|
-|[Types of Azure Monitor alerts](alerts/alerts-types.md)|Azure Database for PostgreSQL - Flexible Servers is supported for monitoring multiple resources.|
+|[Convert ITSM actions that send events to ServiceNow to Secure Webhook actions](./alerts/itsm-convert-servicenow-to-webhook.md)|As of September 2022, we're starting the three-year process of deprecating support of using ITSM actions to send events to ServiceNow. Learn how to convert ITSM actions that send events to ServiceNow to Secure Webhook actions.|
+|[Create a new alert rule](./alerts/alerts-create-new-alert-rule.md)|Added description of all available monitoring services to **Create a new alert rule** and **Alert processing rules** pages. <br><br>Added support for regional processing for metric alert rules that monitor a custom metric with the scope defined as one of the supported regions. <br><br> Clarified that selecting the **Automatically resolve alerts** setting makes log alerts stateful.|
+|[Types of Azure Monitor alerts](alerts/alerts-types.md)|Azure Database for PostgreSQL - Flexible Servers is supported for monitoring multiple resources.|
|[Upgrade legacy rules management to the current Log Alerts API from legacy Log Analytics Alert API](/previous-versions/azure/azure-monitor/alerts/alerts-log-api-switch)|The process of moving legacy log alert rules management from the legacy API to the current API is now supported by the government cloud.|
-### Application insights
+### Application Insights
| Article | Description | |||
-|[Azure Monitor OpenTelemetry-based auto-instrumentation for Java applications](./app/opentelemetry-enable.md?tabs=java)|New OpenTelemetry `@WithSpan` annotation guidance.|
-|[Capture Application Insights custom metrics with .NET and .NET Core](./app/tutorial-asp-net-custom-metrics.md)|Tutorial steps and images have been updated.|
-|[Configuration options - Azure Monitor Application Insights for Java](./app/opentelemetry-enable.md)|Connection string guidance updated.|
-|[Enable Application Insights for ASP.NET Core applications](./app/tutorial-asp-net-core.md)|Tutorial steps and images have been updated.|
-|[Enable Azure Monitor OpenTelemetry Exporter for .NET, Node.js, and Python applications (preview)](./app/opentelemetry-enable.md)|Our product feedback link at the bottom of each document has been fixed.|
+|[Azure Monitor OpenTelemetry-based auto-instrumentation for Java applications](./app/opentelemetry-enable.md?tabs=java)|Added new OpenTelemetry `@WithSpan` annotation guidance.|
+|[Capture Application Insights custom metrics with .NET and .NET Core](./app/tutorial-asp-net-custom-metrics.md)|Updated tutorial steps and images.|
+|[Configuration options: Azure Monitor Application Insights for Java](./app/opentelemetry-enable.md)|Updated connection string guidance.|
+|[Enable Application Insights for ASP.NET Core applications](./app/tutorial-asp-net-core.md)|Updated tutorial steps and images.|
+|[Enable Azure Monitor OpenTelemetry Exporter for .NET, Node.js, and Python applications (preview)](./app/opentelemetry-enable.md)|Fixed the product feedback link at the bottom of each document.|
|[Filter and preprocess telemetry in the Application Insights SDK](./app/api-filtering-sampling.md)|Added sample initializer to control which client IP gets used as part of geo-location mapping.|
-|[Java Profiler for Azure Monitor Application Insights](./app/java-standalone-profiler.md)|Our new Java Profiler was announced at Ignite. Read all about it!|
+|[Java Profiler for Azure Monitor Application Insights](./app/java-standalone-profiler.md)|Announced the new Java Profiler at Ignite. Read all about it.|
|[Release notes for Azure Web App extension for Application Insights](./app/web-app-extension-release-notes.md)|Added release notes for 2.8.44 and 2.8.43.|
-|[Resource Manager template samples for creating Application Insights resources](./app/resource-manager-app-resource.md)|Fixed inaccurate tagging of workspace-based resources as still in Preview.|
-|[Unified cross-component transaction diagnostics](./app/transaction-diagnostics.md)|A complete FAQ section is added to help troubleshoot Azure portal errors, such as "error retrieving data".|
-|[Upgrading from Application Insights Java 2.x SDK](./app/java-standalone-upgrade-from-2x.md)|Additional upgrade guidance added. Java 2.x has been deprecated.|
-|[Using Azure Monitor Application Insights with Spring Boot](./app/java-spring-boot.md)|Configuration options have been updated.|
+|[Resource Manager template samples for creating Application Insights resources](./app/resource-manager-app-resource.md)|Fixed inaccurate tagging of workspace-based resources as still in preview.|
+|[Unified cross-component transaction diagnostics](./app/transaction-diagnostics.md)|Added a FAQ section to help troubleshoot Azure portal errors like "error retrieving data."|
+|[Upgrading from Application Insights Java 2.x SDK](./app/java-standalone-upgrade-from-2x.md)|Added more upgrade guidance. Java 2.x is deprecated.|
+|[Using Azure Monitor Application Insights with Spring Boot](./app/java-spring-boot.md)|Updated configuration options.|
### Autoscale | Article | Description | ||| |[Autoscale with multiple profiles](./autoscale/autoscale-multiprofile.md)|New article: Using multiple profiles in autoscale with CLI PowerShell and templates.|
-|[Flapping in Autoscale](./autoscale/autoscale-flapping.md)|New Article: Flapping in autoscale.|
-|[Understand Autoscale settings](./autoscale/autoscale-understanding-settings.md)|Clarified how often autoscale runs.|
+|[Flapping in autoscale](./autoscale/autoscale-flapping.md)|New article: Flapping in autoscale.|
+|[Understand autoscale settings](./autoscale/autoscale-understanding-settings.md)|Clarified how often autoscale runs.|
-### Change analysis
+### Change Analysis
| Article | Description | ||| |[Troubleshoot Azure Monitor's Change Analysis](./change/change-analysis-troubleshoot.md)|Added section about partial data and how to mitigate to the troubleshooting guide.|
Visualizations|[Azure Workbooks](./visualize/workbooks-overview.md)|New video to
### Essentials | Article | Description | |||
-|[Structure of transformation in Azure Monitor (preview)](./essentials/data-collection-transformations-structure.md)|New KQL functions supported.|
+|[Structure of transformation in Azure Monitor (preview)](./essentials/data-collection-transformations-structure.md)|Added information about new KQL functions that are supported.|
-### Virtual Machines
+### Virtual machines
| Article | Description | ||| |[Migrate from Service Map to Azure Monitor VM insights](./vm/vminsights-migrate-from-service-map.md)|Added a new article with guidance for migrating from the Service Map solution to Azure Monitor VM insights.|
Visualizations|[Azure Workbooks](./visualize/workbooks-overview.md)|New video to
||| |[Network Insights](../network-watcher/network-insights-overview.md)| Onboarded the new topology experience to Network Insights in Azure Monitor.| - ### Visualizations | Article | Description | |||
-|[Access deprecated Troubleshooting guides in Azure Workbooks](./visualize/workbooks-access-troubleshooting-guide.md)|New article: Access deprecated Troubleshooting guides in Azure Workbooks.|
-
+|[Access deprecated troubleshooting guides in Azure Workbooks](./visualize/workbooks-access-troubleshooting-guide.md)|New article: Access deprecated troubleshooting guides in Azure Workbooks.|
-## August 2022
+## August 2022
### Agents | Article | Description | |||
-|[Log Analytics agent overview](agents/log-analytics-agent.md)|Restructured the Agents section and rewrote the Agents Overview article to reflect that Azure Monitor Agent is the primary agent for collecting monitoring data.|
-|[Dependency analysis in Azure Migrate Discovery and assessment - Azure Migrate](../migrate/concepts-dependency-visualization.md)|Revamped the guidance for migrating from Log Analytics Agent to Azure Monitor Agent.|
-
+|[Log Analytics agent overview](agents/log-analytics-agent.md)|Restructured the "Agents" section and rewrote the *Agents overview* article to reflect that Azure Monitor Agent is the primary agent for collecting monitoring data.|
+|[Dependency analysis in Azure Migrate Discovery and assessment - Azure Migrate](../migrate/concepts-dependency-visualization.md)|Revamped the guidance for migrating from the Log Analytics agent to Azure Monitor Agent.|
### Alerts | Article | Description | |:|:|
-|[Create Azure Monitor alert rules](alerts/alerts-create-new-alert-rule.md)|Added support for data processing in a specified region, for action groups and for metric alert rules that monitor a custom metric.|
+|[Create Azure Monitor alert rules](alerts/alerts-create-new-alert-rule.md)|Added support for data processing in a specified region, for action groups, and for metric alert rules that monitor a custom metric.|
-### Application insights
+### Application Insights
| Article | Description | |||
-|[Azure Application Insights Overview Dashboard](app/overview-dashboard.md)|Important information has been added clarifying that moving or renaming resources will break dashboards, with additional instructions on how to resolve this scenario.|
-|[Azure Application Insights override default SDK endpoints](/previous-versions/azure/azure-monitor/app/create-new-resource#override-default-endpoints)|We've clarified that endpoint modification isn't recommended and to use connection strings instead.|
-|[Continuous export of telemetry from Application Insights](/previous-versions/azure/azure-monitor/app/export-telemetry)|Important information has been added about avoiding duplicates when saving diagnostic logs in a Log Analytics workspace.|
-|[Dependency Tracking in Azure Application Insights with OpenCensus Python](app/opencensus-python-dependency.md)|Updated Django sample application and documentation in the Azure Monitor OpenCensus Python samples repository.|
-|[Incoming Request Tracking in Azure Application Insights with OpenCensus Python](app/opencensus-python-request.md)|Updated Django sample application and documentation in the Azure Monitor OpenCensus Python samples repository.|
+|[Application Insights Overview dashboard](app/overview-dashboard.md)|Added important information clarifying that moving or renaming resources breaks dashboards, with more instructions on how to resolve this scenario.|
+|[Application Insights override default SDK endpoints](/previous-versions/azure/azure-monitor/app/create-new-resource#override-default-endpoints)|Clarified that endpoint modification isn't recommended and to use connection strings instead.|
+|[Continuous export of telemetry from Application Insights](/previous-versions/azure/azure-monitor/app/export-telemetry)|Added important information about avoiding duplicates when you save diagnostic logs in a Log Analytics workspace.|
+|[Dependency tracking in Application Insights with OpenCensus Python](app/opencensus-python-dependency.md)|Updated Django sample application and documentation in the Azure Monitor OpenCensus Python samples repository.|
+|[Incoming request tracking in Application Insights with OpenCensus Python](app/opencensus-python-request.md)|Updated Django sample application and documentation in the Azure Monitor OpenCensus Python samples repository.|
|[Monitor Python applications with Azure Monitor](app/opencensus-python.md)|Updated Django sample application and documentation in the Azure Monitor OpenCensus Python samples repository.|
-|[Configuration options - Azure Monitor Application Insights for Java](app/java-standalone-config.md)|Updated connection string overrides example.|
-|[Application Insights SDK for ASP.NET Core applications](app/tutorial-asp-net-core.md)|A new tutorial with step-by-step instructions to use the Application Insights SDK with .NET Core applications.|
-|[Application Insights SDK support guidance](app/sdk-support-guidance.md)|Our SDK support guidance has been updated and clarified.|
-|[Azure Application Insights - Dependency Auto-Collection](app/asp-net-dependencies.md#dependency-auto-collection)|The latest currently supported node.js modules have been updated.|
-|[Application Insights custom metrics with .NET and .NET Core](app/tutorial-asp-net-custom-metrics.md)|A new tutorial with step-by-step instructions on how to enable custom metrics with .NET applications.|
-|[Migrate an Application Insights classic resource to a workspace-based resource](app/convert-classic-resource.md)|A comprehensive FAQ section has been added to assist with migration to workspace-based resources.|
-|[Configuration options - Azure Monitor Application Insights for Java](app/java-standalone-config.md)|This article has been fully updated for 3.4.0-BETA.|
+|[Configuration options: Azure Monitor Application Insights for Java](app/java-standalone-config.md)|Updated connection string overrides example.|
+|[Application Insights SDK for ASP.NET Core applications](app/tutorial-asp-net-core.md)|Added a new tutorial with step-by-step instructions on how to use the Application Insights SDK with .NET Core applications.|
+|[Application Insights SDK support guidance](app/sdk-support-guidance.md)|Updated and clarified the SDK support guidance.|
+|[Application Insights: Dependency autocollection](app/asp-net-dependencies.md#dependency-auto-collection)|Updated the latest currently supported node.js modules.|
+|[Application Insights custom metrics with .NET and .NET Core](app/tutorial-asp-net-custom-metrics.md)|Added a new tutorial with step-by-step instructions on how to enable custom metrics with .NET applications.|
+|[Migrate an Application Insights classic resource to a workspace-based resource](app/convert-classic-resource.md)|Added a comprehensive FAQ section to assist with migration to workspace-based resources.|
+|[Configuration options: Azure Monitor Application Insights for Java](app/java-standalone-config.md)| Updated this article for 3.4.0-BETA.|
### Autoscale | Article | Description | |||
-|[Autoscale in Microsoft Azure](autoscale/autoscale-overview.md)|Updated conceptual diagrams|
-|[Use predictive autoscale to scale out before load demands in Virtual Machine Scale Sets (preview)](autoscale/autoscale-predictive.md)|Predictive autoscale (preview) is now available in all regions|
+|[Autoscale in Microsoft Azure](autoscale/autoscale-overview.md)|Updated conceptual diagrams.|
+|[Use predictive autoscale to scale out before load demands in virtual machine scale sets (preview)](autoscale/autoscale-predictive.md)|Predictive autoscale (preview) is now available in all regions.|
-### Change analysis
+### Change Analysis
| Article | Description | |||
-|[Enable Change Analysis](change/change-analysis-enable.md)| Added note for slot-level enablement|
-|[Tutorial - Track a web app outage using Change Analysis](change/tutorial-outages.md)| Added set up steps to tutorial|
-|[Use Change Analysis in Azure Monitor to find web-app issues](change/change-analysis.md)|Updated limitations|
-|[Observability data in Azure Monitor](observability-data.md)| Added "Changes" section|
+|[Enable Change Analysis](change/change-analysis-enable.md)| Added a note for slot-level enablement.|
+|[Tutorial: Track a web app outage by using Change Analysis](change/tutorial-outages.md)| Added setup steps to the tutorial.|
+|[Use Change Analysis in Azure Monitor to find web-app issues](change/change-analysis.md)|Updated limitations.|
+|[Observability data in Azure Monitor](observability-data.md)| Added a "Changes" section.|
+ ### Containers | Article | Description | |||
-|[Monitor an Azure Kubernetes Service (AKS) cluster deployed](containers/container-insights-enable-existing-clusters.md)|Added section on using private link with Container insights.|
+|[Monitor a deployed Azure Kubernetes Service cluster](containers/container-insights-enable-existing-clusters.md)|Added section on using a private link with Container insights.|
### Essentials | Article | Description | |||
-|[Azure activity log](essentials/activity-log.md)|Added instructions for how to stop collecting activity logs using the legacy collection method.|
-|[Azure activity log insights](essentials/activity-log-insights.md)|Created a separate Activity Log Insights article in the Insights section.|
+|[Azure activity log](essentials/activity-log.md)|Added instructions for how to stop collecting activity logs by using the legacy collection method.|
+|[Azure activity log insights](essentials/activity-log-insights.md)|Created a separate activity log insights article in the "Insights" section.|
### Logs | Article | Description | |||
-|[Configure data retention and archive in Azure Monitor Logs (Preview)](logs/data-retention-archive.md)|Clarified how data retention and archiving work in Azure Monitor Logs to address repeated customer inquiries.|
+|[Configure data retention and archive in Azure Monitor Logs (preview)](logs/data-retention-archive.md)|Clarified how data retention and archiving work in Azure Monitor Logs to address repeated customer inquiries.|
-
-## July 2022
+## July 2022
### General | Article | Description | |:|:|
-|[Sources of data in Azure Monitor](data-sources.md)|Updated with Azure Monitor agent and Logs ingestion API.|
+|[Sources of data in Azure Monitor](data-sources.md)|Updated with Azure Monitor Agent and the Logs Ingestion API.|
### Agents | Article | Description | |:|:|
-|[Azure Monitor Agent overview](agents/agents-overview.md)| Restructure of the Agents section. A single Azure Monitor Agent is replacing all of Azure Monitor's legacy monitoring agents.
-|[Enable network isolation for the Azure Monitor agent](agents/azure-monitor-agent-data-collection-endpoint.md)|Rewritten to better describe configuration of network isolation.
+|[Azure Monitor Agent overview](agents/agents-overview.md)| Restructured the "Agents" section. A single Azure Monitor Agent is replacing all of Azure Monitor's legacy monitoring agents.
+|[Enable network isolation for Azure Monitor Agent](agents/azure-monitor-agent-data-collection-endpoint.md)|Rewritten to better describe configuration of network isolation.
### Alerts | Article | Description | |:|:|
-|[Azure Monitor Alerts Overview](alerts/alerts-overview.md)|Updated the logic for the time to resolve behavior in stateful log alerts.
+|[Azure Monitor alerts overview](alerts/alerts-overview.md)|Updated the logic for the time to resolve behavior in stateful log alerts.
### Application Insights | Article | Description | |:|:|
-|[Azure Monitor Application Insights Java](app/opentelemetry-enable.md?tabs=java)|OpenTelemetry-based auto-instrumentation for Java applications has an updated Supported Custom Telemetry table.
-|[Application Insights API for custom events and metrics](app/api-custom-events-metrics.md)|Clarification has been added that valueCount and itemCount have a minimum value of 1.
-|[Telemetry sampling in Azure Application Insights](app/sampling.md)|Sampling documentation has been updated to warn of the potential impact on alerting accuracy.
-|[Azure Monitor Application Insights Java (redirect to OpenTelemetry)](app/java-in-process-agent-redirect.md)|Java Auto-Instrumentation now redirects to OpenTelemetry documentation.
-|[Azure Application Insights for ASP.NET Core applications](app/asp-net-core.md)|Updated .NET Core FAQ
-|[Create a new Azure Monitor Application Insights workspace-based resource](app/create-workspace-resource.md)|We've linked out to Microsoft Insights components for more information on Properties.
-|[Application Insights SDK support guidance](app/sdk-support-guidance.md)|SDK support guidance has been updated and clarified.
-|[Azure Monitor Application Insights Java](app/opentelemetry-enable.md?tabs=java)|Example code has been updated.
-|[IP addresses used by Azure Monitor](app/ip-addresses.md)|The IP/FQDN table has been updated.
-|[Continuous export of telemetry from Application Insights](/previous-versions/azure/azure-monitor/app/export-telemetry)|The continuous export notice has been updated and clarified.
-|[Set up availability alerts with Application Insights](app/availability-alerts.md)|Custom Alert Rule and Alert Frequency sections have been added.
+|[Azure Monitor Application Insights Java](app/opentelemetry-enable.md?tabs=java)|Updated the Supported Custom Telemetry table in OpenTelemetry-based auto-instrumentation for Java applications.
+|[Application Insights API for custom events and metrics](app/api-custom-events-metrics.md)|Added clarification that valueCount and itemCount have a minimum value of 1.
+|[Telemetry sampling in Application Insights](app/sampling.md)|Updated sampling documentation to warn of the potential impact on alerting accuracy.
+|[Azure Monitor Application Insights Java (redirect to OpenTelemetry)](app/java-in-process-agent-redirect.md)|Java auto-instrumentation now redirects to OpenTelemetry documentation.
+|[Application Insights for ASP.NET Core applications](app/asp-net-core.md)|Updated .NET Core FAQ.
+|[Create a new Azure Monitor Application Insights workspace-based resource](app/create-workspace-resource.md)|Linked to Microsoft Insights components for more information on properties.
+|[Application Insights SDK support guidance](app/sdk-support-guidance.md)|Updated and clarified SDK support guidance.
+|[Azure Monitor Application Insights Java](app/opentelemetry-enable.md?tabs=java)|Updated example code.
+|[IP addresses used by Azure Monitor](app/ip-addresses.md)|Updated the IP/FQDN table.
+|[Continuous export of telemetry from Application Insights](/previous-versions/azure/azure-monitor/app/export-telemetry)|Updated and clarified the continuous export notice.
+|[Set up availability alerts with Application Insights](app/availability-alerts.md)|Added "Custom Alert Rule" and "Alert Frequency" sections.
### Autoscale | Article | Description | |:|:|
-| [How-to guide for setting up autoscale for a web app with a custom metric](autoscale/autoscale-custom-metric.md) |General rewrite to improve clarity.|
-[Overview of autoscale in Microsoft Azure](autoscale/autoscale-overview.md)|General rewrite to improve clarity.|
+| [Set up autoscale for a web app with a custom metric](autoscale/autoscale-custom-metric.md) |Rewritten to improve clarity.|
+[Overview of autoscale in Azure](autoscale/autoscale-overview.md)|Rewritten to improve clarity.|
### Containers | Article | Description | |:|:| |[Overview of Container insights](containers/container-insights-overview.md)|Added information about deprecation of Docker support.|
-|[Enable Container insights](containers/container-insights-onboard.md)|All Container insights content updated for new support of managed identity authentication using Azure Monitor agent.|
+|[Enable Container insights](containers/container-insights-onboard.md)|Updated all Container insights content for new support of managed identity authentication by using Azure Monitor Agent.|
### Essentials | Article | Description | |:|:|
-|[Tutorial - Editing Data Collection Rules](essentials/data-collection-rule-edit.md)|New article.|
-|[Data Collection Rules in Azure Monitor](essentials/data-collection-rule-overview.md)|General rewrite to improve clarity.|
-|[Data collection transformations](essentials/data-collection-transformations.md)|General rewrite to improve clarity.|
+|[Tutorial: Editing data collection rules](essentials/data-collection-rule-edit.md)|New article.|
+|[Data collection rules in Azure Monitor](essentials/data-collection-rule-overview.md)|Rewritten to improve clarity.|
+|[Data collection transformations](essentials/data-collection-transformations.md)|Rewritten to improve clarity.|
|[Data collection in Azure Monitor](essentials/data-collection.md)|New article.|
-|[How to Migrate from Diagnostic Settings Storage Retention to Azure Storage Lifecycle Policy](essentials/migrate-to-azure-storage-lifecycle-policy.md)|New article.|
+|[Migrate from diagnostic settings storage retention to Azure Storage lifecycle policy](essentials/migrate-to-azure-storage-lifecycle-policy.md)|New article.|
### Logs | Article | Description | |:|:|
-|[Logs ingestion API in Azure Monitor (Preview)](logs/logs-ingestion-api-overview.md)|Custom logs API renamed to Logs ingestion API.
-|[Tutorial - Send data to Azure Monitor Logs using REST API (Resource Manager templates)](logs/tutorial-logs-ingestion-api.md)|Custom logs API renamed to Logs ingestion API.
-|[Tutorial - Send data to Azure Monitor Logs using REST API (Azure portal)](logs/tutorial-logs-ingestion-portal.md)|Custom logs API renamed to Logs ingestion API.
+|[Logs Ingestion API in Azure Monitor (preview)](logs/logs-ingestion-api-overview.md)|Custom logs API renamed to Logs Ingestion API.
+|[Tutorial: Send data to Azure Monitor Logs by using the REST API (Resource Manager templates)](logs/tutorial-logs-ingestion-api.md)|Custom logs API renamed to Logs Ingestion API.
+|[Tutorial: Send data to Azure Monitor Logs by using the REST API (Azure portal)](logs/tutorial-logs-ingestion-portal.md)|Custom logs API renamed to Logs Ingestion API.
-### Virtual Machines
+### Virtual machines
| Article | Description | |:|:|
-|[What is VM insights?](vm/vminsights-overview.md)|All VM insights content updated for new support of Azure Monitor agent.
-
+|[What is VM insights?](vm/vminsights-overview.md)|Updated all VM insights content for new support of Azure Monitor Agent.
-## June 2022
+## June 2022
### General | Article | Description | |:|:|
-| [Tutorial - Editing Data Collection Rules](essentials/data-collection-rule-edit.md) | New article|
-
+| [Tutorial: Editing data collection rules](essentials/data-collection-rule-edit.md) | New article.|
### Application Insights | Article | Description | |:|:|
-| [Application Insights logging with .NET](app/ilogger.md) | Connection string sample code has been added.|
+| [Application Insights logging with .NET](app/ilogger.md) | Added connection string sample code.|
| [Application Insights SDK support guidance](app/sdk-support-guidance.md) | Updated SDK supportability guidance. |
-| [Azure AD authentication for Application Insights](app/azure-ad-authentication.md) | Azure AD authenticated telemetry ingestion has been reached general availability.|
-| [Azure Application Insights for JavaScript web apps](app/javascript.md) | Our Java on-premises page has been retired and redirected to [Azure Monitor OpenTelemetry-based auto-instrumentation for Java applications](app/opentelemetry-enable.md?tabs=java).|
-| [Azure Application Insights Telemetry Data Model - Telemetry Context](app/data-model-complete.md#context) | Clarified that Anonymous User ID is simply User.Id for easy selection in Intellisense.|
+| [Azure AD authentication for Application Insights](app/azure-ad-authentication.md) | Azure AD authenticated telemetry ingestion reached general availability.|
+| [Application Insights for JavaScript web apps](app/javascript.md) | Our Java on-premises page is retired and redirected to [Azure Monitor OpenTelemetry-based auto-instrumentation for Java applications](app/opentelemetry-enable.md?tabs=java).|
+| [Application Insights Telemetry Data Model: Telemetry context](app/data-model-complete.md#context) | Clarified that Anonymous User ID is simply User.Id for easy selection in IntelliSense.|
| [Continuous export of telemetry from Application Insights](/previous-versions/azure/azure-monitor/app/export-telemetry) | On February 29, 2024, continuous export will be deprecated as part of the classic Application Insights deprecation.|
-| [Dependency Tracking in Azure Application Insights](app/asp-net-dependencies.md) | The Event Hubs Client SDK and ServiceBus Client SDK information has been updated.|
-| [Monitor Azure app services performance .NET Core](app/azure-web-apps-net-core.md) | Updated Linux troubleshooting guidance. |
-| [Performance counters in Application Insights](app/performance-counters.md) | A prerequisite section has been added to ensure performance counter data is accessible.|
+| [Dependency tracking in Application Insights](app/asp-net-dependencies.md) | Updated the Azure Event Hubs Client SDK and Azure Service Bus Client SDK information.|
+| [Monitor Azure App Service performance and .NET Core](app/azure-web-apps-net-core.md) | Updated Linux troubleshooting guidance. |
+| [Performance counters in Application Insights](app/performance-counters.md) | Added a prerequisite section to ensure performance counter data is accessible.|
### Agents | Article | Description | |:|:|
-| [Collect text and IIS logs with Azure Monitor agent (preview)](agents/data-collection-text-log.md) | Added troubleshooting section.|
-| [Tools for migrating to Azure Monitor Agent from legacy agents](agents/azure-monitor-agent-migration-tools.md) | New article that explains how to install and use tools for migrating from legacy agents to the new Azure Monitor agent (AMA).|
+| [Collect text and IIS logs with Azure Monitor Agent (preview)](agents/data-collection-text-log.md) | Added "Troubleshooting" section.|
+| [Tools for migrating to Azure Monitor Agent from legacy agents](agents/azure-monitor-agent-migration-tools.md) | New article: Explains how to install and use tools for migrating from legacy agents to the new Azure Monitor Agent.|
### Visualizations
-Azure Monitor Workbooks documentation previously resided on an external GitHub repository. We've migrated all Azure Workbooks content to the same repo as all other Azure Monitor content.
-
+Azure Monitor Workbooks documentation previously resided on an external GitHub repository. We've migrated all Azure Workbooks content to the same repo as all other Azure Monitor content.
-
-## May 2022
+## May 2022
### General | Article | Description | |:|:|
-| [Azure Monitor cost and usage](usage-estimated-costs.md) | Added standard web tests to table<br>Added explanation of billable GB calculation |
-| [Azure Monitor overview](overview.md) | Updated overview diagram |
+| [Azure Monitor cost and usage](usage-estimated-costs.md) | Added standard web tests to table.<br>Added explanation of billable GB calculation. |
+| [Azure Monitor overview](overview.md) | Updated overview diagram. |
### Agents | Article | Description | |:|:|
-| [Azure Monitor agent extension versions](agents/azure-monitor-agent-extension-versions.md) | Update to latest extension version |
-| [Azure Monitor agent overview](agents/azure-monitor-agent-overview.md) | Added supported resource types |
-| [Collect text and IIS logs with Azure Monitor agent (preview)](agents/data-collection-text-log.md) | Corrected error in data collection rule |
-| [Overview of the Azure monitoring agents](agents/agents-overview.md) | Added new OS supported for agent |
-| [Resource Manager template samples for agents](agents/resource-manager-agent.md) | Added Bicep examples |
-| [Resource Manager template samples for data collection rules](agents/resource-manager-data-collection-rules.md) | Fixed bug in sample parameter file |
-| [Rsyslog data not uploaded due to Full Disk space issue on AMA Linux Agent](agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md) | New article |
-| [Troubleshoot the Azure Monitor agent on Linux virtual machines and scale sets](agents/azure-monitor-agent-troubleshoot-linux-vm.md) | New article |
-| [Troubleshoot the Azure Monitor agent on Windows Arc-enabled server](agents/azure-monitor-agent-troubleshoot-windows-arc.md) | New article |
-| [Troubleshoot the Azure Monitor agent on Windows virtual machines and scale sets](agents/azure-monitor-agent-troubleshoot-windows-vm.md) | New article |
+| [Azure Monitor Agent extension versions](agents/azure-monitor-agent-extension-versions.md) | Updated to latest extension version. |
+| [Azure Monitor Agent overview](agents/azure-monitor-agent-overview.md) | Added supported resource types. |
+| [Collect text and IIS logs with Azure Monitor Agent (preview)](agents/data-collection-text-log.md) | Corrected error in data collection rule. |
+| [Overview of the Azure monitoring agents](agents/agents-overview.md) | Added new OS supported for agent. |
+| [Resource Manager template samples for agents](agents/resource-manager-agent.md) | Added Bicep examples. |
+| [Resource Manager template samples for data collection rules](agents/resource-manager-data-collection-rules.md) | Fixed bug in sample parameter file. |
+| [Rsyslog data not uploaded due to Full Disk space issue on Azure Monitor Agent Linux Agent](agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md) | New article. |
+| [Troubleshoot the Azure Monitor Agent on Linux virtual machines and scale sets](agents/azure-monitor-agent-troubleshoot-linux-vm.md) | New article. |
+| [Troubleshoot the Azure Monitor Agent on Windows Arc-enabled server](agents/azure-monitor-agent-troubleshoot-windows-arc.md) | New article. |
+| [Troubleshoot the Azure Monitor Agent on Windows virtual machines and scale sets](agents/azure-monitor-agent-troubleshoot-windows-vm.md) | New article. |
### Alerts | Article | Description | |:|:|
-| [IT Service Management Connector | Secure Webhook in Azure Monitor | Azure Configurations](alerts/itsm-connector-secure-webhook-connections-azure-configuration.md) | Added the workflow for ITSM management and removed all references to SCSM. |
-| [Overview of Azure Monitor Alerts](alerts/alerts-overview.md) | Complete rewrite |
-| [Resource Manager template samples for log query alerts](alerts/resource-manager-alerts-log.md) | Bicep samples for alerting have been added to the Resource Manager template samples articles. |
+| [Configure Azure to connect ITSM tools by using Secure Webhook](alerts/itsm-connector-secure-webhook-connections-azure-configuration.md) | Added the workflow for ITSM management and removed all references to System Center Service Manager. |
+| [Overview of Azure Monitor Alerts](alerts/alerts-overview.md) | Complete rewrite. |
+| [Resource Manager template samples for log query alerts](alerts/resource-manager-alerts-log.md) | Added Bicep samples for alerting to the Resource Manager template samples articles. |
| [Supported resources for metric alerts in Azure Monitor](alerts/alerts-metric-near-real-time.md) | Added a newly supported resource type. | ### Application Insights | Article | Description | |:|:|
-| [Application Map in Azure Application Insights](app/app-map.md) | Application Maps Intelligent View feature |
-| [Azure Application Insights for ASP.NET Core applications](app/asp-net-core.md) | telemetry.Flush() guidance is now available. |
+| [Application Map in Application Insights](app/app-map.md) | Application Maps Intelligent View feature. |
+| [Application Insights for ASP.NET Core applications](app/asp-net-core.md) | The `telemetry.Flush()` guidance is now available. |
| [Diagnose with Live Metrics Stream](app/live-stream.md) | Updated information on using unsecure control channel. |
-| [Migrate an Azure Monitor Application Insights classic resource to a workspace-based resource](app/convert-classic-resource.md) | Schema change documentation is now available here. |
-| [Profile production apps in Azure with Application Insights Profiler](profiler/profiler-overview.md) | Profiler documentation now has a new home in the table of contents. |
+| [Migrate an Azure Monitor Application Insights classic resource to a workspace-based resource](app/convert-classic-resource.md) | Schema change documentation is now available. |
+| [Profile production apps in Azure with Application Insights Profiler](profiler/profiler-overview.md) | Profiler documentation now has a new home in the TOC. |
+
+All references to unsupported versions of .NET and .NET CORE are scrubbed from Application Insights product documentation. See [.NET and .NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
-All references to unsupported versions of .NET and .NET CORE have been scrubbed from Application Insights product documentation. See [.NET and >NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core)
### Change Analysis | Article | Description | |:|:|
-| [Navigate to a change using custom filters in Change Analysis](change/change-analysis-custom-filters.md) | New article |
-| [Pin and share a Change Analysis query to the Azure dashboard](change/change-analysis-query.md) | New article |
-| [Use Change Analysis in Azure Monitor to find web-app issues](change/change-analysis.md) | Added details enabling for web app in-guest changes |
+| [Navigate to a change by using custom filters in Change Analysis](change/change-analysis-custom-filters.md) | New article. |
+| [Pin and share a Change Analysis query to the Azure dashboard](change/change-analysis-query.md) | New article. |
+| [Use Change Analysis in Azure Monitor to find web app issues](change/change-analysis.md) | Added details for enabling web app in-guest changes. |
+ ### Containers | Article | Description | |:|:|
-| [Configure ContainerLogv2 schema (preview) for Container Insights](containers/container-insights-logging-v2.md) | New article describing new schema for container logs |
-| [Enable Container insights](containers/container-insights-onboard.md) | General rewrite to improve clarity |
-| [Resource Manager template samples for Container insights](containers/resource-manager-container-insights.md) | Added Bicep examples |
+| [Configure ContainerLogv2 schema (preview) for Container insights](containers/container-insights-logging-v2.md) | New article: Describes new schema for container logs. |
+| [Enable Container insights](containers/container-insights-onboard.md) | Rewritten to improve clarity. |
+| [Resource Manager template samples for Container insights](containers/resource-manager-container-insights.md) | Added Bicep examples. |
### Insights | Article | Description |
All references to unsupported versions of .NET and .NET CORE have been scrubbed
| Article | Description | |:|:|
-| [Azure Monitor customer-managed key](logs/customer-managed-keys.md) | Update limitations and constraint. |
-| [Design a Log Analytics workspace architecture](logs/workspace-design.md) | Complete rewrite to better describe decision criteria and include Sentinel considerations |
-| [Manage access to Log Analytics workspaces](logs/manage-access.md) | Consolidated and rewrote all content on configuring workspace access |
-| [Restore logs in Azure Monitor (Preview)](logs/restore.md) | Documented new Log Analytics table management configuration UI, which lets you configure a table's log plan and archive and retention policies. |
+| [Azure Monitor customer-managed key](logs/customer-managed-keys.md) | Updated limitations and constraint. |
+| [Design a Log Analytics workspace architecture](logs/workspace-design.md) | Rewritten to better describe decision criteria and include Microsoft Sentinel considerations. |
+| [Manage access to Log Analytics workspaces](logs/manage-access.md) | Consolidated and rewrote all content on configuring workspace access. |
+| [Restore logs in Azure Monitor (preview)](logs/restore.md) | Documented new Log Analytics table management configuration UI, which lets you configure a table's log plan and archive and retention policies. |
-### Virtual Machines
+### Virtual machines
| Article | Description | |:|:|
-| [Migrate from VM insights guest health (preview) to Azure Monitor log alerts](vm/vminsights-health-migrate.md) | New article describing process to replace VM guest health with alert rules |
-| [VM insights guest health (preview)](vm/vminsights-health-overview.md) | Added deprecation statement |
+| [Migrate from VM insights guest health (preview) to Azure Monitor log alerts](vm/vminsights-health-migrate.md) | New article: Describes process to replace VM guest health with alert rules. |
+| [VM insights guest health (preview)](vm/vminsights-health-overview.md) | Added deprecation statement. |
azure-netapp-files Azure Government https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-netapp-files/azure-government.md
ms.assetid:
na+ Last updated 03/08/2023
azure-netapp-files Azure Netapp Files Resize Capacity Pools Or Volumes https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md
ms.assetid:
na+ Last updated 02/21/2023
azure-netapp-files Azure Netapp Files Sdk Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-netapp-files/azure-netapp-files-sdk-cli.md
ms.assetid:
na+ Last updated 09/30/2022
azure-netapp-files Monitor Volume Capacity https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-netapp-files/monitor-volume-capacity.md
ms.assetid:
na+ Last updated 09/30/2022
azure-portal Azure Portal Dashboards Create Programmatically https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-portal/azure-portal-dashboards-create-programmatically.md
Title: Programmatically create Azure Dashboards description: Use a dashboard in the Azure portal as a template to programmatically create Azure Dashboards. Includes JSON reference. + Last updated 11/18/2021
azure-portal Quick Create Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-portal/quick-create-bicep.md
Title: Create an Azure portal dashboard by using a Bicep file description: Learn how to create an Azure portal dashboard by using a Bicep file. -+ Last updated 09/15/2022
azure-portal Quick Create Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-portal/quick-create-template.md
Title: Create an Azure portal dashboard by using an Azure Resource Manager template description: Learn how to create an Azure portal dashboard by using an Azure Resource Manager template. -+ Last updated 09/16/2022
azure-resource-manager Add Template To Azure Pipelines https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/add-template-to-azure-pipelines.md
Title: CI/CD with Azure Pipelines and Bicep files description: In this quickstart, you learn how to configure continuous integration in Azure Pipelines by using Bicep files. It shows how to use an Azure CLI task to deploy a Bicep file. + Last updated 01/10/2023
azure-resource-manager Best Practices https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/best-practices.md
description: Describes practices to follow when creating your Bicep files so the
+ Last updated 05/16/2022 # Best practices for Bicep
azure-resource-manager Bicep Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-cli.md
Title: Bicep CLI commands and overview description: Describes the commands that you can use in the Bicep CLI. These commands include building Azure Resource Manager templates from Bicep. -+ Last updated 01/10/2023
azure-resource-manager Bicep Config Linter https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-config-linter.md
Title: Linter settings for Bicep config description: Describes how to customize configuration values for the Bicep linter + Last updated 03/16/2023
azure-resource-manager Bicep Config Modules https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-config-modules.md
Title: Module setting for Bicep config description: Describes how to customize configuration values for modules in Bicep deployments. + Last updated 01/18/2023
azure-resource-manager Bicep Config https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-config.md
Title: Bicep config file description: Describes the configuration file for your Bicep deployments + Last updated 02/21/2023
azure-resource-manager Bicep Extensibility Kubernetes Provider https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md
Title: Bicep extensibility Kubernetes provider description: Learn how to Bicep Kubernetes provider to deploy .NET applications to Azure Kubernetes Service clusters. + Last updated 02/21/2023
From Visual Studio Code, you can import Kubernetes manifest files to create Bice
## Next steps - [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep extensibility Kubernetes provider](../../aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md)-
azure-resource-manager Bicep Functions Any https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-any.md
Title: Bicep functions - any description: Describes the any function that is available in Bicep to convert types. + Last updated 09/09/2021
For more complex uses of the `any()` function, see the following examples:
* [Child resources that require a specific names](https://github.com/Azure/bicep/blob/62eb8109ae51d4ee4a509d8697ef9c0848f36fe4/docs/examples/201/api-management-create-all-resources/main.bicep#L247) * [A resource property not defined in the resource's type, even though it exists](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.insights/log-analytics-with-solutions-and-diagnostics/main.bicep#L26)-
azure-resource-manager Bicep Functions Array https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-array.md
Title: Bicep functions - arrays
description: Describes the functions to use in a Bicep file for working with arrays. + Last updated 12/09/2022
azure-resource-manager Bicep Functions Date https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-date.md
description: Describes the functions to use in a Bicep file to work with dates.
+ Last updated 05/03/2022
azure-resource-manager Bicep Functions Deployment https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-deployment.md
description: Describes the functions to use in a Bicep file to retrieve deployme
+ Last updated 11/09/2022
azure-resource-manager Bicep Functions Files https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-files.md
Title: Bicep functions - files description: Describes the functions to use in a Bicep file to load content from a file. + Last updated 10/10/2022
azure-resource-manager Bicep Functions Lambda https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-lambda.md
Title: Bicep functions - lambda
description: Describes the lambda functions to use in a Bicep file. + Last updated 03/15/2023- # Lambda functions for Bicep
azure-resource-manager Bicep Functions Logical https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-logical.md
description: Describes the functions to use in a Bicep file to determine logical
+ Last updated 01/30/2023
azure-resource-manager Bicep Functions Numeric https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-numeric.md
description: Describes the functions to use in a Bicep file to work with numbers
+ Last updated 09/30/2021
azure-resource-manager Bicep Functions Object https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-object.md
description: Describes the functions to use in a Bicep file for working with obj
+ Last updated 03/19/2023
azure-resource-manager Bicep Functions Resource https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-resource.md
description: Describes the functions to use in a Bicep file to retrieve values a
+ Last updated 09/09/2022
azure-resource-manager Bicep Functions Scope https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-scope.md
Title: Bicep functions - scopes description: Describes the functions to use in a Bicep file to retrieve values about deployment scopes. + Last updated 11/17/2022
azure-resource-manager Bicep Functions String https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions-string.md
description: Describes the functions to use in a Bicep file to work with strings
+ Last updated 12/09/2022
azure-resource-manager Bicep Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-functions.md
Title: Bicep functions description: Describes the functions to use in a Bicep file to retrieve values, work with strings and numerics, and retrieve deployment information. + Last updated 07/05/2022
azure-resource-manager Bicep Import Providers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/bicep-import-providers.md
Title: Import Bicep extensibility providers description: Describes how to import Bicep extensibility providers. + Last updated 02/21/2023
azure-resource-manager Child Resource Name Type https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/child-resource-name-type.md
description: Describes how to set the name and type for child resources in Bicep
+ Last updated 09/13/2021
azure-resource-manager Compare Template Syntax https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/compare-template-syntax.md
description: Compares Azure Resource Manager templates developed with JSON and B
+ Last updated 04/26/2022 # Comparing JSON and Bicep for templates
azure-resource-manager Conditional Resource Deployment https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/conditional-resource-deployment.md
description: Describes how to conditionally deploy a resource in Bicep.
+ Last updated 07/30/2021
azure-resource-manager Contribute https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/contribute.md
description: Describes how to submit open source contributions to Bicep.
+ Last updated 03/27/2022
azure-resource-manager Data Types https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/data-types.md
Title: Data types in Bicep description: Describes the data types that are available in Bicep + Last updated 01/10/2023
azure-resource-manager Decompile https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/decompile.md
Title: Decompile ARM template JSON to Bicep
description: Describes commands for decompiling Azure Resource Manager templates to Bicep files. Last updated 03/03/2023-+ # Decompiling ARM template JSON to Bicep
azure-resource-manager Deploy Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-cli.md
Last updated 07/08/2022-+ # How to deploy resources with Bicep and Azure CLI
azure-resource-manager Deploy Cloud Shell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-cloud-shell.md
description: Use Azure Resource Manager and Azure Cloud Shell to deploy resource
+ Last updated 06/01/2021
azure-resource-manager Deploy Github Actions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-github-actions.md
Last updated 08/22/2022-+ # Quickstart: Deploy Bicep files by using GitHub Actions
azure-resource-manager Deploy Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-powershell.md
description: Use Azure Resource Manager and Azure PowerShell to deploy resources
+ Last updated 08/05/2022
azure-resource-manager Deploy To Management Group https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-to-management-group.md
Title: Use Bicep to deploy resources to management group description: Describes how to create a Bicep file that deploys resources at the management group scope. + Last updated 11/22/2021
azure-resource-manager Deploy To Resource Group https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-to-resource-group.md
Title: Use Bicep to deploy resources to resource groups description: Describes how to deploy resources in a Bicep file. It shows how to target more than one resource group. + Last updated 08/05/2022
azure-resource-manager Deploy To Subscription https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-to-subscription.md
Title: Use Bicep to deploy resources to subscription description: Describes how to create a Bicep file that deploys resources to the Azure subscription scope. It shows how to create a resource group. + Last updated 11/22/2021
azure-resource-manager Deploy To Tenant https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-to-tenant.md
Title: Use Bicep to deploy resources to tenant description: Describes how to deploy resources at the tenant scope in a Bicep file. + Last updated 11/22/2021
azure-resource-manager Deploy Vscode https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-vscode.md
description: Deploy Bicep files from Visual Studio Code.
+ Last updated 12/06/2022
azure-resource-manager Deploy What If https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deploy-what-if.md
Title: Bicep deployment what-if
description: Determine what changes will happen to your resources before deploying a Bicep file. + Last updated 02/15/2023
azure-resource-manager Deployment Script Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/deployment-script-bicep.md
description: use deployment scripts in Bicep.
+ Last updated 01/25/2023
azure-resource-manager Existing Resource https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/existing-resource.md
Title: Reference existing resource in Bicep description: Describes how to reference a resource that already exists. + Last updated 02/04/2022
azure-resource-manager File https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/file.md
Title: Bicep file structure and syntax description: Describes the structure and properties of a Bicep file using declarative syntax. + Last updated 07/06/2022
azure-resource-manager Install https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/install.md
Title: Set up Bicep development and deployment environments
description: How to configure Bicep development and deployment environments Last updated 03/17/2023-+ # Install Bicep tools
azure-resource-manager Installation Troubleshoot https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/installation-troubleshoot.md
Title: Troubleshoot problems with Bicep installation description: How to resolve errors and problems with your Bicep installation. + Last updated 12/15/2021
azure-resource-manager Key Vault Parameter https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/key-vault-parameter.md
description: Shows how to pass a secret from a key vault as a parameter during B
-+ Last updated 06/18/2021
azure-resource-manager Learn Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/learn-bicep.md
Title: Learn modules for Bicep description: Provides an overview of the Learn modules for Bicep. + Last updated 09/05/2022 # Learn modules for Bicep
azure-resource-manager Linter Rule Admin Username Should Not Be Literal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-admin-username-should-not-be-literal.md
Title: Linter rule - admin user name should not be literal description: Linter rule - admin user name should not be a literal + Last updated 11/18/2021
azure-resource-manager Linter Rule Artifacts Parameters https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-artifacts-parameters.md
Title: Linter rule - artifacts parameters description: Linter rule - artifacts parameters + Last updated 08/05/2022
azure-resource-manager Linter Rule Decompiler Cleanup https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-decompiler-cleanup.md
Title: Linter rule - decompiler cleanup description: Linter rule - decompiler cleanup + Last updated 02/10/2023
azure-resource-manager Linter Rule Explicit Values For Loc Params https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-explicit-values-for-loc-params.md
Title: Linter rule - use explicit values for module location parameters description: Linter rule - use explicit values for module location parameters + Last updated 1/6/2022
azure-resource-manager Linter Rule Max Outputs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-max-outputs.md
Title: Linter rule - max outputs description: Linter rule - max outputs. + Last updated 02/03/2022
azure-resource-manager Linter Rule Max Parameters https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-max-parameters.md
Title: Linter rule - max parameters description: Linter rule - max parameters. + Last updated 02/03/2022
azure-resource-manager Linter Rule Max Resources https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-max-resources.md
Title: Linter rule - max resources description: Linter rule - max resources. + Last updated 02/03/2022
azure-resource-manager Linter Rule Max Variables https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-max-variables.md
Title: Linter rule - max variables description: Linter rule - max variables. + Last updated 02/03/2022
azure-resource-manager Linter Rule No Hardcoded Environment Urls https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-no-hardcoded-environment-urls.md
Title: Linter rule - no hardcoded environment URL description: Linter rule - no hardcoded environment URL + Last updated 11/18/2021
azure-resource-manager Linter Rule No Hardcoded Location https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-no-hardcoded-location.md
Title: Linter rule - no hardcoded locations description: Linter rule - no hardcoded locations + Last updated 02/10/2023
azure-resource-manager Linter Rule No Loc Expr Outside Params https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md
Title: Linter rule - no location expressions outside of parameter default values description: Linter rule - no location expressions outside of parameter default values + Last updated 8/30/2022
azure-resource-manager Linter Rule No Unnecessary Dependson https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-no-unnecessary-dependson.md
Title: Linter rule - no unnecessary dependsOn entries description: Linter rule - no unnecessary dependsOn entries + Last updated 02/10/2023
azure-resource-manager Linter Rule No Unused Existing Resources https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-no-unused-existing-resources.md
Title: Linter rule - no unused existing resources description: Linter rule - no unused existing resources + Last updated 02/10/2023
azure-resource-manager Linter Rule No Unused Parameters https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-no-unused-parameters.md
Title: Linter rule - no unused parameters description: Linter rule - no unused parameters + Last updated 02/10/2023
azure-resource-manager Linter Rule No Unused Variables https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-no-unused-variables.md
Title: Linter rule - no unused variables description: Linter rule - no unused variables + Last updated 02/10/2023
azure-resource-manager Linter Rule Outputs Should Not Contain Secrets https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-outputs-should-not-contain-secrets.md
Title: Linter rule - outputs should not contain secrets description: Linter rule - outputs should not contain secrets + Last updated 02/10/2023
azure-resource-manager Linter Rule Prefer Interpolation https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-prefer-interpolation.md
Title: Linter rule - prefer interpolation description: Linter rule - prefer interpolation + Last updated 02/10/2023
azure-resource-manager Linter Rule Prefer Unquoted Property Names https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-prefer-unquoted-property-names.md
Title: Linter rule - prefer unquoted property names description: Linter rule - prefer unquoted property names + Last updated 02/10/2023
azure-resource-manager Linter Rule Protect Commandtoexecute Secrets https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-protect-commandtoexecute-secrets.md
Title: Linter rule - use protectedSettings for commandToExecute secrets description: Linter rule - use protectedSettings for commandToExecute secrets + Last updated 12/17/2021
azure-resource-manager Linter Rule Secure Parameter Default https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-secure-parameter-default.md
Title: Linter rule - secure parameter default description: Linter rule - secure parameter default + Last updated 02/10/2023
azure-resource-manager Linter Rule Secure Params In Nested Deploy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-secure-params-in-nested-deploy.md
Title: Linter rule - secure params in nested deploy description: Linter rule - secure params in nested deploy + Last updated 09/22/2022
azure-resource-manager Linter Rule Secure Secrets In Parameters https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-secure-secrets-in-parameters.md
Title: Linter rule - secure secrets in parameters description: Linter rule - secure secrets in parameters + Last updated 02/10/2023
azure-resource-manager Linter Rule Simplify Interpolation https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-simplify-interpolation.md
Title: Linter rule - simplify interpolation description: Linter rule - simplify interpolation + Last updated 02/10/2023
azure-resource-manager Linter Rule Use Parent Property https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-use-parent-property.md
Title: Linter rule - use parent property description: Linter rule - use parent property + Last updated 01/30/2023
azure-resource-manager Linter Rule Use Recent Api Versions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-use-recent-api-versions.md
Title: Linter rule - use recent API versions description: Linter rule - use recent API versions + Last updated 02/13/2023
azure-resource-manager Linter Rule Use Resource Id Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-use-resource-id-functions.md
Title: Linter rule - use resource ID functions description: Linter rule - use resource ID functions + Last updated 09/23/2022
azure-resource-manager Linter Rule Use Stable Resource Identifier https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-use-stable-resource-identifier.md
Title: Linter rule - use stable resource identifier description: Linter rule - use stable resource identifier + Last updated 08/03/2022
azure-resource-manager Linter Rule Use Stable Vm Image https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter-rule-use-stable-vm-image.md
Title: Linter rule - use stable VM image description: Linter rule - use stable VM image + Last updated 12/15/2021
resource vm 'Microsoft.Compute/virtualMachines@2020-06-01' = {
## Next steps
-For more information about the linter, see [Use Bicep linter](./linter.md).
+For more information about the linter, see [Use Bicep linter](./linter.md).
azure-resource-manager Linter https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/linter.md
Title: Use Bicep linter description: Learn how to use Bicep linter. + Last updated 03/16/2023
azure-resource-manager Loops https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/loops.md
Title: Iterative loops in Bicep description: Use loops to iterate over collections in Bicep + Last updated 12/09/2022
azure-resource-manager Migrate https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/migrate.md
description: Describes the recommended workflow when migrating Azure resources a
+ Last updated 03/03/2023 # Migrate to Bicep
azure-resource-manager Modules https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/modules.md
Title: Bicep modules description: Describes how to define a module in a Bicep file, and how to use module scopes. + Last updated 11/04/2022
azure-resource-manager Msbuild Bicep File https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/msbuild-bicep-file.md
Title: Use MSBuild to convert Bicep to JSON
description: Use MSBuild to convert a Bicep file to Azure Resource Manager template (ARM template) JSON. Last updated 09/26/2022 + - # Customer intent: As a developer I want to convert Bicep files to Azure Resource Manager template (ARM template) JSON in an MSBuild pipeline.
azure-resource-manager Operators Access https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/operators-access.md
description: Describes Bicep resource access operator and property access operat
+ Last updated 09/10/2021
azure-resource-manager Operators Comparison https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/operators-comparison.md
description: Describes Bicep comparison operators that compare values.
+ Last updated 09/07/2021
azure-resource-manager Operators Logical https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/operators-logical.md
description: Describes Bicep logical operators that evaluate conditions.
+ Last updated 12/12/2022
azure-resource-manager Operators Numeric https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/operators-numeric.md
description: Describes Bicep numeric operators that calculate values.
+ Last updated 06/01/2021
azure-resource-manager Operators https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/operators.md
description: Describes the Bicep operators available for Azure Resource Manager
+ Last updated 09/10/2021
azure-resource-manager Outputs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/outputs.md
Title: Outputs in Bicep description: Describes how to define output values in Bicep + Last updated 09/28/2022
azure-resource-manager Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/overview.md
Title: Bicep language for deploying Azure resources description: Describes the Bicep language for deploying infrastructure to Azure. It provides an improved authoring experience over using JSON to develop templates. + Last updated 11/03/2022
azure-resource-manager Parameter Files https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/parameter-files.md
description: Create parameter file for passing in values during deployment of a
+ Last updated 11/14/2022
azure-resource-manager Parameters https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/parameters.md
description: Describes how to define parameters in a Bicep file.
+ Last updated 09/28/2022
azure-resource-manager Patterns Configuration Set https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/patterns-configuration-set.md
description: Describes the configuration set pattern.
+ Last updated 11/30/2021 # Configuration set pattern
azure-resource-manager Patterns Logical Parameter https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/patterns-logical-parameter.md
description: Describes the logical parameter pattern.
+ Last updated 12/01/2021 # Logical parameter pattern
azure-resource-manager Patterns Name Generation https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/patterns-name-generation.md
description: Describes the name generation pattern.
+ Last updated 12/01/2021 # Name generation pattern
azure-resource-manager Patterns Shared Variable File https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/patterns-shared-variable-file.md
description: Describes the shared variable file pattern.
+ Last updated 07/01/2022 # Shared variable file pattern
azure-resource-manager Private Module Registry https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/private-module-registry.md
Title: Create private registry for Bicep module description: Learn how to set up an Azure container registry for private Bicep modules + Last updated 01/10/2023
azure-resource-manager Quickstart Create Bicep Use Visual Studio Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md
Title: Create Bicep files - Visual Studio Code
description: Use Visual Studio Code and the Bicep extension to Bicep files for deploy Azure resources Last updated 11/03/2022 -+ #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio Code to create and edit Bicep files, so I can use them to deploy Azure resources.
azure-resource-manager Quickstart Create Bicep Use Visual Studio https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md
Title: Create Bicep files - Visual Studio
description: Use Visual Studio and the Bicep extension to create Bicep files for deploy Azure resources. Last updated 09/12/2022 -+ #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio to create and edit Bicep files, so I can use them to deploy Azure resources.
azure-resource-manager Quickstart Create Template Specs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/quickstart-create-template-specs.md
Title: Create and deploy a template spec with Bicep
description: Learn how to use Bicep to create and deploy a template spec to a resource group in your Azure subscription. Then, use a template spec to deploy Azure resources. Last updated 03/30/2022 -+ # Customer intent: As a developer I want to use Bicep to create and share deployment templates so that other people in my organization can deploy Microsoft Azure resources.
azure-resource-manager Quickstart Loops https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/quickstart-loops.md
Title: Create multiple resource instances in Bicep
description: Use different methods to create multiple resource instances in Bicep Last updated 12/06/2021 -+ #Customer intent: As a developer new to Azure deployment, I want to learn how to create multiple resources in Bicep.
azure-resource-manager Quickstart Private Module Registry https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/quickstart-private-module-registry.md
Title: Publish modules to private module registry
description: Publish Bicep modules to private module registry and use the modules. Last updated 04/01/2022 -+ #Customer intent: As a developer new to Azure deployment, I want to learn how to publish Bicep modules to private module registry.
azure-resource-manager Resource Declaration https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/resource-declaration.md
Title: Declare resources in Bicep description: Describes how to declare resources to deploy in Bicep. + Last updated 02/21/2023
azure-resource-manager Resource Dependencies https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/resource-dependencies.md
Title: Set resource dependencies in Bicep description: Describes how to specify the order resources are deployed. + Last updated 10/05/2022
azure-resource-manager Scenarios Monitoring https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/scenarios-monitoring.md
description: Describes how to create monitoring resources by using Bicep.
+ Last updated 07/01/2022 # Create monitoring resources by using Bicep
In this example, a *scale out* condition for the App Service plan based on the a
- [Microsoft.Portal/dashboards](/azure/templates/microsoft.portal/dashboards?tabs=bicep) - [Microsoft.Insights/activityLogAlerts](/azure/templates/microsoft.insights/activitylogalerts?tabs=bicep) - [Microsoft.AlertsManagement/smartDetectorAlertRules](/azure/templates/microsoft.alertsmanagement/smartdetectoralertrules?tabs=bicep).
- - [Microsoft.Insights/autoscaleSettings](/azure/templates/microsoft.insights/autoscalesettings?tabs=bicep)
+ - [Microsoft.Insights/autoscaleSettings](/azure/templates/microsoft.insights/autoscalesettings?tabs=bicep)
azure-resource-manager Scenarios Rbac https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/scenarios-rbac.md
description: Describes how to create role assignments and role definitions by us
+ Last updated 05/15/2022 # Create Azure RBAC resources by using Bicep
azure-resource-manager Scenarios Secrets https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/scenarios-secrets.md
description: Describes how to manage secrets by using Bicep and Azure Key Vault.
+ Last updated 07/20/2022 # Manage secrets by using Bicep
azure-resource-manager Scenarios Virtual Networks https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/scenarios-virtual-networks.md
description: Describes how to create virtual networks, network security groups,
+ Last updated 07/20/2022 # Create virtual network resources by using Bicep
Private endpoint approval is an operation, so you can't perform it directly with
- Quickstart templates - [Create a Virtual Network with two Subnets](https://azure.microsoft.com/resources/templates/vnet-two-subnets/) - [Virtual Network with diagnostic logs](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.network/vnet-create-with-diagnostic-logs)
-
+
azure-resource-manager Scope Extension Resources https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/scope-extension-resources.md
Title: Scope on extension resource types (Bicep) description: Describes how to use the scope property when deploying extension resource types with Bicep. + Last updated 07/12/2022
azure-resource-manager Template Specs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/template-specs.md
Title: Create & deploy template specs in Bicep description: Describes how to create template specs in Bicep and share them with other users in your organization. -+ Last updated 11/17/2022
azure-resource-manager User Defined Data Types https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/user-defined-data-types.md
Title: User-defined types in Bicep description: Describes how to define and use user-defined data types in Bicep. + Last updated 01/09/2023
azure-resource-manager Variables https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/variables.md
description: Describes how to define variables in Bicep
+ Last updated 09/28/2022
You can define variables that hold related values for configuring an environment
## Next steps - To learn about the available properties for variables, see [Understand the structure and syntax of Bicep files](file.md).-- To learn about using loop syntax, see [Iterative loops in Bicep](loops.md).
+- To learn about using loop syntax, see [Iterative loops in Bicep](loops.md).
azure-resource-manager Visual Studio Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/bicep/visual-studio-code.md
Title: Create Bicep files by using Visual Studio Code description: Describes how to create Bicep files by using Visual Studio Code + Last updated 03/03/2023
azure-resource-manager Tutorial Custom Providers Function Setup https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/custom-providers/tutorial-custom-providers-function-setup.md
Title: Set up Azure Functions description: This tutorial describes how to create a function app in Azure Functions that works with Azure Custom Resource Providers. + Last updated 09/20/2022
azure-resource-manager Tutorial Get Started With Custom Providers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/custom-providers/tutorial-get-started-with-custom-providers.md
Title: Create custom actions and resources
description: This tutorial goes over how to create custom actions and resources in Azure Resource Manager. It also shows how custom workflows interoperate with Azure Resource Manager Templates, Azure CLI, Azure Policy, and Azure Activity Log. + Last updated 06/19/2019
azure-resource-manager Publish Service Catalog App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/managed-applications/publish-service-catalog-app.md
description: Describes how to create and publish an Azure Managed Application in
-+ Last updated 03/21/2023
azure-resource-manager Publish Service Catalog Bring Your Own Storage https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/managed-applications/publish-service-catalog-bring-your-own-storage.md
description: Describes how to bring your own storage to create and publish an Az
-+ Last updated 03/21/2023
azure-resource-manager Authenticate Multi Tenant https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/authenticate-multi-tenant.md
Title: Authenticate across tenants description: Describes how Azure Resource Manager handles authentication requests across tenants. + Last updated 10/11/2019
azure-resource-manager Azure Services Resource Providers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/azure-services-resource-providers.md
Title: Resource providers by Azure services
description: Lists all resource provider namespaces for Azure Resource Manager and shows the Azure service for that namespace. Last updated 02/28/2023-+ # Resource providers for Azure services
azure-resource-manager Control Plane And Data Plane https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/control-plane-and-data-plane.md
Title: Control plane and data plane operations description: Describes the difference between control plane and data plane operations. Control plane operations are handled by Azure Resource Manager. Data plane operations are handled by a service. -+ Last updated 09/10/2020 # Azure control plane and data plane
azure-resource-manager Control Plane Metrics https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/control-plane-metrics.md
Title: Control plane metrics in Azure Monitor description: Azure Resource Manager metrics in Azure Monitor | Traffic and latency observability for subscription-level control plane requests + Last updated 12/01/2021
azure-resource-manager Delete Resource Group https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/delete-resource-group.md
Title: Delete resource group and resources
description: Describes how to delete resource groups and resources. It describes how Azure Resource Manager orders the deletion of resources when a deleting a resource group. It describes the response codes and how Resource Manager handles them to determine if the deletion succeeded. Last updated 10/13/2022-+ # Azure Resource Manager resource group and resource deletion
azure-resource-manager Deployment Models https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/deployment-models.md
Title: Resource Manager and classic deployment description: Describes the differences between the Resource Manager deployment model and the classic (or Service Management) deployment model. + Last updated 04/12/2021 # Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources
azure-resource-manager Manage Resource Groups Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/manage-resource-groups-cli.md
description: Use Azure CLI to manage your resource groups through Azure Resource
Last updated 03/31/2023-+ # Manage Azure Resource Groups by using Azure CLI
azure-resource-manager Manage Resource Groups Portal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/manage-resource-groups-portal.md
Title: Manage resource groups - Azure portal
description: Use Azure portal to manage your resource groups through Azure Resource Manager. Shows how to create, list, and delete resource groups. + Last updated 03/26/2019
azure-resource-manager Manage Resource Groups Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/manage-resource-groups-powershell.md
description: Use Azure PowerShell to manage your resource groups through Azure R
Last updated 03/31/2023--+ # Manage Azure Resource Groups by using Azure PowerShell
azure-resource-manager Manage Resource Groups Python https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/manage-resource-groups-python.md
Title: Manage resource groups - Python
description: Use Python to manage your resource groups through Azure Resource Manager. Shows how to create, list, and delete resource groups. + Last updated 02/27/2023
azure-resource-manager Manage Resources Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/manage-resources-cli.md
Last updated 02/11/2019 -+ # Manage Azure resources by using Azure CLI
Tagging helps organizing your resource group and resources logically. For inform
- To learn Azure Resource Manager, see [Azure Resource Manager overview](overview.md). - To learn the Resource Manager template syntax, see [Understand the structure and syntax of Azure Resource Manager templates](../templates/syntax.md). - To learn how to develop templates, see the [step-by-step tutorials](../index.yml).-- To view the Azure Resource Manager template schemas, see [template reference](/azure/templates/).
+- To view the Azure Resource Manager template schemas, see [template reference](/azure/templates/).
azure-resource-manager Manage Resources Portal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/manage-resources-portal.md
Title: Manage resources - Azure portal
description: Use the Azure portal and Azure Resource Manager to manage your resources. Shows how to deploy and delete resources. + Last updated 02/11/2019 - # Manage Azure resources by using the Azure portal
You can select the pin icon on the upper right corner of the graphs to pin the g
- To learn Azure Resource Manager, see [Azure Resource Manager overview](overview.md). - To learn the Resource Manager template syntax, see [Understand the structure and syntax of Azure Resource Manager templates](../templates/syntax.md). - To learn how to develop templates, see the [step-by-step tutorials](../index.yml).-- To view the Azure Resource Manager template schemas, see [template reference](/azure/templates/).
+- To view the Azure Resource Manager template schemas, see [template reference](/azure/templates/).
azure-resource-manager Manage Resources Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/manage-resources-powershell.md
Last updated 02/11/2019 -+ # Manage Azure resources by using Azure PowerShell
azure-resource-manager App Service Move Limitations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md
Title: Move Azure App Service resources across resource groups or subscriptions description: Use Azure Resource Manager to move App Service resources to a new resource group or subscription. + Last updated 03/31/2022
azure-resource-manager Classic Model Move Limitations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/move-limitations/classic-model-move-limitations.md
Title: Move Azure classic deployment resources
description: Use Azure Resource Manager to move classic deployment resources to a new resource group or subscription. Last updated 04/11/2022-+ # Move guidance for classic deployment model resources
azure-resource-manager Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/move-limitations/cloud-services-extended-support.md
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. Last updated 02/14/2023-+ # Move guidance for Cloud Services (extended support) deployment model resources
azure-resource-manager Networking Move Limitations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/move-limitations/networking-move-limitations.md
Title: Move Azure Networking resources to new subscription or resource group description: Use Azure Resource Manager to move virtual networks and other networking resources to a new resource group or subscription. + Last updated 10/28/2022
azure-resource-manager Virtual Machines Move Limitations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/move-limitations/virtual-machines-move-limitations.md
Title: Move Azure VMs to new subscription or resource group
description: Use Azure Resource Manager to move virtual machines to a new resource group or subscription. Last updated 03/31/2022 -+ # Move virtual machines to resource group or subscription
azure-resource-manager Move Resource Group And Subscription https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/move-resource-group-and-subscription.md
Title: Move resources to a new subscription or resource group
description: Use Azure Resource Manager to move resources to a new resource group or subscription. Last updated 01/30/2023-+ # Move resources to a new resource group or subscription
azure-resource-manager Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/overview.md
Title: Azure Resource Manager overview
description: Describes how to use Azure Resource Manager for deployment, management, and access control of resources on Azure. Last updated 02/28/2023-+ # What is Azure Resource Manager?
azure-resource-manager Policy Reference https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/policy-reference.md
Title: Built-in policy definitions for Azure Resource Manager
description: Lists Azure Policy built-in policy definitions for Azure Resource Manager. These built-in policy definitions provide common approaches to managing your Azure resources. Last updated 02/21/2023 -+ # Azure Policy built-in definitions for Azure Resource Manager
azure-resource-manager Request Limits And Throttling https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/request-limits-and-throttling.md
Title: Request limits and throttling
description: Describes how to use throttling with Azure Resource Manager requests when subscription limits have been reached. Last updated 03/02/2023-+ # Throttling Resource Manager requests
azure-resource-manager Resource Graph Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/resource-graph-samples.md
Title: Azure Resource Graph sample queries for Azure Resource Manager
description: Sample Azure Resource Graph queries for Azure Resource Manager showing use of resource types and tables to access Azure Resource Manager related resources and properties. Last updated 07/07/2022 -+ # Azure Resource Graph sample queries for Azure Resource Manager
azure-resource-manager Resource Manager Personal Data https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/resource-manager-personal-data.md
Title: Personal data description: Learn how to manage personal data associated with Azure Resource Manager operations. + Last updated 05/14/2018 # Manage personal data associated with Azure Resource Manager
azure-resource-manager Resource Providers And Types https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/resource-providers-and-types.md
Title: Resource providers and resource types
description: Describes the resource providers that support Azure Resource Manager. It describes their schemas, available API versions, and the regions that can host the resources. Last updated 08/05/2022 -+ # Azure resource providers and types
West US
* To learn about creating Resource Manager templates, see [Authoring Azure Resource Manager templates](../templates/syntax.md). * To view the resource provider template schemas, see [Template reference](/azure/templates/). * For a list that maps resource providers to Azure services, see [Resource providers for Azure services](azure-services-resource-providers.md).
-* To view the operations for a resource provider, see [Azure REST API](/rest/api/).
+* To view the operations for a resource provider, see [Azure REST API](/rest/api/).
azure-resource-manager Security Controls Policy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/security-controls-policy.md
-+ # Azure Policy Regulatory Compliance controls for Azure Resource Manager
azure-resource-manager Tls Support https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/management/tls-support.md
Title: TLS version supported by Azure Resource Manager description: Describes the deprecation of TLS versions prior to 1.2 in Azure Resource Manager + Last updated 09/26/2022 # Migrating to TLS 1.2 for Azure Resource Manager
azure-resource-manager Add Template To Azure Pipelines https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/add-template-to-azure-pipelines.md
Title: CI/CD with Azure Pipelines and templates description: Describes how to configure continuous integration in Azure Pipelines by using Azure Resource Manager templates. It shows how to use a PowerShell script, or copy files to a staging location and deploy from there. + Last updated 02/07/2022 # Integrate ARM templates with Azure Pipelines
azure-resource-manager All Files Test Cases https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/all-files-test-cases.md
Title: All files test cases for Azure Resource Manager test toolkit description: Describes the tests that are run for all files by the Azure Resource Manager template test toolkit. + Last updated 07/16/2021
azure-resource-manager Best Practices https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/best-practices.md
Title: Best practices for templates description: Describes recommended approaches for authoring Azure Resource Manager templates (ARM templates). Offers suggestions to avoid common problems when using templates. + Last updated 09/01/2022 # ARM template best practices
After you've completed your template, run the test toolkit to see if there are w
## Next steps * For information about the structure of the template file, see [Understand the structure and syntax of ARM templates](./syntax.md).
-* For recommendations about how to build templates that work in all Azure cloud environments, see [Develop ARM templates for cloud consistency](./template-cloud-consistency.md).
+* For recommendations about how to build templates that work in all Azure cloud environments, see [Develop ARM templates for cloud consistency](./template-cloud-consistency.md).
azure-resource-manager Child Resource Name Type https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/child-resource-name-type.md
Title: Child resources in templates description: Describes how to set the name and type for child resources in an Azure Resource Manager template (ARM template). + Last updated 01/19/2022
azure-resource-manager Conditional Resource Deployment https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/conditional-resource-deployment.md
Title: Conditional deployment with templates description: Describes how to conditionally deploy a resource in an Azure Resource Manager template (ARM template). + Last updated 01/19/2022
azure-resource-manager Copy Outputs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/copy-outputs.md
Title: Define multiple instances of an output value description: Use copy operation in an Azure Resource Manager template (ARM template) to iterate multiple times when returning a value from a deployment. + Last updated 05/07/2021
azure-resource-manager Copy Properties https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/copy-properties.md
Title: Define multiple instances of a property description: Use copy operation in an Azure Resource Manager template (ARM template) to iterate multiple times when creating a property on a resource. + Last updated 12/20/2021
azure-resource-manager Copy Resources https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/copy-resources.md
Title: Deploy multiple instances of resources description: Use copy operation and arrays in an Azure Resource Manager template (ARM template) to deploy resource type many times. + Last updated 05/07/2021
azure-resource-manager Copy Variables https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/copy-variables.md
Title: Define multiple instances of a variable description: Use copy operation in an Azure Resource Manager template (ARM template) to iterate multiple times when creating a variable. + Last updated 02/13/2020 # Variable iteration in ARM templates
azure-resource-manager Create Templates Use Intellij https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/create-templates-use-intellij.md
description: Learn how to create your first Azure Resource Manager template (ARM
ms.devlang: java Last updated 08/01/2019 -+ #Customer intent: As a developer new to Azure deployment, I want to learn how to use the IntelliJ IDEA to create and edit Resource Manager templates, so I can use the templates to deploy Azure resources.
azure-resource-manager Createuidefinition Test Cases https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/createuidefinition-test-cases.md
Title: createUiDefinition.json test cases for Azure Resource Manager test toolkit description: Describes the createUiDefinition.json tests that are run by the Azure Resource Manager template test toolkit. + Last updated 07/16/2021
azure-resource-manager Data Types https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/data-types.md
Title: Data types in templates description: Describes the data types that are available in Azure Resource Manager templates. + Last updated 09/16/2022
The following example shows two secure parameters.
## Next steps
-To learn about the template syntax, see [Understand the structure and syntax of ARM templates](./syntax.md).
+To learn about the template syntax, see [Understand the structure and syntax of ARM templates](./syntax.md).
azure-resource-manager Deploy Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-cli.md
Title: Azure deployment templates with Azure CLI ΓÇô Azure Resource Manager | Mi
description: Use Azure Resource Manager and Azure CLI to create and deploy resource groups to Azure. The resources are defined in an Azure deployment template. Last updated 09/17/2021-+ keywords: azure cli deploy arm template, create resource group azure, azure deployment template, deployment resources, arm template, azure arm template
If you are using Azure CLI with version 2.3.0 or older, you can deploy a templat
* To roll back to a successful deployment when you get an error, see [Rollback on error to successful deployment](rollback-on-error.md). * To specify how to handle resources that exist in the resource group but aren't defined in the template, see [Azure Resource Manager deployment modes](deployment-modes.md). * To understand how to define parameters in your template, see [Understand the structure and syntax of ARM templates](./syntax.md).
-* For tips on resolving common deployment errors, see [Troubleshoot common Azure deployment errors with Azure Resource Manager](common-deployment-errors.md).
+* For tips on resolving common deployment errors, see [Troubleshoot common Azure deployment errors with Azure Resource Manager](common-deployment-errors.md).
azure-resource-manager Deploy Cloud Shell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-cloud-shell.md
Title: Deploy templates with Cloud Shell description: Use Azure Resource Manager and Azure Cloud Shell to deploy resources to Azure. The resources are defined in an Azure Resource Manager template (ARM template). + Last updated 09/03/2021
To deploy a local template, you must first upload your template to the storage a
## Next steps - For more information about deployment commands, see [Deploy resources with ARM templates and Azure CLI](deploy-cli.md) and [Deploy resources with ARM templates and Azure PowerShell](deploy-powershell.md).-- To preview changes before deploying a template, see [ARM template deployment what-if operation](./deploy-what-if.md).
+- To preview changes before deploying a template, see [ARM template deployment what-if operation](./deploy-what-if.md).
azure-resource-manager Deploy Github Actions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-github-actions.md
Title: Deploy Resource Manager templates by using GitHub Actions
description: Describes how to deploy Azure Resource Manager templates (ARM templates) by using GitHub Actions. Last updated 05/10/2022-+ # Deploy ARM templates by using GitHub Actions
azure-resource-manager Deploy Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-powershell.md
Title: Deploy resources with PowerShell and template
description: Use Azure Resource Manager and Azure PowerShell to deploy resources to Azure. The resources are defined in a Resource Manager template. Last updated 05/13/2021-+ # Deploy resources with ARM templates and Azure PowerShell
azure-resource-manager Deploy Rest https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-rest.md
Title: Deploy resources with REST API and template description: Use Azure Resource Manager and Resource Manager REST API to deploy resources to Azure. The resources are defined in a Resource Manager template. + Last updated 02/01/2022
To avoid conflicts with concurrent deployments and to ensure unique entries in t
- To roll back to a successful deployment when you get an error, see [Rollback on error to successful deployment](rollback-on-error.md). - To specify how to handle resources that exist in the resource group but aren't defined in the template, see [Azure Resource Manager deployment modes](deployment-modes.md). - To learn about handling asynchronous REST operations, see [Track asynchronous Azure operations](../management/async-operations.md).-- To learn more about templates, see [Understand the structure and syntax of ARM templates](./syntax.md).
+- To learn more about templates, see [Understand the structure and syntax of ARM templates](./syntax.md).
azure-resource-manager Deploy To Azure Button https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-to-azure-button.md
Title: Deploy to Azure button description: Use button to deploy remote Azure Resource Manager templates. + Last updated 02/15/2022
The portal displays a pane that allows you to easily provide parameter values. T
## Next steps -- To learn more about templates, see [Understand the structure and syntax of ARM templates](./syntax.md).
+- To learn more about templates, see [Understand the structure and syntax of ARM templates](./syntax.md).
azure-resource-manager Deploy To Management Group https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-to-management-group.md
Title: Deploy resources to management group
description: Describes how to deploy resources at the management group scope in an Azure Resource Manager template. Last updated 01/19/2022-+ # Management group deployments with ARM templates
azure-resource-manager Deploy To Resource Group https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-to-resource-group.md
Title: Deploy resources to resource groups description: Describes how to deploy resources in an Azure Resource Manager template. It shows how to target more than one resource group. + Last updated 08/05/2022
azure-resource-manager Deploy To Subscription https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-to-subscription.md
Title: Deploy resources to subscription
description: Describes how to create a resource group in an Azure Resource Manager template. It also shows how to deploy resources at the Azure subscription scope. Last updated 01/19/2022-+ # Subscription deployments with ARM templates
azure-resource-manager Deploy To Tenant https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-to-tenant.md
Title: Deploy resources to tenant
description: Describes how to deploy resources at the tenant scope in an Azure Resource Manager template. Last updated 01/19/2022-+ # Tenant deployments with ARM templates
azure-resource-manager Deploy What If https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deploy-what-if.md
Title: Template deployment what-if
description: Determine what changes will happen to your resources before deploying an Azure Resource Manager template. Last updated 02/15/2023-+ ms.devlang: azurecli
azure-resource-manager Deployment Complete Mode Deletion https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-complete-mode-deletion.md
Title: Complete mode deletion description: Shows how resource types handle complete mode deletion in Azure Resource Manager templates. + Last updated 10/20/2022
azure-resource-manager Deployment History Deletions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-history-deletions.md
Title: Deployment history deletions
description: Describes how Azure Resource Manager automatically deletes deployments from the deployment history. Deployments are deleted when the history is close to exceeding the limit of 800. Last updated 06/04/2021-+ # Automatic deletions from deployment history
azure-resource-manager Deployment History https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-history.md
description: Describes how to view Azure Resource Manager deployment operations
tags: top-support-issue Last updated 12/03/2021-+ # View deployment history with Azure Resource Manager
azure-resource-manager Deployment Modes https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-modes.md
Title: Deployment modes description: Describes how to specify whether to use a complete or incremental deployment mode with Azure Resource Manager. + Last updated 01/21/2022 # Azure Resource Manager deployment modes
azure-resource-manager Deployment Script Template Configure Dev https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-script-template-configure-dev.md
Last updated 12/14/2020 -+ ms.devlang: azurecli- # Configure development environment for deployment scripts in ARM templates
azure-resource-manager Deployment Script Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-script-template.md
description: Use deployment scripts in Azure Resource Manager templates.
+ Last updated 01/25/2022
azure-resource-manager Deployment Tutorial Local Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-tutorial-local-template.md
Title: Tutorial - Deploy a local Azure Resource Manager template
description: Learn how to deploy an Azure Resource Manager template (ARM template) from your local computer Last updated 02/10/2021 +
azure-resource-manager Deployment Tutorial Pipeline https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/deployment-tutorial-pipeline.md
Title: Continuous integration with Azure Pipelines
description: Learn how to continuously build, test, and deploy Azure Resource Manager templates (ARM templates). Last updated 03/02/2021 +
azure-resource-manager Export Template Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/export-template-cli.md
Title: Export template in Azure CLI description: Use Azure CLI to export an Azure Resource Manager template from resources in your subscription. + Last updated 09/03/2021 # Use Azure CLI to export a template
To get templates deployed at other levels, use:
- Learn how to export templates with [Azure portal](export-template-portal.md), [Azure PowerShell](export-template-powershell.md), or [REST API](/rest/api/resources/resourcegroups/exporttemplate). - To learn the Resource Manager template syntax, see [Understand the structure and syntax of Azure Resource Manager templates](./syntax.md).-- To learn how to develop templates, see the [step-by-step tutorials](../index.yml).
+- To learn how to develop templates, see the [step-by-step tutorials](../index.yml).
azure-resource-manager Export Template Portal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/export-template-portal.md
Title: Export template in Azure portal description: Use Azure portal to export an Azure Resource Manager template from resources in your subscription. + Last updated 09/01/2021 # Use Azure portal to export a template
You can export the template that was used to deploy existing resources. The temp
- Learn how to export templates with [Azure CLI](export-template-cli.md), [Azure PowerShell](export-template-powershell.md), or [REST API](/rest/api/resources/resourcegroups/exporttemplate). - To learn the Resource Manager template syntax, see [Understand the structure and syntax of Azure Resource Manager templates](./syntax.md).-- To learn how to develop templates, see the [step-by-step tutorials](../index.yml).
+- To learn how to develop templates, see the [step-by-step tutorials](../index.yml).
azure-resource-manager Export Template Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/export-template-powershell.md
Title: Export template in Azure PowerShell description: Use Azure PowerShell to export an Azure Resource Manager template from resources in your subscription. -+ Last updated 09/03/2021 # Use Azure PowerShell to export a template
azure-resource-manager Linked Templates https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/linked-templates.md
Title: Link templates for deployment
description: Describes how to use linked templates in an Azure Resource Manager template (ARM template) to create a modular template solution. Shows how to pass parameters values, specify a parameter file, and dynamically created URLs. Last updated 01/06/2022-+ # Using linked and nested templates when deploying Azure resources
azure-resource-manager Outputs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/outputs.md
Title: Outputs in templates description: Describes how to define output values in an Azure Resource Manager template (ARM template). + Last updated 09/28/2022
azure-resource-manager Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/overview.md
Title: Templates overview description: Describes the benefits using Azure Resource Manager templates (ARM templates) for deployment of resources. + Last updated 05/26/2022
azure-resource-manager Parameter File Test Cases https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/parameter-file-test-cases.md
Title: Parameter file test cases for Azure Resource Manager test toolkit description: Describes the parameter file tests that are run by the Azure Resource Manager template test toolkit. + Last updated 07/16/2021
azure-resource-manager Parameter Files https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/parameter-files.md
Title: Create parameter file description: Create parameter file for passing in values during deployment of an Azure Resource Manager template + Last updated 11/14/2022
azure-resource-manager Parameters https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/parameters.md
Title: Parameters in templates description: Describes how to define parameters in an Azure Resource Manager template (ARM template). + Last updated 09/28/2022
azure-resource-manager Quickstart Create Template Specs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/quickstart-create-template-specs.md
Last updated 05/04/2021 -+ ms.devlang: azurecli
azure-resource-manager Quickstart Create Templates Use The Portal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md
Last updated 08/22/2022 -+ #Customer intent: As a developer new to Azure deployment, I want to learn how to use the Azure portal to create and edit Resource Manager templates, so I can use the templates to deploy Azure resources.
azure-resource-manager Quickstart Create Templates Use Visual Studio Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md
Last updated 06/27/2022 -+ #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio Code to create and edit Resource Manager templates, so I can use the templates to deploy Azure resources.
azure-resource-manager Resource Declaration https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/resource-declaration.md
Title: Declare resources in templates description: Describes how to declare resources to deploy in an Azure Resource Manager template (ARM template). + Last updated 09/28/2022
azure-resource-manager Resource Extensions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/resource-extensions.md
Title: Post-deployment configuration with extensions
description: Learn how to use Azure Resource Manager template (ARM template) extensions for post-deployment configurations. + Last updated 12/14/2018
azure-resource-manager Resource Location https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/resource-location.md
Title: Template resource location description: Describes how to set resource location in an Azure Resource Manager template (ARM template). + Last updated 09/04/2019
azure-resource-manager Scope Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/scope-functions.md
Title: Template functions in scoped deployments description: Describes how template functions are resolved in scoped deployments. The scope can be a tenant, management groups, subscriptions, and resource groups. + Last updated 10/22/2020
azure-resource-manager Secure Template With Sas Token https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/secure-template-with-sas-token.md
Title: Deploy ARM template with SAS token - Azure Resource Manager | Microsoft D
description: Learn how to use Azure CLI or Azure PowerShell to securely deploy a private ARM template with a SAS token. Protect and manage access to your templates. Last updated 09/17/2021-+ keywords: private template, sas token template, storage account, template security, azure arm template, azure resource manager template # How to deploy private ARM template with SAS token
For an example of using a SAS token with linked templates, see [Using linked tem
## Next steps * For an introduction to deploying templates, see [Deploy resources with ARM templates and Azure PowerShell](deploy-powershell.md).
-* To define parameters in template, see [Authoring templates](./syntax.md#parameters).
+* To define parameters in template, see [Authoring templates](./syntax.md#parameters).
azure-resource-manager Syntax https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/syntax.md
Title: Template structure and syntax description: Describes the structure and properties of Azure Resource Manager templates (ARM templates) using declarative JSON syntax. -+ Last updated 09/28/2022
azure-resource-manager Template Cloud Consistency https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-cloud-consistency.md
Last updated 12/09/2018 -+ # Develop ARM templates for cloud consistency
azure-resource-manager Template Expressions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-expressions.md
Title: Template syntax and expressions description: Describes the declarative JSON syntax for Azure Resource Manager templates (ARM templates). + Last updated 02/22/2023
azure-resource-manager Template Functions Array https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-array.md
Title: Template functions - arrays description: Describes the functions to use in an Azure Resource Manager template (ARM template) for working with arrays. + Last updated 04/12/2022
azure-resource-manager Template Functions Comparison https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-comparison.md
Title: Template functions - comparison description: Describes the functions to use in an Azure Resource Manager template (ARM template) to compare values. + Last updated 02/11/2022
azure-resource-manager Template Functions Date https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-date.md
Title: Template functions - date description: Describes the functions to use in an Azure Resource Manager template (ARM template) to work with dates. + Last updated 05/03/2022
azure-resource-manager Template Functions Deployment https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-deployment.md
Title: Template functions - deployment description: Describes the functions to use in an Azure Resource Manager template (ARM template) to retrieve deployment information. + Last updated 06/27/2022
azure-resource-manager Template Functions Lambda https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-lambda.md
Title: Template functions - lambda
description: Describes the lambda functions to use in an Azure Resource Manager template (ARM template) + Last updated 03/15/2023
azure-resource-manager Template Functions Logical https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-logical.md
Title: Template functions - logical description: Describes the functions to use in an Azure Resource Manager template (ARM template) to determine logical values. + Last updated 02/11/2022
azure-resource-manager Template Functions Numeric https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-numeric.md
Title: Template functions - numeric description: Describes the functions to use in an Azure Resource Manager template (ARM template) to work with numbers. + Last updated 03/10/2022
azure-resource-manager Template Functions Object https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-object.md
Title: Template functions - objects description: Describes the functions to use in an Azure Resource Manager template (ARM template) for working with objects. + Last updated 09/16/2022
azure-resource-manager Template Functions Resource https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-resource.md
Title: Template functions - resources
description: Describes the functions to use in an Azure Resource Manager template (ARM template) to retrieve values about resources. Last updated 09/09/2022-+ # Resource functions for ARM templates
azure-resource-manager Template Functions Scope https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-scope.md
Title: Template functions - scope description: Describes the functions to use in an Azure Resource Manager template (ARM template) to retrieve values about deployment scope. + Last updated 11/17/2022
azure-resource-manager Template Functions String https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions-string.md
Title: Template functions - string description: Describes the functions to use in an Azure Resource Manager template (ARM template) to work with strings. + Last updated 03/10/2022
azure-resource-manager Template Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-functions.md
Title: Template functions description: Describes the functions to use in an Azure Resource Manager template (ARM template) to retrieve values, work with strings and numerics, and retrieve deployment information. + Last updated 05/02/2022
azure-resource-manager Template Specs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-specs.md
Title: Create & deploy template specs
description: Describes how to create template specs and share them with other users in your organization. Last updated 11/17/2022-+ # Azure Resource Manager template specs
azure-resource-manager Template Test Cases https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-test-cases.md
Title: Template test cases for test toolkit description: Describes the template tests that are run by the Azure Resource Manager template test toolkit. + Last updated 11/09/2022
azure-resource-manager Template Tutorial Add Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-add-functions.md
Last updated 06/17/2022 -+ # Tutorial: Add template functions to your ARM template
azure-resource-manager Template Tutorial Add Outputs https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-add-outputs.md
Last updated 08/17/2022 -+ # Tutorial: Add outputs to your ARM template
azure-resource-manager Template Tutorial Add Parameters https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-add-parameters.md
description: Add parameters to your Azure Resource Manager template (ARM templat
Last updated 06/15/2022 +
azure-resource-manager Template Tutorial Add Resource https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-add-resource.md
Last updated 06/14/2022 -+ # Tutorial: Add a resource to your ARM template
azure-resource-manager Template Tutorial Add Tags https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-add-tags.md
Last updated 08/22/2022 -+ # Tutorial: Add tags in your ARM template
azure-resource-manager Template Tutorial Add Variables https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-add-variables.md
Last updated 06/17/2022 -+ # Tutorial: Add variables to your ARM template
azure-resource-manager Template Tutorial Create First Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-create-first-template.md
description: Create your first Azure Resource Manager template (ARM template). I
Last updated 06/15/2022 + #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio Code to create and edit Azure Resource Manager templates, so I can use them to deploy Azure resources.
azure-resource-manager Template Tutorial Create Multiple Instances https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-create-multiple-instances.md
description: Learn how to create an Azure Resource Manager template (ARM templat
Last updated 09/28/2022 +
azure-resource-manager Template Tutorial Create Templates With Dependent Resources https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-create-templates-with-dependent-resources.md
description: Learn how to create an Azure Resource Manager template (ARM templat
Last updated 04/23/2020 +
azure-resource-manager Template Tutorial Deploy Sql Extensions Bacpac https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac.md
Title: Import SQL BACPAC files with templates
description: Learn how to use Azure SQL Database extensions to import SQL BACPAC files with Azure Resource Manager templates (ARM templates). Last updated 02/28/2022 -+ #Customer intent: As a database administrator I want use ARM templates so that I can import a SQL BACPAC file.
azure-resource-manager Template Tutorial Deploy Vm Extensions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-deploy-vm-extensions.md
description: Learn how to deploy virtual machine extensions with Azure Resource
Last updated 03/26/2021 +
azure-resource-manager Template Tutorial Deployment Script https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-deployment-script.md
na-+ Last updated 09/28/2022
azure-resource-manager Template Tutorial Use Key Vault https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-use-key-vault.md
Last updated 03/01/2021 -+ # Tutorial: Integrate Azure Key Vault in your ARM template deployment
azure-resource-manager Template Tutorial Use Parameter File https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-use-parameter-file.md
description: Use parameter files that contain the values to use for deploying yo
Last updated 08/22/2022 +
azure-resource-manager Template Tutorial Use Template Reference https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/template-tutorial-use-template-reference.md
description: Use the Azure Resource Manager template (ARM template) reference to
Last updated 02/11/2022 +
azure-resource-manager Test Toolkit https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/test-toolkit.md
Title: ARM template test toolkit description: Describes how to run the Azure Resource Manager template (ARM template) test toolkit on your template. The toolkit lets you see if you have implemented recommended practices. + Last updated 03/21/2023
azure-resource-manager User Defined Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/user-defined-functions.md
Title: User-defined functions in templates description: Describes how to define and use user-defined functions in an Azure Resource Manager template (ARM template). + Last updated 04/12/2021
When defining a user function, there are some restrictions:
## Next steps * To learn about the available properties for user-defined functions, see [Understand the structure and syntax of ARM templates](./syntax.md).
-* For a list of the available template functions, see [ARM template functions](template-functions.md).
+* For a list of the available template functions, see [ARM template functions](template-functions.md).
azure-resource-manager Variables https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/templates/variables.md
Title: Variables in templates description: Describes how to define variables in an Azure Resource Manager template (ARM template). + Last updated 09/28/2022
azure-resource-manager Common Deployment Errors https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/common-deployment-errors.md
Title: Troubleshoot common Azure deployment errors description: Troubleshoot common Azure deployment errors for resources that are deployed with Bicep files or Azure Resource Manager templates (ARM templates). tags: top-support-issue+ Last updated 04/05/2023
azure-resource-manager Create Troubleshooting Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/create-troubleshooting-template.md
Title: Create a troubleshooting template description: Describes how to create a template to troubleshoot Azure resource deployed with Azure Resource Manager templates (ARM templates) or Bicep files. tags: top-support-issue+ Last updated 04/05/2023
azure-resource-manager Enable Debug Logging https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/enable-debug-logging.md
Title: Enable debug logging description: Describes how to enable debug logging to troubleshoot Azure resources deployed with Bicep files or Azure Resource Manager templates (ARM templates). tags: top-support-issue+ Last updated 04/05/2023
azure-resource-manager Error Invalid Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-invalid-template.md
Title: Invalid template errors description: Describes how to resolve invalid template errors when deploying Bicep files or Azure Resource Manager templates (ARM templates). + Last updated 04/05/2023
azure-resource-manager Error Job Size Exceeded https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-job-size-exceeded.md
Title: Job size exceeded error description: Describes how to troubleshoot errors for job size exceeded or if the template is too large for deployments using a Bicep file or Azure Resource Manager template (ARM template). + Last updated 04/05/2023
azure-resource-manager Error Not Found https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-not-found.md
Title: Resource not found errors description: Describes how to resolve errors when a resource can't be found. The error might occur when you deploy a Bicep file or Azure Resource Manager template, or when doing management tasks. + Last updated 04/05/2023
azure-resource-manager Error Parent Resource https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-parent-resource.md
Title: Parent resource errors description: Describes how to resolve errors when you deploy a resource that's dependent on a parent resource in a Bicep file or Azure Resource Manager template (ARM template). + Last updated 04/05/2023
azure-resource-manager Error Policy Requestdisallowedbypolicy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-policy-requestdisallowedbypolicy.md
Title: Request disallowed by policy error description: Describes the error for request disallowed by policy when deploying resources with an Azure Resource Manager template (ARM template) or Bicep file. + Last updated 04/05/2023
azure-resource-manager Error Register Resource Provider https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-register-resource-provider.md
Title: Resource provider registration errors description: Describes how to resolve Azure resource provider registration errors for resources deployed with a Bicep file or Azure Resource Manager template (ARM template). + Last updated 04/05/2023- # Resolve errors for resource provider registration
azure-resource-manager Error Resource Quota https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-resource-quota.md
Title: Resource quota errors description: Describes how to resolve resource quota errors when deploying resources with an Azure Resource Manager template (ARM template) or Bicep file. + Last updated 04/05/2023
azure-resource-manager Error Sku Not Available https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-sku-not-available.md
Title: SKU not available errors description: Describes how to troubleshoot the SKU not available error when deploying resources with an Azure Resource Manager template (ARM template) or Bicep file. + Last updated 04/05/2023
azure-resource-manager Error Storage Account Name https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/error-storage-account-name.md
Title: Resolve errors for storage account names description: Describes how to resolve errors for Azure storage account names that can occur during deployment with a Bicep file or Azure Resource Manager template (ARM template). + Last updated 04/05/2023
azure-resource-manager Find Error Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/find-error-code.md
Title: Find error codes
description: Describes how to find error codes to troubleshoot Azure resources deployed with Azure Resource Manager templates (ARM templates) or Bicep files. tags: top-support-issue + Last updated 04/05/2023- # Find error codes
azure-resource-manager Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/overview.md
Title: Overview of deployment troubleshooting for Bicep files and ARM templates description: Describes deployment troubleshooting when you use Bicep files or Azure Resource Manager templates (ARM templates) to deploy Azure resources. + Last updated 04/05/2023- # What is deployment troubleshooting?
azure-resource-manager Quickstart Troubleshoot Arm Deployment https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-arm-deployment.md
Title: Troubleshoot ARM template JSON deployments
description: Learn how to troubleshoot Azure Resource Manager template (ARM template) JSON deployments. Last updated 04/05/2023 -+ # Quickstart: Troubleshoot ARM template JSON deployments
azure-resource-manager Quickstart Troubleshoot Bicep Deployment https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-bicep-deployment.md
Title: Troubleshoot Bicep file deployments
description: Learn how to monitor and troubleshoot Bicep file deployments. Shows activity logs and deployment history. Last updated 04/05/2023 -+ # Quickstart: Troubleshoot Bicep file deployments
azure-signalr Signalr Howto Key Rotation https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-signalr/signalr-howto-key-rotation.md
Title: Rotate access keys for Azure SignalR Service
description: An overview on why the customer needs to routinely rotate the access keys and how to do it with the Azure portal GUI and the Azure CLI. + Last updated 03/29/2023
The Azure SignalR Service can enforce a mandatory access key regeneration under
> [Azure SignalR Service authentication](./signalr-concept-authenticate-oauth.md) > [!div class="nextstepaction"]
-> [Build a serverless real-time app with authentication](./signalr-tutorial-authenticate-azure-functions.md)
+> [Build a serverless real-time app with authentication](./signalr-tutorial-authenticate-azure-functions.md)
azure-signalr Signalr Howto Move Across Regions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-signalr/signalr-howto-move-across-regions.md
Last updated 05/23/2022 -+ # Move an Azure SignalR resource to another region
azure-signalr Signalr Quickstart Azure Signalr Service Arm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md
Last updated 10/02/2020 -+ # Quickstart: Use an ARM template to deploy Azure SignalR Service
azure-signalr Signalr Quickstart Azure Signalr Service Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-signalr/signalr-quickstart-azure-signalr-service-bicep.md
Last updated 05/18/2022 -+ # Quickstart: Use Bicep to deploy Azure SignalR Service
azure-signalr Signalr Reference Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-signalr/signalr-reference-cli.md
Title: Azure CLI Samples - Azure SignalR Service
description: Follow real samples to learn Azure CLI for Azure SignalR Service. You will learn how to create SignalR Service with more Azure services. + Last updated 11/13/2019
azure-video-indexer Deploy With Arm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-video-indexer/deploy-with-arm-template.md
Title: Deploy Azure Video Indexer by using an ARM template description: Learn how to create an Azure Video Indexer account by using an Azure Resource Manager (ARM) template. + Last updated 05/23/2022
azure-video-indexer Deploy With Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-video-indexer/deploy-with-bicep.md
Title: Deploy Azure Video Indexer by using Bicep description: Learn how to create an Azure Video Indexer account by using a Bicep file. + Last updated 06/06/2022
azure-video-indexer Network Security https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-video-indexer/network-security.md
Title: How to enable network security description: This article gives an overview of the Azure Video Indexer network security options. + Last updated 12/19/2022
azure-vmware Concepts Identity https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-vmware/concepts-identity.md
Title: Concepts - Identity and access
description: Learn about the identity and access concepts of Azure VMware Solution Previously updated : 4/6/2023 Last updated : 4/7/2023 # Azure VMware Solution identity concepts
-Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX-T Manager. You'll use vCenter to manage virtual machine (VM) workloads and NSX-T Manager to manage and extend the private cloud. The CloudAdmin role is used for vCenter Server and the CloudAdmin role (with restricted permissions) is used for NSX-T Manager.
+Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX-T Manager. You'll use vCenter Server to manage virtual machine (VM) workloads and NSX-T Manager to manage and extend the private cloud. The CloudAdmin role is used for vCenter Server and the CloudAdmin role (with restricted permissions) is used for NSX-T Manager.
## vCenter Server access and identity
azure-web-pubsub Howto Service Tags https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-web-pubsub/howto-service-tags.md
description: Use service tags to allow outbound traffic to your Azure Web PubSub service. + Last updated 11/08/2021
az network nsg rule create -n <rule-name> --nsg-name <nsg-name> -g <resource-gro
## Next steps -- [Network security groups: service tags](../virtual-network/network-security-groups-overview.md#security-rules)
+- [Network security groups: service tags](../virtual-network/network-security-groups-overview.md#security-rules)
azure-web-pubsub Quickstart Bicep Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-web-pubsub/quickstart-bicep-template.md
Last updated 06/15/2022 -+ # Quickstart: Use Bicep to deploy Azure Web PubSub service
azure-web-pubsub Tutorial Pub Sub Messages https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-web-pubsub/tutorial-pub-sub-messages.md
description: A tutorial to walk through how to use Azure Web PubSub service and
+ Last updated 03/09/2023
backup Azure Backup Glossary https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/azure-backup-glossary.md
Title: Azure Backup glossary description: This article defines terms helpful for use with Azure Backup. + Last updated 12/21/2020
backup Backup Afs Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/backup-afs-cli.md
Title: Back up Azure file shares with Azure CLI description: Learn how to use Azure CLI to back up Azure file shares in the Recovery Services vault + Last updated 01/14/2020
backup Backup Azure Sql Restore Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/backup-azure-sql-restore-cli.md
description: Learn how to use CLI to restore SQL server databases in Azure VMs i
Last updated 08/11/2022 +
backup Backup Rm Template Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/backup-rm-template-samples.md
Title: Azure Resource Manager and Bicep templates
description: Azure Resource Manager and Bicep templates for use with Recovery Services vaults and Azure Backup features Last updated 09/05/2022-+
backup Create Manage Azure Services Using Azure Command Line Interface https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/create-manage-azure-services-using-azure-command-line-interface.md
Title: Create and manage Azure services with Azure CLI description: Use Azure CLI to create and manage Azure services for Azure Backup. + Last updated 05/21/2021
Azure services | CLI document references
Azure Vault | [Delete a Recovery Services vault](./backup-azure-delete-vault.md?tabs=cli#tabpanel_1_cli) Azure Virtual Machine (VM) | <li>[Backup an Azure VM](quick-backup-vm-cli.md)</li><li>[Restore an Azure VM](tutorial-restore-disk.md)</li><li>[Restores files from Azure VM backups](tutorial-restore-files.md)</li><li>[Update the existing VM backup policy](modify-vm-policy-cli.md)</li><li>[Backup and restore selective disk for Azure VMs](selective-disk-backup-restore.md#using-azure-cli)</li> Azure file share | <li>[Back up Azure file shares](backup-afs-cli.md)</li><li>[Restore Azure file shares](restore-afs-cli.md)</li><li>[Manage Azure file share backups](manage-afs-backup-cli.md)</li>
-SAP HANA | <li>[Back up SAP HANA databases in an Azure VM](tutorial-sap-hana-backup-cli.md)</li><li>[Restore SAP HANA databases in an Azure VM](tutorial-sap-hana-restore-cli.md)</li><li>[Manage SAP HANA databases in an Azure VM](tutorial-sap-hana-manage-cli.md)</li>
+SAP HANA | <li>[Back up SAP HANA databases in an Azure VM](tutorial-sap-hana-backup-cli.md)</li><li>[Restore SAP HANA databases in an Azure VM](tutorial-sap-hana-restore-cli.md)</li><li>[Manage SAP HANA databases in an Azure VM](tutorial-sap-hana-manage-cli.md)</li>
backup Modify Vm Policy Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/modify-vm-policy-cli.md
Title: Update the existing VM backup policy using CLI description: Learn how to update the existing VM backup policy using Azure CLI. + Last updated 12/31/2020
To modify an existing VM backup policy, follow these steps:
## Next steps -- [Manage Azure VM backups with the Azure Backup service](backup-azure-manage-vms.md)
+- [Manage Azure VM backups with the Azure Backup service](backup-azure-manage-vms.md)
backup Quick Backup Vm Bicep Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/quick-backup-vm-bicep-template.md
ms.devlang: azurecli
Last updated 11/17/2021 -+
backup Quick Backup Vm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/quick-backup-vm-template.md
description: Learn how to back up your virtual machines with Azure Resource Mana
ms.devlang: azurecli Last updated 11/15/2021-+
backup Restore Afs Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/restore-afs-cli.md
Title: Restore Azure file shares with the Azure CLI description: Learn how to use the Azure CLI to restore backed-up Azure file shares in the Recovery Services vault + Last updated 01/16/2020
backup Selective Disk Backup Restore https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/selective-disk-backup-restore.md
Title: Selective disk backup and restore for Azure virtual machines
description: In this article, learn about selective disk backup and restore using the Azure virtual machine backup solution. Last updated 04/05/2023-+
baremetal-infrastructure Solution Design https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/solution-design.md
This article identifies topologies and constraints for NC2 on Azure.
The following table describes the network topologies supported by each network features configuration of NC2 on Azure.
-|Topology |Basic network features |
+|Topology |Supported |
| :- |::| |Connectivity to BareMetal (BM) in a local VNet| Yes | |Connectivity to BM in a peered VNet (Same region)|Yes | |Connectivity to BM in a peered VNet (Cross region or global peering)|No |
-|Connectivity to a BM over ExpressRoute gateway |Yes|
+|On-premises Connectivity to Delegated Subnet via Global and Local Expressroute |Yes|
|ExpressRoute (ER) FastPath |No | |Connectivity from on-premises to a BM in a spoke VNet over ExpressRoute gateway and VNet peering with gateway transit|Yes |
-|Connectivity from on-premises to a BM in a spoke VNet over VPN gateway| Yes |
+|On-premises Connectivity to Delegated Subnet via VPN GW| Yes |
|Connectivity from on-premises to a BM in a spoke VNet over VPN gateway and VNet peering with gateway transit| Yes | |Connectivity over Active/Passive VPN gateways| Yes | |Connectivity over Active/Active VPN gateways| No | |Connectivity over Active/Active Zone Redundant gateways| No |
-|Connectivity over Virtual WAN (VWAN)| No |
+|Transit connectivity via vWAN for Spoke Delegated VNETS| No |
+|On-premises connectivity to Delegated subnet via vWAN attached SD-WAN| No|
+|On-premises Connectivity via Secured HUB(Az Firewall NVA) | No|
## Constraints The following table describes whatΓÇÖs supported for each network features configuration:
-|Features |Basic network features |
+|Features |Supported |
| :- | -: | |Delegated subnet per VNet |1| |[Network Security Groups](../../../virtual-network/network-security-groups-overview.md) on NC2 on Azure-delegated subnets|No|
bastion Configure Host Scaling Powershell https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/bastion/configure-host-scaling-powershell.md
description: Learn how to add additional instances (scale units) to Azure Bastio
+ Last updated 11/29/2021
This article helps you add additional scale units (instances) to Azure Bastion t
## Next steps For more information about configuration settings, see [Azure Bastion configuration settings](configuration-settings.md).-
bastion Quickstart Host Arm Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/bastion/quickstart-host-arm-template.md
Last updated 06/27/2022-+ Customer intent: As someone with a networking background, I want to deploy Azure Bastion to a virtual machine using a Bastion ARM Template.
batch Account Move https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/batch/account-move.md
Title: Move an Azure Batch account to another region
description: Learn how to move an Azure Batch account to a different region using an Azure Resource Manager template in the Azure portal. Last updated 02/27/2023-+ # Move an Azure Batch account to another region
batch Batch Aad Auth Management https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/batch/batch-aad-auth-management.md
Title: Use Azure Active Directory to authenticate Batch Management solutions
description: Explore using Azure Active Directory to authenticate from applications that use the Batch Management .NET library. Last updated 04/27/2017--+ # Authenticate Batch Management solutions with Active Directory
batch Batch Job Prep Release https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/batch/batch-job-prep-release.md
Title: Create tasks to prepare and complete jobs on compute nodes
-description: Make job-level preparation tasks to minimize data transfer to Azure Batch compute nodes, and release tasks for node cleanup at job completion.
+ Title: Job preparation and release tasks on Batch compute nodes
+description: Use job-level preparation tasks to minimize data transfer to Azure Batch compute nodes, and release tasks for node cleanup at job completion.
Previously updated : 01/12/2021 Last updated : 04/06/2023 ms.devlang: csharp
-# Create tasks to prepare and complete jobs on Batch compute nodes
+# Job preparation and release tasks on Batch compute nodes
-An Azure Batch job often requires some form of setup before its tasks are executed. It also may require post-job maintenance when its tasks are completed. For example, you might need to download common task input data to your compute nodes, or upload task output data to Azure Storage after the job completes. You can use **job preparation** and **job release** tasks to perform these operations.
+An Azure Batch job often requires setup before its tasks are executed, and post-job maintenance when its tasks are completed. For example, you might need to download common task input data to your compute nodes, or upload task output data to Azure Storage after the job completes. You can use *job preparation* and *job release* tasks for these operations.
-## What are job preparation and release tasks?
+- A job preparation task runs before a job's tasks, on all compute nodes scheduled to run at least one task.
+- A job release task runs once the job is completed, on each node in the pool that executed at least one task.
-Before a job's tasks run, the job preparation task runs on all compute nodes scheduled to run at least one task. Once the job is completed, the job release task runs on each node in the pool that executed at least one task. As with normal Batch tasks, you can specify a command line to be invoked when a job preparation or release task is run.
+As with other Batch tasks, you can specify a command line to invoke when a job preparation or release task runs. Job preparation and release tasks offer familiar Batch task features such as:
-Job preparation and release tasks offer familiar Batch task features such as file download ([resource files](/dotnet/api/microsoft.azure.batch.jobpreparationtask.resourcefiles)), elevated execution, custom environment variables, maximum execution duration, retry count, and file retention time.
+- [Resource file download](/dotnet/api/microsoft.azure.batch.jobpreparationtask.resourcefiles).
+- Elevated execution.
+- Custom environment variables.
+- Maximum execution duration.
+- Retry count.
+- File retention time.
-In the following sections, you'll learn how to use the [JobPreparationTask](/dotnet/api/microsoft.azure.batch.jobpreparationtask) and [JobReleaseTask](/dotnet/api/microsoft.azure.batch.jobreleasetask) classes found in the [Batch .NET](/dotnet/api/microsoft.azure.batch) library.
+This article shows how to use the [JobPreparationTask](/dotnet/api/microsoft.azure.batch.jobpreparationtask) and [JobReleaseTask](/dotnet/api/microsoft.azure.batch.jobreleasetask) classes in the [Batch .NET](/dotnet/api/microsoft.azure.batch) library.
> [!TIP]
-> Job preparation and release tasks are especially helpful in "shared pool" environments, in which a pool of compute nodes persists between job runs and is used by many jobs.
+> Job preparation and release tasks are especially helpful in *shared pool* environments, in which a pool of compute nodes persists between job runs and is used by many jobs.
-## When to use job preparation and release tasks
+## Use cases for job preparation and release tasks
-Job preparation and job release tasks are a good fit for the following situations:
+Job preparation and job release tasks are a good fit for the following scenarios:
-- **Downloading common task data**: Batch jobs often require a common set of data as input for the job's tasks. For example, in daily risk analysis calculations, market data is job-specific, yet common to all tasks in the job. This market data, often several gigabytes in size, should be downloaded to each compute node only once so that any task that runs on the node can use it. Use a **job preparation task** to download this data to each node before the execution of the job's other tasks.
+- **Download common task data**. Batch jobs often require a common set of data as input for a job's tasks. You can use a job preparation task to download this data to each node before the execution of the job's other tasks.
-- **Job and task output deletion**: In a "shared pool" environment, where a pool's compute nodes are not decommissioned between jobs, you may need to delete job data between runs. You might need to conserve disk space on the nodes, or satisfy your organization's security policies. Use a **job release task** to delete data that was downloaded by a job preparation task, or that was generated during task execution.
+ For example, in daily risk analysis calculations, market data is job-specific yet common to all tasks in the job. You can use a job preparation task to download this market data, which is often several gigabytes in size, to each compute node so that any task that runs on the node can use it.
-- **Log retention**: You might want to keep a copy of log files that your tasks generate, or perhaps crash dump files that can be generated by failed applications. Use a **job release task** in such cases to compress and upload this data to an [Azure Storage account](accounts.md#azure-storage-accounts).
+- **Delete job and task output**. In a shared pool environment, where a pool's compute nodes aren't decommissioned between jobs, you might need to delete job data between runs. For example, you might need to conserve disk space on the nodes, or satisfy your organization's security policies. You can use a job release task to delete data that a job preparation task downloaded or that task execution generated.
+
+- **Retain logs**. You might want to keep a copy of log files that your tasks generate, or crash dump files that failed applications generate. You can use a job release task to compress and upload this data to an [Azure Storage account](accounts.md#azure-storage-accounts).
## Job preparation task
-Before executing tasks in a job, Batch runs the job preparation task on each compute node scheduled to run a task. By default, Batch waits for the job preparation task to complete before running the tasks scheduled to execute on the node. However, you can configure the service not to wait. If the node restarts, the job preparation task runs again. You can also disable this behavior. If you have a job with a job preparation task and a job manager task configured, the job preparation task runs before the job manager task, just as it does for all other tasks. The job preparation task always runs first.
+Before it runs job tasks, Batch runs the job preparation task on each compute node scheduled to run a task. By default, Batch waits for the job preparation task to complete before running scheduled job tasks, but you can configure it not to wait.
+
+If the node restarts, the job preparation task runs again, but you can also disable this behavior. If you have a job with a job preparation task and a job manager task, the job preparation task runs before the job manager task and before all other tasks. The job preparation task always runs first.
-The job preparation task is executed only on nodes that are scheduled to run a task. This prevents the unnecessary execution of a preparation task in case a node is not assigned any tasks. This can occur when the number of tasks for a job is less than the number of nodes in a pool. It also applies when [concurrent task execution](batch-parallel-node-tasks.md) is enabled, which leaves some nodes idle if the task count is lower than the total possible concurrent tasks.
+The job preparation task runs only on nodes that are scheduled to run a task. This behavior prevents unnecessary runs on nodes that aren't assigned any tasks. Nodes might not be assigned any tasks when the number of job tasks is less than the number of nodes in the pool. This behavior also applies when [concurrent task execution](batch-parallel-node-tasks.md) is enabled, which leaves some nodes idle if the task count is lower than the total possible concurrent tasks.
> [!NOTE]
-> [JobPreparationTask](/dotnet/api/microsoft.azure.batch.cloudjob.jobpreparationtask) differs from [CloudPool.StartTask](/dotnet/api/microsoft.azure.batch.cloudpool.starttask) in that JobPreparationTask executes at the start of each job, whereas StartTask executes only when a compute node first joins a pool or restarts.
+> [JobPreparationTask](/dotnet/api/microsoft.azure.batch.cloudjob.jobpreparationtask) differs from [CloudPool.StartTask](/dotnet/api/microsoft.azure.batch.cloudpool.starttask) in that `JobPreparationTask` runs at the start of each job, whereas `StartTask` runs only when a compute node first joins a pool or restarts.
## Job release task
-Once a job is marked as completed, the job release task runs on each node in the pool that executed at least one task. You mark a job as completed by issuing a terminate request. This request sets the job state to *terminating*, terminates any active or running tasks associated with the job, and runs the job release task. The job then moves to the *completed* state.
+Once you mark a job as completed, the job release task runs on each node in the pool that ran at least one task. You mark a job as completed by issuing a terminate request. This request sets the job state to *terminating*, terminates any active or running tasks associated with the job, and runs the job release task. The job then moves to the *completed* state.
> [!NOTE]
-> Deleting a job also executes the job release task. However, if a job has already been terminated, the release task is not run a second time if the job is later deleted.
+> Deleting a job also executes the job release task. However, if a job is already terminated, the release task doesn't run a second time if the job is later deleted.
-Jobs release tasks can run for a maximum of 15 minutes before being terminated by the Batch service. For more information, see the [REST API reference documentation](/rest/api/batchservice/job/add#jobreleasetask).
+Job release tasks can run for a maximum of 15 minutes before the Batch service terminates them. For more information, see the [REST API reference documentation](/rest/api/batchservice/job/add#jobreleasetask).
-## Job prep and release tasks with Batch .NET
+## Job preparation and release tasks with Batch .NET
-To use a job preparation task, assign a [JobPreparationTask](/dotnet/api/microsoft.azure.batch.jobpreparationtask) object to your job's [CloudJob.JobPreparationTask](/dotnet/api/microsoft.azure.batch.cloudjob.jobpreparationtask) property. Similarly, to use a job release task, initialize a [JobReleaseTask](/dotnet/api/microsoft.azure.batch.jobreleasetask) and assign it to your job's [CloudJob.JobReleaseTask](/dotnet/api/microsoft.azure.batch.cloudjob.jobreleasetask).
+To run a job preparation task, assign a [JobPreparationTask](/dotnet/api/microsoft.azure.batch.jobpreparationtask) object to your job's [CloudJob.JobPreparationTask](/dotnet/api/microsoft.azure.batch.cloudjob.jobpreparationtask) property. Similarly, to use a job release task, initialize a [JobReleaseTask](/dotnet/api/microsoft.azure.batch.jobreleasetask) and assign it to your job's [CloudJob.JobReleaseTask](/dotnet/api/microsoft.azure.batch.cloudjob.jobreleasetask).
-In this code snippet, `myBatchClient` is an instance of [BatchClient](/dotnet/api/microsoft.azure.batch.batchclient), and `myPool` is an existing pool within the Batch account.
+In the following code snippet, `myBatchClient` is an instance of [BatchClient](/dotnet/api/microsoft.azure.batch.batchclient), and `myPool` is an existing pool within the Batch account.
```csharp // Create the CloudJob for CloudPool "myPool"
myJob.JobReleaseTask =
await myJob.CommitAsync(); ```
-As mentioned earlier, the release task is executed when a job is terminated or deleted. Terminate a job with [JobOperations.TerminateJobAsync](/dotnet/api/microsoft.azure.batch.joboperations.terminatejobasync). Delete a job with [JobOperations.DeleteJobAsync](/dotnet/api/microsoft.azure.batch.joboperations.deletejobasync). You typically terminate or delete a job when its tasks are completed, or when a timeout that you've defined has been reached.
+The job release task runs when a job is terminated or deleted. You terminate a job by using [JobOperations.TerminateJobAsync](/dotnet/api/microsoft.azure.batch.joboperations.terminatejobasync), and delete a job by using [JobOperations.DeleteJobAsync](/dotnet/api/microsoft.azure.batch.joboperations.deletejobasync). You typically terminate or delete a job when its tasks are completed, or when a timeout you define is reached.
```csharp
-// Terminate the job to mark it as completed; this will initiate the
-// job release task on any node that executed job tasks. Note that the
-// job release task is also executed when a job is deleted, so you don't
+// Terminate the job to mark it as completed. Terminate initiates the
+// job release task on any node that ran job tasks. Note that the
+// job release task also runs when a job is deleted, so you don't
// have to call Terminate if you delete jobs after task completion. await myBatchClient.JobOperations.TerminateJobAsync("JobPrepReleaseSampleJob");
await myBatchClient.JobOperations.TerminateJobAsync("JobPrepReleaseSampleJob");
## Code sample on GitHub
-To see job preparation and release tasks in action, check out the [JobPrepRelease](https://github.com/Azure-Samples/azure-batch-samples/tree/master/CSharp/ArticleProjects/JobPrepRelease) sample project on GitHub. This console application does the following:
+To see job preparation and release tasks in action, build and run the [JobPrepRelease](https://github.com/Azure-Samples/azure-batch-samples/tree/master/CSharp/ArticleProjects/JobPrepRelease) sample project from GitHub. This console application takes the following actions:
1. Creates a pool with two nodes. 1. Creates a job with job preparation, release, and standard tasks.
-1. Runs the job preparation task, which first writes the node ID to a text file in a node's "shared" directory.
+1. Runs the job preparation task, which first writes the node ID to a text file in a node's *shared* directory.
1. Runs a task on each node that writes its task ID to the same text file.
-1. Once all tasks are completed (or the timeout is reached), prints the contents of each node's text file to the console.
-1. When the job is completed, runs the job release task to delete the file from the node.
-1. Prints the exit codes of the job preparation and release tasks for each node on which they executed.
+1. Once all tasks are completed or the timeout is reached, prints the contents of each node's text file to the console.
+1. Runs the job release task to delete the file from the node when the job is completed.
+1. Prints the exit codes of the job preparation and release tasks for each node they ran on.
1. Pauses execution to allow confirmation of job and/or pool deletion.
-Output from the sample application is similar to the following:
+Output from the sample application is similar to the following example:
-```
+```output
Attempting to create pool: JobPrepReleaseSamplePool Created pool JobPrepReleaseSamplePool with 2 nodes Checking for existing job JobPrepReleaseSampleJob...
Sample complete, hit ENTER to exit...
``` > [!NOTE]
-> Due to the variable creation and start time of nodes in a new pool (some nodes are ready for tasks before others), you may see different output. Specifically, because the tasks complete quickly, one of the pool's nodes may execute all of the job's tasks. If this occurs, you will notice that the job prep and release tasks do not exist for the node that executed no tasks.
+> The varying creation and start times of nodes in a new pool means some nodes are ready for tasks before others, so you might see different output. Specifically, because the tasks complete quickly, one of the pool's nodes might run all of the job's tasks. If this occurs, the job preparation and release tasks don't exist for the node that ran no tasks.
+
+## View job preparation and release tasks in the Azure portal
+
+You can use the [Azure portal](https://portal.azure.com) to view Batch job properties and tasks, including job preparation and release tasks. From your Batch account page, select **Jobs** from the left navigation and then select a job. If you run the sample application, navigate to the job page after the tasks complete, but before you delete the job and pool.
-### Inspect job preparation and release tasks in the Azure portal
+You can monitor job progress and status by expanding **Approximate task count** on the job **Overview** or **Tasks** page.
-You can use the [Azure portal](https://portal.azure.com) to view the properties of the job and its tasks. After you run the sample application, you can also download the shared text file that is modified by the job's tasks.
-The screenshot below shows the **Preparation tasks blade** in the Azure portal. Navigate to the *JobPrepReleaseSampleJob* properties after your tasks have completed (but before deleting your job and pool) and click **Preparation tasks** or **Release tasks** to view their properties.
+The following screenshot shows the **JobPrepReleaseSampleJob** page after the sample application runs. This job had preparation and release tasks, so you can select **Preparation tasks** or **Release tasks** in the left navigation to see their properties.
## Next steps
batch Quick Create Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/batch/quick-create-bicep.md
Last updated 03/22/2022 -+ tags: azure-resource-manager, bicep
batch Quick Create Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/batch/quick-create-template.md
Title: Azure Quickstart - Create a Batch account - Azure Resource Manager templa
description: This quickstart shows how to create a Batch account by using an ARM template. Last updated 05/25/2021 -+ # Quickstart: Create a Batch account by using ARM template
batch Simplified Node Communication Pool No Public Ip https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/batch/simplified-node-communication-pool-no-public-ip.md
Title: Create a simplified node communication pool without public IP addresses
description: Learn how to create an Azure Batch simplified node communication pool without public IP addresses. Last updated 12/16/2022-+ # Create a simplified node communication pool without public IP addresses
cdn Create Profile Endpoint Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cdn/create-profile-endpoint-bicep.md
na -+ Last updated 03/14/2022
cdn Create Profile Endpoint Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cdn/create-profile-endpoint-template.md
na -+ Last updated 02/27/2023
certification How To Test Pnp https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/certification/how-to-test-pnp.md
Last updated 01/28/2022-+ # How to test IoT Plug and Play devices
When a device is certified, you can choose to publish your product details to th
## Next steps
-Now the device submission is completed, you can contact the device certification team at [iotcert@microsoft.com](mailto:iotcert@microsoft.com) to continue to the next steps, which include Microsoft Partner Network membership validation and a review of the getting started guides. When all the requirements are satisfied, you can choose to have your device included in the [Certified for Azure IoT device catalog](https://devicecatalog.azure.com).
+Now the device submission is completed, you can contact the device certification team at [iotcert@microsoft.com](mailto:iotcert@microsoft.com) to continue to the next steps, which include Microsoft Partner Network membership validation and a review of the getting started guides. When all the requirements are satisfied, you can choose to have your device included in the [Certified for Azure IoT device catalog](https://devicecatalog.azure.com).
chaos-studio Sample Template Experiment https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/chaos-studio/sample-template-experiment.md
Last updated 11/10/2021 + # Resource Manager template samples for experiments in Azure Chaos Studio
chaos-studio Sample Template Targets https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/chaos-studio/sample-template-targets.md
Last updated 11/10/2021 + # Resource Manager template samples for targets and capabilities in Azure Chaos Studio
cloud-services-extended-support Deploy Visual Studio https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cloud-services-extended-support/deploy-visual-studio.md
description: Learn now to create and deploy an Azure Cloud Service using Azure R
-+ Last updated 10/5/2020
To clean up the Azure resources you created by following this tutorial, go to th
## Next steps
-Set up continuous integration (CI) using the **Configure** button on the **Publish** screen. For more information, see [Azure Pipelines documentation](/azure/devops/pipelines).
+Set up continuous integration (CI) using the **Configure** button on the **Publish** screen. For more information, see [Azure Pipelines documentation](/azure/devops/pipelines).
cloud-services-extended-support Enable Wad https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cloud-services-extended-support/enable-wad.md
Last updated 10/13/2020-+ # Apply the Windows Azure diagnostics extension in Cloud Services (extended support)
cloud-services-extended-support Generate Template Portal https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cloud-services-extended-support/generate-template-portal.md
Last updated 03/07/2021-+ # Generate ARM Template for Cloud Services (extended support) using the Azure portal
cloud-services-extended-support Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cloud-services-extended-support/overview.md
Last updated 10/13/2020-+ # About Azure Cloud Services (extended support)
cloud-services-extended-support Swap Cloud Service https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cloud-services-extended-support/swap-cloud-service.md
Title: Swap or switch deployments in Azure Cloud Services (extended support)
description: Learn how to swap or switch between deployments in Azure Cloud Services (extended support). +
cloud-services Cloud Services Powershell Create Cloud Container https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cloud-services/cloud-services-powershell-create-cloud-container.md
Last updated 02/21/2023
-+ # Use an Azure PowerShell command to create an empty cloud service (classic) container
Get-help New-AzureService
### Next steps * To manage the cloud service deployment, refer to the [Get-AzureService](/powershell/module/servicemanagement/azure.service/Get-AzureService), [Remove-AzureService](/powershell/module/servicemanagement/azure.service/Remove-AzureService), and [Set-AzureService](/powershell/module/servicemanagement/azure.service/set-azureservice) commands. You may also refer to [How to configure cloud services](cloud-services-how-to-configure-portal.md) for further information.
-* To publish your cloud service project to Azure, refer to the **PublishCloudService.ps1** code sample from [archived cloud services repository](https://github.com/MicrosoftDocs/azure-cloud-services-files/tree/master/Scripts/cloud-services-continuous-delivery).
+* To publish your cloud service project to Azure, refer to the **PublishCloudService.ps1** code sample from [archived cloud services repository](https://github.com/MicrosoftDocs/azure-cloud-services-files/tree/master/Scripts/cloud-services-continuous-delivery).
cognitive-services Deploy Anomaly Detection On Container Instances https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/Anomaly-Detector/How-to/deploy-anomaly-detection-on-container-instances.md
+ Last updated 04/01/2020
Learn how to deploy the Cognitive Services [Anomaly Detector](../anomaly-detecto
* Review [Install and run containers](../anomaly-detector-container-configuration.md) for pulling the container image and run the container * Review [Configure containers](../anomaly-detector-container-configuration.md) for configuration settings
-* [Learn more about Anomaly Detector API service](https://go.microsoft.com/fwlink/?linkid=2080698&clcid=0x409)
+* [Learn more about Anomaly Detector API service](https://go.microsoft.com/fwlink/?linkid=2080698&clcid=0x409)
cognitive-services Platform Upgrade https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/Translator/custom-translator/platform-upgrade.md
> > On June 02, 2023, Microsoft will retire the Custom Translator v1.0 model platform. Existing v1.0 models must migrate to the v2.0 platform for continued processing and support.
-Following measured and consistent high-quality results using models trained on the Custom Translator v2.0 platform, the v1.0 platform will be retired. Custom Translator v2.0 delivers significant improvements in many domains compared to both standard and Custom v1.0 platform translations. Migrate your v1.0 models to the v2.0 platform by June 02, 2023.
+Following measured and consistent high-quality results using models trained on the Custom Translator v2.0 platform, the v1.0 platform is retiring. Custom Translator v2.0 delivers significant improvements in many domains compared to both standard and Custom v1.0 platform translations. Migrate your v1.0 models to the v2.0 platform by June 02, 2023.
## Custom Translator v1.0 upgrade timeline
Following measured and consistent high-quality results using models trained on t
## Upgrade to v2.0
+> [!IMPORTANT]
+>
+> * Starting **May 01, 2023** the upgrade wizard and workspace banner will be displayed in the Custom Translator portal indicating that you have v1.0 models to upgrade.
+> * The banner contains a **Select** button that takes you to the upgrade wizard where a list of all your v1.0 models available for upgrade are displayed.
+> * Select any or all of your v1.0 models then select **Train** to start v2.0 model upgrade training.
+ * **Check to see if you have published v1.0 models**. After signing in to the Custom Translator portal, you'll see a message indicating that you have v1.0 models to upgrade. You can also check to see if a current workspace has v1.0 models by selecting **Workspace settings** and scrolling to the bottom of the page. * **Use the upgrade wizard**. Follow the steps listed in **Upgrade to the latest version** wizard. Depending on your training data size, it may take from a few hours to a full day to upgrade your models to the v2.0 platform.
cognitive-services Cognitive Services Custom Subdomains https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/cognitive-services-custom-subdomains.md
+ Last updated 12/04/2020
Yes. This is a list of regional endpoints that you can use with Azure Cognitive
## See also * [What are the Cognitive Services?](./what-are-cognitive-services.md)
-* [Authentication](authentication.md)
+* [Authentication](authentication.md)
cognitive-services Create Account Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/create-account-bicep.md
Last updated 01/19/2023 -+ # Quickstart: Create a Cognitive Services resource using Bicep
cognitive-services Create Account Resource Manager Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/create-account-resource-manager-template.md
Last updated 09/01/2022 -+ # Quickstart: Create a Cognitive Services resource using an ARM template
cognitive-services Best Practices https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/language-service/conversational-language-understanding/concepts/best-practices.md
-+ Last updated 10/11/2022
cognitive-services Faq https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/language-service/conversational-language-understanding/faq.md
-+ Last updated 09/29/2022
cognitive-services Faq https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/language-service/custom-named-entity-recognition/faq.md
-+ Last updated 08/08/2022
cognitive-services Faq https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/language-service/custom-text-classification/faq.md
-+ Last updated 04/22/2022
cognitive-services Faq https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/language-service/orchestration-workflow/faq.md
-+ Last updated 06/21/2022
cognitive-services Whats New https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/language-service/whats-new.md
-+ Last updated 03/09/2023
cognitive-services Managed Identity https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/openai/how-to/managed-identity.md
Last updated 06/24/2022
recommendations: false-+ # How to Configure Azure OpenAI Service with Managed Identities
cognitive-services How To Feature Evaluation https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/how-to-feature-evaluation.md
ms. -+ Last updated 09/22/2022
cognitive-services How To Inference Explainability https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/how-to-inference-explainability.md
ms. -+ Last updated 09/20/2022
cognitive-services How To Thick Client https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/how-to-thick-client.md
-+ Last updated 09/06/2022
cognitive-services Responsible Characteristics And Limitations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/responsible-characteristics-and-limitations.md
Last updated 05/23/2022-+
cognitive-services Responsible Data And Privacy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/responsible-data-and-privacy.md
Last updated 05/23/2022-+ # Data and privacy for Personalizer
cognitive-services Responsible Guidance Integration https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/responsible-guidance-integration.md
Last updated 05/23/2022-+
cognitive-services Responsible Use Cases https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/responsible-use-cases.md
Last updated 05/23/2022-+ # Use cases for Personalizer
cognitive-services Whats New https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cognitive-services/personalizer/whats-new.md
ms. -+ Last updated 05/28/2021 # What's new in Personalizer
communication-services Certified Session Border Controllers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/communication-services/concepts/telephony/certified-session-border-controllers.md
# List of Session Border Controllers certified for Azure Communication Services direct routing This document contains a list of Session Border Controllers certified for Azure Communication Services direct routing. It also includes known limitations.
-Microsoft is working with the selected Session Border Controllers (SBC) vendors certified for Teams Direct Routing to work with Azure direct routing. You can watch the progress on this page. While the SBC, certified for Teams Direct Routing, can work with Azure direct routing, we encourage not to put any workload on the SBC until it appears on this page. We also do not support the uncertified SBC. While Azure direct routing is built on the same backend as Teams Direct Routing, there are some differences. The certification covers comprehensive validation of the SBC for the Azure direct routing.
+Microsoft is working with the selected Session Border Controllers (SBC) vendors certified for Teams Direct Routing to work with Azure direct routing. You can watch the progress on this page. While the SBC, certified for Teams Direct Routing, can work with Azure direct routing, we encourage not to put any workload on the SBC until it appears on this page. We also don't support the uncertified SBC. While Azure direct routing is built on the same backend as Teams Direct Routing, there are some differences. The certification covers comprehensive validation of the SBC for the Azure direct routing.
Microsoft works with each vendor to: - Jointly work on the SIP interconnection protocols. - Perform intense tests using a third-party lab. Only devices that pass the tests are certified.-- Run daily tests with all certified devices in production and pre-production environments. Validating the devices in pre-production environments guarantees that new versions of Azure Communication Services code in the cloud will work with certified SBCs.
+- Run daily tests with all certified devices in production and preproduction environments. Validating the devices in preproduction environments guarantees that new versions of Azure Communication Services code in the cloud work with certified SBCs.
- Establish a joint support process with the SBC vendors. [!INCLUDE [Public Preview](../../includes/public-preview-include-document.md)] [!INCLUDE [Dynamics 365 Omnichannel Notice](../includes/direct-routing-omnichannel-note.md)] Media bypass is not yet supported by Azure Communication Services.
-Early media is not supported by a web-based client.
The table that follows list devices certified for Azure Communication Services direct routing. If you have any questions about the SBC certification program for Communication Services direct routing, contact acsdrcertification@microsoft.com.
confidential-computing Quick Create Confidential Vm Arm Amd https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/confidential-computing/quick-create-confidential-vm-arm-amd.md
Last updated 7/14/2022 -+ ms.devlang: azurecli
confidential-computing Virtual Machine Solutions Amd https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/confidential-computing/virtual-machine-solutions-amd.md
+ Last updated 3/29/2023
Make sure to specify the following properties for your VM in the parameters sect
> [!div class="nextstepaction"] > [Deploy a confidential VM on AMD from the Azure portal](quick-create-confidential-vm-portal-amd.md)-
confidential-computing Virtual Machine Solutions Sgx https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/confidential-computing/virtual-machine-solutions-sgx.md
Last updated 12/20/2021 -+ # Solutions on Azure for Intel SGX
confidential-ledger Quickstart Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/confidential-ledger/quickstart-cli.md
Last updated 03/22/2022 + - # Quickstart: Create a confidential ledger using the Azure CLI
confidential-ledger Quickstart Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/confidential-ledger/quickstart-template.md
-+ Last updated 11/14/2022
container-apps Azure Arc Create Container App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/azure-arc-create-container-app.md
description: Get started with Azure Container Apps on Azure Arc-enabled Kubernet
+ Last updated 3/20/2023
container-apps Azure Resource Manager Api Spec https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/azure-resource-manager-api-spec.md
Last updated 05/26/2022 -+ # Container Apps ARM template API specification
container-apps Container Console https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/container-console.md
description: Connect to a container console in your container app.
-+ Last updated 08/30/2022
az containerapp exec `
> [!div class="nextstepaction"]
-> [View log streams from the Azure portal](log-streaming.md)
+> [View log streams from the Azure portal](log-streaming.md)
container-apps Containers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/containers.md
The following code is an example of the `containers` array in the [`properties.t
| `volumeMounts` | An array of volume mount definitions. | You can define a temporary volume or multiple permanent storage volumes for your container. For more information about storage volumes, see [Use storage mounts in Azure Container Apps](storage-mounts.md).| | `probes`| An array of health probes enabled in the container. | This feature is based on Kubernetes health probes. For more information about probes settings, see [Health probes in Azure Container Apps](health-probes.md).|
+<a id="allocations"></a>
+ In the Consumption plan, the total CPU and memory allocations requested for all the containers in a container app must add up to one of the following combinations. | vCPUs (cores) | Memory |
container-apps Github Actions Cli https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/github-actions-cli.md
description: Learn to automatically create GitHub Actions workflow in Azure Cont
-+ Last updated 11/09/2022
container-apps Ingress Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/ingress-overview.md
HTTP ingress adds headers to pass metadata about the client request to your cont
| `X-Forwarded-For` | The IP address of the client that sent the request. | | | `X-Forwarded-Host` | The host name the client used to connect with the Container Apps service. | |
-### <a name="tcp"></a>TCP (preview)
+### <a name="tcp"></a>TCP
Container Apps supports TCP-based protocols other than HTTP or HTTPS. For example, you can use TCP ingress to expose a container app that uses the [Redis protocol](https://redis.io/topics/protocol). > [!NOTE]
-> TCP ingress is in public preview.  External TCP ingress setting is only supported in Container Apps environments that use a [custom VNET](vnet-custom.md).
+> External TCP ingress is only supported for Container Apps environments that use a [custom VNET](vnet-custom.md).
With TCP ingress enabled, your container app:
container-apps Log Options https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/log-options.md
description: Description of logging options in Azure Container Apps
+ Last updated 09/29/2022
container-apps Log Streaming https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/log-streaming.md
description: View your container app's log stream.
+ Last updated 03/24/2023
az containerapp env logs show `
> [!div class="nextstepaction"]
-> [Log storage and monitoring options in Azure Container Apps](log-monitoring.md)
+> [Log storage and monitoring options in Azure Container Apps](log-monitoring.md)
container-apps Manage Secrets https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/manage-secrets.md
Previously updated : 09/29/2022 Last updated : 04/06/2023 # Manage secrets in Azure Container Apps
-Azure Container Apps allows your application to securely store sensitive configuration values. Once secrets are defined at the application level, secured values are available to container apps. Specifically, you can reference secured values inside scale rules. For information on using secrets with Dapr, refer to [Dapr integration](./dapr-overview.md)
+Azure Container Apps allows your application to securely store sensitive configuration values. Once secrets are defined at the application level, secured values are available to revisions in your container apps. Additionally, you can reference secured values inside scale rules. For information on using secrets with Dapr, refer to [Dapr integration](./dapr-overview.md).
- Secrets are scoped to an application, outside of any specific revision of an application. - Adding, removing, or changing secrets doesn't generate new revisions.
An updated or deleted secret doesn't automatically affect existing revisions in
Before you delete a secret, deploy a new revision that no longer references the old secret. Then deactivate all revisions that reference the secret.
-> [!NOTE]
-> Container Apps doesn't support Azure Key Vault integration. Instead, enable managed identity in the container app and use the [Key Vault SDK](../key-vault/general/developers-guide.md) in your app to access secrets.
+## Defining secrets
+Secrets are defined as a set of name/value pairs. The value of each secret is specified directly or as a reference to a secret stored in Azure Key Vault.
-## Defining secrets
+### Store secret value in Container Apps
+
+When you define secrets through the portal, or via different command line options.
+
+# [Azure portal](#tab/azure-portal)
+
+1. Go to your container app in the [Azure portal](https://portal.azure.com).
+
+1. Under the *Settings* section, select **Secrets**.
+
+1. Select **Add**.
+
+1. In the *Add secret* context pane, enter the following information:
+
+ - **Name**: The name of the secret.
+ - **Type**: Select **Container Apps Secret**.
+ - **Value**: The value of the secret.
+
+1. Select **Add**.
# [ARM template](#tab/arm-template)
az containerapp create \
--name queuereader \ --environment "my-environment-name" \ --image demos/queuereader:v1 \
- --secrets "queue-connection-string=$CONNECTION_STRING"
+ --secrets "queue-connection-string=<CONNECTION_STRING>"
```
-Here, a connection string to a queue storage account is declared in the `--secrets` parameter. The value for `queue-connection-string` comes from an environment variable named `$CONNECTION_STRING`.
+Here, a connection string to a queue storage account is declared in the `--secrets` parameter. Replace `<CONNECTION_STRING>` with the value of your connection string.
# [PowerShell](#tab/powershell)
Here, a connection string to a queue storage account is declared. The value for
+### <a name="reference-secret-from-key-vault"></a>Reference secret from Key Vault (preview)
+
+When you define a secret, you create a reference to a secret stored in Azure Key Vault. Container Apps automatically retrieves the secret value from Key Vault and makes it available as a secret in your container app.
+
+To reference a secret from Key Vault, you must first enable managed identity in your container app and grant the identity access to the Key Vault secrets.
+
+To enable managed identity in your container app, see [Managed identities](managed-identity.md).
+
+To grant access to Key Vault secrets, [create an access policy](../key-vault/general/assign-access-policy.md) in Key Vault for the managed identity you created. Enable the "Get" secret permission on this policy.
+
+# [Azure portal](#tab/azure-portal)
+
+1. Go to your container app in the [Azure portal](https://portal.azure.com).
+
+1. Under the *Settings* section, select **Identity**.
+
+1. In the *System assigned* tab, select **On**.
+
+1. Select **Save** to enable system-assigned managed identity.
+
+1. Under the *Settings* section, select **Secrets**.
+
+1. Select **Add**.
+
+1. In the *Add secret* context pane, enter the following information:
+
+ - **Name**: The name of the secret.
+ - **Type**: Select **Key Vault reference**.
+ - **Key Vault secret URL**: The URI of your secret in Key Vault.
+ - **Identity**: The identity to use to retrieve the secret from Key Vault.
+
+1. Select **Add**.
+
+# [ARM template](#tab/arm-template)
+
+Secrets are defined at the application level in the `resources.properties.configuration.secrets` section.
+
+```json
+"resources": [
+{
+ ...
+ "properties": {
+ "configuration": {
+ "secrets": [
+ {
+ "name": "queue-connection-string",
+ "keyVaultUrl": "<KEY-VAULT-SECRET-URI>",
+ "identity": "System"
+ }],
+ }
+ }
+}
+```
+
+Here, a connection string to a queue storage account is declared in the `secrets` array. Its value is automatically retrieved from Key Vault using the specified identity. To use a user managed identity, replace `System` with the identity's resource ID.
+
+Replace `<KEY-VAULT-SECRET-URI>` with the URI of your secret in Key Vault.
+
+# [Azure CLI](#tab/azure-cli)
+
+When you create a container app, secrets are defined using the `--secrets` parameter.
+
+- The parameter accepts a space-delimited set of name/value pairs.
+- Each pair is delimited by an equals sign (`=`).
+- To specify a Key Vault reference, use the format `<SECRET_NAME>=keyvaultref:<KEY_VAULT_SECRET_URI>,identityref:<MANAGED_IDENTITY_ID>`. For example, `queue-connection-string=keyvaultref:https://mykeyvault.vault.azure.net/secrets/queuereader,identityref:/subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/my-resource-group/providers/Microsoft.ManagedIdentity/userAssignedIdentities/my-identity`.
+
+```bash
+az containerapp create \
+ --resource-group "my-resource-group" \
+ --name queuereader \
+ --environment "my-environment-name" \
+ --image demos/queuereader:v1 \
+ --user-assigned "<USER_ASSIGNED_IDENTITY_ID>" \
+ --secrets "queue-connection-string=keyvaultref:<KEY_VAULT_SECRET_URI>,identityref:<USER_ASSIGNED_IDENTITY_ID>"
+```
+
+Here, a connection string to a queue storage account is declared in the `--secrets` parameter. Replace `<KEY_VAULT_SECRET_URI>` with the URI of your secret in Key Vault. Replace `<USER_ASSIGNED_IDENTITY_ID>` with the resource ID of the user assigned identity. For system assigned identity, use `System` instead of the resource ID.
+
+> [!NOTE]
+> The user assigned identity must have access to read the secret in Key Vault. System assigned identity can't be used with the create command because it's not available until after the container app is created.
+
+# [PowerShell](#tab/powershell)
+
+Secrets Key Vault references aren't supported in PowerShell.
+++
+#### Key Vault secret URI and secret rotation
+
+The Key Vault secret URI must be in one of the following formats:
+
+* `https://myvault.vault.azure.net/secrets/mysecret/ec96f02080254f109c51a1f14cdb1931`: Reference a specific version of a secret.
+* `https://myvault.vault.azure.net/secrets/mysecret`: Reference the latest version of a secret.
+
+If a version isn't specified in the URI, then the app uses the latest version that exists in the key vault. When newer versions become available, the app automatically retrieves the latest version within 30 minutes. Any active revisions that reference the secret in an environment variable is automatically restarted to pick up the new value.
+
+For full control of which version of a secret is used, specify the version in the URI.
+ ## <a name="using-secrets"></a>Referencing secrets in environment variables After declaring secrets at the application level as described in the [defining secrets](#defining-secrets) section, you can reference them in environment variables when you create a new revision in your container app. When an environment variable references a secret, its value is populated with the value defined in the secret.
-## Example
+### Example
The following example shows an application that declares a connection string at the application level. This connection is referenced in a container environment variable and in a scale rule.
+# [Azure portal](#tab/azure-portal)
+
+After you've [defined a secret](#defining-secrets) in your container app, you can reference it in an environment variable when you create a new revision.
+
+1. Go to your container app in the [Azure portal](https://portal.azure.com).
+
+1. Open the *Revision management* page.
+
+1. Select **Create new revision**.
+
+1. In the *Create and deploy new revision* page, select a container.
+
+1. In the *Environment variables* section, select **Add**.
+
+1. Enter the following information:
+
+ - **Name**: The name of the environment variable.
+ - **Source**: Select **Reference a secret**.
+ - **Value**: Select the secret you want to reference.
+
+1. Select **Save**.
+
+1. Select **Create** to create the new revision.
+ # [ARM template](#tab/arm-template) In this example, the application connection string is declared as `queue-connection-string` and becomes available elsewhere in the configuration sections.
container-apps Microservices Dapr Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/microservices-dapr-azure-resource-manager.md
Last updated 06/29/2022 -+ zone_pivot_groups: container-apps
container-apps Scale App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-apps/scale-app.md
description: Learn how applications scale in and out in Azure Container Apps.
+ Last updated 12/08/2022
container-instances Availability Zones https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/availability-zones.md
Last updated 06/17/2022-+ # Deploy an Azure Container Instances (ACI) container group in an availability zone (preview)
container-instances Container Instances Exec https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-exec.md
+ Last updated 06/17/2022
Learn about other troubleshooting tools and common deployment issues in [Trouble
<!-- LINKS - internal --> [az-container-create]: /cli/azure/container#az_container_create [az-container-exec]: /cli/azure/container#az_container_exec
-[azure-cli]: /cli/azure
+[azure-cli]: /cli/azure
container-instances Container Instances Monitor https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-monitor.md
+ Last updated 06/17/2022
container-instances Container Instances Multi Container Group https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-multi-container-group.md
Last updated 06/17/2022-+ # Tutorial: Deploy a multi-container group using a Resource Manager template
container-instances Container Instances Multi Container Yaml https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-multi-container-yaml.md
+ Last updated 06/17/2022
container-instances Container Instances Quickstart Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-quickstart-bicep.md
Last updated 03/10/2022 -+ # Quickstart: Deploy a container instance in Azure using Bicep
Remove-AzResourceGroup -Name exampleRG
In this quickstart, you created an Azure container instance using Bicep. If you'd like to build a container image and deploy it from a private Azure container registry, continue to the Azure Container Instances tutorial. > [!div class="nextstepaction"]
-> [Tutorial: Create a container image for deployment to Azure Container Instances](./container-instances-tutorial-prepare-app.md)
+> [Tutorial: Create a container image for deployment to Azure Container Instances](./container-instances-tutorial-prepare-app.md)
container-instances Container Instances Quickstart Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-quickstart-template.md
Last updated 06/17/2022-+ # Quickstart: Deploy a container instance in Azure using an ARM template
container-instances Container Instances Samples Rm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-samples-rm.md
description: Find Azure Resource Manager template samples to deploy Azure Contai
+ Last updated 06/17/2022
container-instances Container Instances Start Command https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-start-command.md
+ Last updated 06/17/2022
container-instances Container Instances Tutorial Deploy Confidential Containers Cce Arm https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-tutorial-deploy-confidential-containers-cce-arm.md
Last updated 02/28/2023-+ # Tutorial: Create an ARM template for a confidential container deployment with custom confidential computing enforcement policy (preview)
container-instances Container Instances Using Azure Container Registry https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-using-azure-container-registry.md
Last updated 06/17/2022-+ # Deploy to Azure Container Instances from Azure Container Registry using a service principal
For more information about Azure Container Registry authentication, see [Authent
[az-acr-show]: /cli/azure/acr#az_acr_show [az-ad-sp-create-for-rbac]: /cli/azure/ad/sp#az_ad_sp_create_for_rbac [az-container-create]: /cli/azure/container#az_container_create
-[az-keyvault-secret-set]: /cli/azure/keyvault/secret#az_keyvault_secret_set
+[az-keyvault-secret-set]: /cli/azure/keyvault/secret#az_keyvault_secret_set
container-instances Container Instances Volume Gitrepo https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-volume-gitrepo.md
+ Last updated 06/17/2022
container-instances Container Instances Volume Secret https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/container-instances-volume-secret.md
+ Last updated 06/17/2022
container-instances How To Reuse Dns Names https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/how-to-reuse-dns-names.md
You now have the choice when creating an ACI to choose what level of reuse you w
| Policy name | Policy definition | | - | - |
-| unsecure | Hash will be generated based on only the DNS name. Avoiding subdomain takeover is not guaranteed if another customer uses the same DNS name. |
+| unsecure | Hash will not be generated. Object's domain label can't be reused within resource group, subscription, or tenant. |
| tenantReuse | **Default** Hash will be generated based on the DNS name and the tenant ID. Object's domain name label can be reused within the same tenant. | | subscriptionReuse | Hash will be generated based on the DNS name and the tenant ID and subscription ID. Object's domain name label can be reused within the same subscription. | | resourceGroupReuse | Hash will be generated based on the DNS name and the tenant ID, subscription ID, and resource group name. Object's domain name label can be reused within the same resource group. |
-| noReuse | Hash will not be generated. Object's domain label can't be reused within resource group, subscription, or tenant. |
+| noReuse | Hash will be generated using a GUID. Object's domain label can be reused freely, as this hash will always be unique. |
## Create a container instance
container-instances Using Azure Container Registry Mi https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-instances/using-azure-container-registry-mi.md
Last updated 06/17/2022-+ # Deploy to Azure Container Instances from Azure Container Registry using a managed identity
container-registry Container Registry Delete https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-registry/container-registry-delete.md
Title: Delete image resources description: Details on how to effectively manage registry size by deleting container image data using Azure CLI commands. + Last updated 10/11/2022
container-registry Container Registry Enable Conditional Access Policy https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-registry/container-registry-enable-conditional-access-policy.md
Title: Configure conditional access to your Azure Container Registry description: Learn how to configure conditional access to your registry by using Azure CLI and Azure portal. + Last updated 09/13/2021
Create a Conditional Access policy and assign your test group of users as follow
* Learn more about [Azure Policy definitions](../governance/policy/concepts/definition-structure.md) and [effects](../governance/policy/concepts/effects.md). * Learn more about [common access concerns that Conditional Access policies can help with](../active-directory/conditional-access/concept-conditional-access-policy-common.md).
-* Learn more about [Conditional Access policy components](../active-directory/conditional-access/concept-conditional-access-policies.md).
+* Learn more about [Conditional Access policy components](../active-directory/conditional-access/concept-conditional-access-policies.md).
container-registry Container Registry Get Started Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-registry/container-registry-get-started-bicep.md
Last updated 10/11/2022 -+ # Quickstart: Create a container registry by using a Bicep file
container-registry Container Registry Get Started Geo Replication Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-registry/container-registry-get-started-geo-replication-template.md
Last updated 10/11/2022 -+ # Quickstart: Create a geo-replicated container registry by using an ARM template
container-registry Container Registry Task Run Template https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-registry/container-registry-task-run-template.md
Title: Quick task run with template description: Queue an ACR task run to build an image using an Azure Resource Manager template -+ Last updated 10/11/2022
container-registry Container Registry Webhook https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/container-registry/container-registry-webhook.md
Title: Webhooks to respond to registry actions description: Learn how to use webhooks to trigger events when push or pull actions occur in your registry repositories. + Last updated 10/11/2022
cosmos-db How To Provision Throughput https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/cassandra/how-to-provision-throughput.md
Last updated 10/15/2020 ms.devlang: csharp-+ # Provision database, container or autoscale throughput on Azure Cosmos DB for Apache Cassandra resources
cosmos-db Manage With Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/cassandra/manage-with-bicep.md
description: Use Bicep to create and configure Azure Cosmos DB for Apache Cassan
-+ Last updated 9/13/2021
cosmos-db Powershell Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/cassandra/powershell-samples.md
description: Get the Azure PowerShell samples to perform common tasks in Azure
-+ Last updated 01/20/2021
cosmos-db Prevent Rate Limiting Errors https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/cassandra/prevent-rate-limiting-errors.md
description: Prevent your Azure Cosmos DB for Apache Cassandra operations from h
-+ Last updated 10/11/2021
cosmos-db Templates Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/cassandra/templates-samples.md
description: Use Azure Resource Manager templates to create and configure Azure
-+ Last updated 10/14/2020
cosmos-db Continuous Backup Restore Permissions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/continuous-backup-restore-permissions.md
Last updated 02/17/2023 -+ # Manage permissions to restore an Azure Cosmos DB account
cosmos-db How To Provision Throughput https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/gremlin/how-to-provision-throughput.md
Last updated 10/15/2020
ms.devlang: csharp-+ # Provision database, container or autoscale throughput on Azure Cosmos DB for Gremlin resources
cosmos-db Manage With Bicep https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/gremlin/manage-with-bicep.md
description: Use Bicep to create and configure Azure Cosmos DB for Gremlin.
-+ Last updated 9/13/2021
cosmos-db Powershell Samples https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/gremlin/powershell-samples.md
description: Get the Azure PowerShell samples to perform common tasks in Azure
-+ Last updated 01/20/2021
cosmos-db How To Create Multiple Cosmos Db Triggers https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/nosql/how-to-create-multiple-cosmos-db-triggers.md
Previously updated : 07/17/2019 Last updated : 04/07/2023 ms.devlang: csharp
The goal of this article is to guide you to accomplish the second option.
## Configuring a shared leases container
-To configure the shared leases container, the only extra configuration you need to make on your triggers is to add the `LeaseCollectionPrefix` [attribute](../../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#attributes) if you are using C# or `leaseCollectionPrefix` [attribute](../../azure-functions/functions-bindings-cosmosdb-v2-trigger.md) if you are using JavaScript. The value of the attribute should be a logical descriptor of what that particular trigger.
+To configure the shared leases container, the only extra configuration you need to make on your triggers is to add the `LeaseContainerPrefix` [attribute](../../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#attributes) if you are using C# or `leaseContainerPrefix` [attribute](../../azure-functions/functions-bindings-cosmosdb-v2-trigger.md) if you are using JavaScript. The value of the attribute should be a logical descriptor of what that particular trigger.
-For example, if you have three Triggers: one that sends emails, one that does an aggregation to create a materialized view, and one that sends the changes to another storage, for later analysis, you could assign the `LeaseCollectionPrefix` of "emails" to the first one, "materialized" to the second one, and "analytics" to the third one.
+For example, if you have three Triggers: one that sends emails, one that does an aggregation to create a materialized view, and one that sends the changes to another storage, for later analysis, you could assign the `LeaseContainerPrefix` of "emails" to the first one, "materialized" to the second one, and "analytics" to the third one.
The important part is that all three Triggers **can use the same leases container configuration** (account, database, and container name).
-A very simple code samples using the `LeaseCollectionPrefix` attribute in C#, would look like this:
+A very simple code samples using the `LeaseContainerPrefix` attribute in C#, would look like this:
```cs
-using Microsoft.Azure.Documents;
using Microsoft.Azure.WebJobs; using Microsoft.Azure.WebJobs.Host; using System.Collections.Generic;
using Microsoft.Extensions.Logging;
[FunctionName("SendEmails")] public static void SendEmails([CosmosDBTrigger( databaseName: "ToDoItems",
- collectionName: "Items",
- ConnectionStringSetting = "CosmosDBConnection",
- LeaseCollectionName = "leases",
- LeaseCollectionPrefix = "emails")]IReadOnlyList<Document> documents,
+ containerName: "Items",
+ Connection = "CosmosDBConnection",
+ LeaseContainerName = "leases",
+ LeaseContainerPrefix = "emails")]IReadOnlyList<MyItem> items,
ILogger log) { ...
public static void SendEmails([CosmosDBTrigger(
[FunctionName("MaterializedViews")] public static void MaterializedViews([CosmosDBTrigger( databaseName: "ToDoItems",
- collectionName: "Items",
- ConnectionStringSetting = "CosmosDBConnection",
- LeaseCollectionName = "leases",
- LeaseCollectionPrefix = "materialized")]IReadOnlyList<Document> documents,
+ containerName: "Items",
+ Connection = "CosmosDBConnection",
+ LeaseContainerName = "leases",
+ LeaseContainerPrefix = "materialized")]IReadOnlyList<MyItem> items,
ILogger log) { ... } ```
-And for JavaScript, you can apply the configuration on the `function.json` file, with the `leaseCollectionPrefix` attribute:
+And for JavaScript, you can apply the configuration on the `function.json` file, with the `leaseContainerPrefix` attribute:
```json { "type": "cosmosDBTrigger", "name": "documents", "direction": "in",
- "leaseCollectionName": "leases",
- "connectionStringSetting": "CosmosDBConnection",
+ "leaseContainerName": "leases",
+ "connection": "CosmosDBConnection",
"databaseName": "ToDoItems",
- "collectionName": "Items",
- "leaseCollectionPrefix": "emails"
+ "containerName": "Items",
+ "leaseContainerPrefix": "emails"
}, { "type": "cosmosDBTrigger", "name": "documents", "direction": "in",
- "leaseCollectionName": "leases",
- "connectionStringSetting": "CosmosDBConnection",
+ "leaseContainerName": "leases",
+ "connection": "CosmosDBConnection",
"databaseName": "ToDoItems",
- "collectionName": "Items",
- "leaseCollectionPrefix": "materialized"
+ "containerName": "Items",
+ "leaseContainerPrefix": "materialized"
} ```
cosmos-db Troubleshoot Changefeed Functions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cosmos-db/nosql/troubleshoot-changefeed-functions.md
Previously updated : 01/03/2023 Last updated : 04/07/2023
The error text itself tells you which Azure Cosmos DB database and container the
To resolve this issue:
-1. Verify the `ConnectionStringSetting` attribute and that it references a setting that exists in your Azure function app.
+1. Verify the `Connection` attribute and that it references a setting that exists in your Azure function app.
The value on this attribute shouldn't be the connection string itself, but the name of the configuration setting.
-1. Verify that the `databaseName` and `collectionName` values exist in your Azure Cosmos DB account.
+1. Verify that the `databaseName` and `containerName` values exist in your Azure Cosmos DB account.
If you're using automatic value replacement (using `%settingName%` patterns), make sure that the name of the setting exists in your Azure function app.
-1. If you don't specify a `LeaseCollectionName/leaseCollectionName` value, the default is `leases`. Verify that such a container exists.
+1. If you don't specify a `LeaseContainerName/leaseContainerName` value, the default is `leases`. Verify that such a container exists.
- Optionally, you can set the `CreateLeaseCollectionIfNotExists` attribute in your trigger to `true` to automatically create it.
+ Optionally, you can set the `CreateLeaseContainerIfNotExists` attribute in your trigger to `true` to automatically create it.
1. Verify your [Azure Cosmos DB account's firewall configuration](../how-to-configure-firewall.md) to ensure that it's not blocking the Azure function.
This scenario can have multiple causes. Consider trying any or all of the follow
* The speed at which your trigger receives new changes is dictated by the speed at which you're processing them. Verify the function's [execution time, or duration](../../azure-functions/analyze-telemetry-data.md). If your function is slow, that will increase the time it takes for the trigger to get new changes. If you see a recent increase in duration, a recent code change might be affecting it. If the speed at which you're receiving operations on your Azure Cosmos DB container is faster than the speed of your trigger, it will keep lagging behind. You might want to investigate the function's code to determine the most time-consuming operation and how to optimize it.
+* You can use [Debug logs](how-to-configure-cosmos-db-trigger.md#enabling-trigger-specific-logs) to check the Diagnostics and verify if there are networking delays.
+ ### Some changes are repeated in my trigger The concept of a *change* is an operation on a document. The most common scenarios where events for the same document are received are:
The concept of a *change* is an operation on a document. The most common scenari
You might find that some of the changes that occurred in your Azure Cosmos DB container aren't being picked up by the Azure function. Or some changes are missing at the destination when you're copying them. If so, try the solutions in this section.
+* Make sure you have [logs](how-to-configure-cosmos-db-trigger.md#enabling-trigger-specific-logs) enabled. Verify no errors are happening during processing.
+ * When your Azure function receives the changes, it often processes them and could, optionally, send the result to another destination. When you're investigating missing changes, make sure that you measure which changes are being received at the ingestion point (that is, when the Azure function starts), not at the destination. * If some changes are missing on the destination, this could mean that some error is happening during the Azure function execution after the changes were received.
cost-management-billing Direct Ea Administration https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cost-management-billing/manage/direct-ea-administration.md
New subscriptions can take up to 24 hours to appear in the subscriptions list. A
You can also create subscriptions by navigating to the Azure Subscriptions page and selecting **+ Add**.
+### Create subscription in other tenant and view transfer requests
+
+A user with the following permission can create subscriptions in another directory if they're allowed or exempted with subscription policy. For more information, see [Setting subscription policy](manage-azure-subscription-policy.md#setting-subscription-policy).
+
+- Account owner
+
+When you try to create a subscription for someone in a directory outside of the current directory (such as a customer's tenant), a _subscription creation request_ is created.
++
+When the request is created, the subscription owner (the customer) is sent an email letting them know that they need to accept subscription ownership. The email contains a link used to accept ownership in the Azure portal. The customer must accept the request within seven days. If not accepted within seven days, the request expires. The person that created the request can also manually send their customer the ownership URL to accept the subscription.
+
+After the request is created, it's visible in the Azure portal at **Subscriptions** > **View Requests** by the following people:
+
+- The tenant global administrator of the source tenant where the subscription provisioning request is made.
+- The user who made the subscription creation request for the subscription being provisioned in the other tenant.
+- The user who made the request to provision the subscription in a different tenant than where they make the [Subscription ΓÇô Alias REST API](/rest/api/subscription/) call instead of the Azure portal.
+
+The subscription owner in the request who resides in the target tenant doesn't see this subscription creation request on the View requests page. Instead, they receive an email with the link to accept ownership of the subscription in the target tenant.
++
+Anyone with access to view the request can view its details. In the request details, the **Accept ownership URL** is visible. You can copy it to manually share it with the subscription owner in the target tenant for subscription ownership acceptance.
++ ## Cancel a subscription Only account owners can cancel their own subscriptions.
cost-management-billing Programmatically Create Subscription Enterprise Agreement https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cost-management-billing/manage/programmatically-create-subscription-enterprise-agreement.md
Previously updated : 03/27/2023 Last updated : 04/07/2023
You get the subscriptionId as part of the response from the command.
+## Create subscriptions in a different enrollment
+
+Using the subscription [Alias](/rest/api/subscription/2021-10-01/alias/create) REST API, you can use the `subscriptionTenantId` parameter in the request body. Your SPN must get the token from the home tenant to create the subscription. After you create the SPN, you get the token from `subscriptionTenantId` and accept the transfer using the [Accept Ownership](/rest/api/subscription/2021-10-01/subscription/accept-ownership) API.
+
+For more information about creating EA subscriptions in another tenant, see [Create subscription in other tenant and view transfer requests](direct-ea-administration.md#create-subscription-in-other-tenant-and-view-transfer-requests).
+ ## Use ARM template or Bicep The previous section showed how to create a subscription with PowerShell, CLI, or REST API. If you need to automate creating subscriptions, consider using an Azure Resource Manager template (ARM template) or [Bicep file](../../azure-resource-manager/bicep/overview.md).
resource subToMG 'Microsoft.Management/managementGroups/subscriptions@2020-05-01
- Only Azure Enterprise subscriptions are created using the API. - There's a limit of 5000 subscriptions per enrollment account. After that, more subscriptions for the account can only be created in the Azure portal. To create more subscriptions through the API, create another enrollment account. Canceled, deleted, and transferred subscriptions count toward the 5000 limit. - Users who aren't Account Owners, but were added to an enrollment account via Azure RBAC, can't create subscriptions in the Azure portal.-- You can't select the tenant for the subscription to be created in. The subscription is always created in the home tenant of the Account Owner. To move the subscription to a different tenant, see [change subscription tenant](../../active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md).- ## Next steps
data-factory Tutorial Pipeline Failure Error Handling https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/data-factory/tutorial-pipeline-failure-error-handling.md
In some cases, you may want to invoke a shared error handling or logging step, i
```json @or(equals(activity('ActivityFailed').Status, 'Failed'), equals(activity('ActivitySucceeded').Status, 'Failed')) ```
-* Note: you need concatenated or if you've more than two dependency activities, for instance,
+* Note: you need concatenated or if you have more than two dependency activities, for instance,
```json @or(or(equals(activity('ActivityFailed').Status, 'Failed'), equals(activity('ActivitySucceeded1').Status, 'Failed')),equals(activity('ActivitySucceeded1').Status, 'Failed')) ```
The pattern is a combination of two: conditional and + error handling. The pipel
:::image type="content" source="media/tutorial-pipeline-failure-error-handling/conditional-complex-1.png" alt-text="Screenshot showcasing pipeline proceeds to next step if any of the activities pass, or else runs error handling code.":::
+## Common patterns
### Try-Catch-Proceed
-The pattern is equivalent to try catch block in coding. It states that if either the activity or the error handling code succeeds, the pipeline should proceed. We've simplified and streamlined the implementation for our customers. Try catch block doesn't need an if block.
+The pattern is equivalent to try catch block in coding. An activity might fail in a pipeline. When it fails, customer needs to run an error handling job to deal with it. However, the single activity failure shouldn't block next activities in the pipeline. For instance, I attempt to run a copy job, moving files into storage. However it might fail half way through. And in that case, I want to delete the partially copied, unreliable files from the storage account (my error handling step). But I'm OK to proceed with other activities afterwards.
+
+To set up the pattern:
* Add first activity * Add error handling to the UponFailure path * Add second activity, but don't connect to the first activity * Connect both UponFailure and UponSkip paths from the error handling activity to the second activity +
+Error Handling job runs only when First Activity fails. Next Activity will run regardless if First Activity succeeds or not.
+
+### Generic error handling
+Commonly, we have multiple activities running sequentially in the pipeline. If any fails, I need to run an error handling job to clear the state, and/or log the error. For instance, I have sequential copy activities in the pipeline. If any of these fails, I need to run a script job to log the pipeline failure.
+
+To set up the pattern:
+
+* Build sequential data processing pipeline
+* Add generic error handling step to the end of the pipeline
+* Connect both UponFailure and UponSkip paths from the last activity to the error handling activity
++
+The last step, Generic Error Handling, will only run if any of the previous activities fails. It will not run if they all succeed.
## Next steps
defender-for-cloud Upcoming Changes https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/defender-for-cloud/upcoming-changes.md
If you're looking for the latest release notes, you'll find them in the [What's
| [Deprecation and improvement of selected alerts for Windows and Linux Servers](#deprecation-and-improvement-of-selected-alerts-for-windows-and-linux-servers) | April 2023 | | [Deprecation of App Service language monitoring policies](#deprecation-of-app-service-language-monitoring-policies) | April 2023 | | [Deprecation of legacy compliance standards across cloud environments](#deprecation-of-legacy-compliance-standards-across-cloud-environments) | April 2023 |
-| [Multiple changes to identity recommendations](#multiple-changes-to-identity-recommendations) | April 2023 |
+| [Multiple changes to identity recommendations](#multiple-changes-to-identity-recommendations) | May 2023 |
| [New Azure Active Directory authentication-related recommendations for Azure Data Services](#new-azure-active-directory-authentication-related-recommendations-for-azure-data-services) | April 2023 | | [DevOps Resource Deduplication for Defender for DevOps](#devops-resource-deduplication-for-defender-for-devops) | June 2023 |
defender-for-iot Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/defender-for-iot/device-builders/overview.md
Microsoft Defender for IoT provides lightweight security agents so that you can
- **Security posture management**: Monitor the security posture of your IoT devices. Defender for IoT provides security posture recommendations based on the CIS benchmark, along with device-specific recommendations. Get visibility into operating system security, including OS configuration, firewall settings, and permissions. - **Endpoint threat detection**: Detect threats like botnets, brute force attempts, crypto miners, hardware connections, and suspicious network activity using the Microsoft TI database.-- **Device vulnerabilities management**: Monitor a full list of all your devices vulnerabilities based on a real-time dynamic SBoM and your operating system.-- **Microsoft Sentinel integration**: Use Microsoft Sentinel to investigate and manage your devices security, create custom dashboards and automatic response playbooks.
+- **Device vulnerabilities management**: Monitor a full list of device vulnerabilities based on a real-time dynamic SBoM and your operating system.
+- **Microsoft Sentinel integration**: Use Microsoft Sentinel to investigate and manage your device security, create custom dashboards and automatic response playbooks.
- **Raw events investigation**: Investigate all the raw events sent from your devices in your Log Analytics workspace. ## Defender for IoT micro agent
deployment-environments How To Configure Catalog https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/deployment-environments/how-to-configure-catalog.md
Next, create a personal access token. Depending on the type of repository you us
### Store the personal access token as a key vault secret
-To store the personal access token that you generated as a [key vault secret](../key-vault/secrets/about-secrets.md) and copy the secret identifier:
+Store the personal access token that you generated as a [key vault secret](../key-vault/secrets/about-secrets.md) and copy the secret identifier:
1. Create a [key vault](../key-vault/general/quick-create-portal.md#create-a-vault). 1. Add the personal access token as a [secret to the key vault](../key-vault/secrets/quick-create-portal.md#add-a-secret-to-key-vault).
To store the personal access token that you generated as a [key vault secret](..
1. In the [Azure portal](https://portal.azure.com/), go to your dev center. 1. Ensure that the [identity](./how-to-configure-managed-identity.md) that's attached to the dev center has [access to the key vault secret](./how-to-configure-managed-identity.md#grant-the-managed-identity-access-to-the-key-vault-secret) where your personal access token is stored.
-1. On the left menu under **Environment configuration**, select **Catalogs**, and then select **Add**.
-1. On **Add catalog**, enter the following information, and then select **Add**:
+1. In the left menu under **Environment configuration**, select **Catalogs**, and then select **Add**.
+1. In **Add catalog**, enter the following information, and then select **Add**:
| Field | Value | | -- | -- | | **Name** | Enter a name for the catalog. | | **Git clone URI** | Enter or paste the [clone URL](#get-the-clone-url-for-your-repository) for either your GitHub repository or your Azure DevOps repository.<br />*Sample catalog example:* `https://github.com/Azure/deployment-environments.git` | | **Branch** | Enter the repository branch to connect to.<br />*Sample catalog example:* `main`|
- | **Folder path** | Enter the folder path relative to the clone URI that contains subfolders that hold your catalog items. <br /> This folder path should be the path to the folder that contains the subfolders that have the catalog item manifests, and not the path to the folder that has the catalog item manifest itself.<br />*Sample catalog example:* `/Environments`<br /> The folder path can begin with or without a forward slash (`/`).|
+ | **Folder path** | Enter the folder path relative to the clone URI that contains subfolders that hold your catalog items. <br /> The folder path is for the folder with subfolders containing catalog item manifests, not for the folder with the catalog item manifest itself. The following image shows the sample catalog folder structure.<br />*Sample catalog example:* `/Environments`<br /> :::image type="content" source="media/how-to-configure-catalog/github-folders.png" alt-text="Screenshot showing Environments sample folder in GitHub."::: The folder path can begin with or without a forward slash (`/`).|
| **Secret identifier**| Enter the [secret identifier](#create-a-personal-access-token) that contains your personal access token for the repository.<br /> When you copy a secret identifier, the connection string includes a version identifier at the end, like in this example: `https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat/9376b432b72441a1b9e795695708ea5a`.<br />Removing the version identifier ensures that Deployment Environments fetches the latest version of the secret from the key vault. If your personal access token expires, only the key vault needs to be updated. <br />*Example secret identifier:* `https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat`| :::image type="content" source="media/how-to-configure-catalog/add-catalog-form-inline.png" alt-text="Screenshot that shows how to add a catalog to a dev center." lightbox="media/how-to-configure-catalog/add-catalog-form-expanded.png":::
-1. On **Catalogs** for the dev center, verify that your catalog appears. If the connection is successful, **Status** is **Connected**.
+1. In **Catalogs** for the dev center, verify that your catalog appears. If the connection is successful, **Status** is **Connected**.
## Update a catalog
deployment-environments Quickstart Create And Configure Devcenter https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/deployment-environments/quickstart-create-and-configure-devcenter.md
If you don't have an existing key vault, use the following steps to create one:
1. In the Search box, enter *Key Vault*. 1. From the results list, select **Key Vault**. 1. On the Key Vault page, select **Create**.
-1. On the Create key vault page provide the following information:
+1. On the Create key vault page, provide the following information:
|Name |Value | |-|--|
You also need the path to the secret you created in the key vault.
:::image type="content" source="media/quickstart-create-and-configure-devcenter/catalogs-page.png" alt-text="Screenshot that shows the Catalogs pane.":::
-1. In the **Add catalog** pane, enter the following information, and then select **Add**.
+1. In **Add catalog**, enter the following information, and then select **Add**:
- | Name | Value |
+ | Field | Value |
| -- | -- | | **Name** | Enter a name for the catalog. |
- | **Git clone URI** | Enter or paste the clone URL for either your GitHub repository or your Azure DevOps repository.<br/>*Sample Catalog Example:* https://github.com/Azure/deployment-environments.git |
- | **Branch** | Enter the repository branch to connect to.<br/>*Sample Catalog Example:* main|
- | **Folder path** | Enter the folder path relative to the clone URI that contains subfolders with your catalog items. </br>This folder path should be the path to the folder that contains the subfolders with the catalog item manifests, and not the path to the folder with the catalog item manifest itself.<br/>*Sample Catalog Example:* /Environments </br> The folder path can begin with or without a '/'.|
- | **Secret identifier**| Enter the secret identifier that contains your personal access token for the repository. When you copy a Secret Identifier, the connection string includes a version identifier at the end, like this: https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat/9376b432b72441a1b9e795695708ea5a. </br>Removing the version identifier ensures that Deployment Environments fetches the latest version of the secret from the key vault. If your PAT expires, only the key vault needs to be updated. </br> *Example secret identifier: https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat*|
+ | **Git clone URI** | Enter or paste the clone URL for either your GitHub repository or your Azure DevOps repository.<br />*Sample catalog example:* `https://github.com/Azure/deployment-environments.git` |
+ | **Branch** | Enter the repository branch to connect to.<br />*Sample catalog example:* `main`|
+ | **Folder path** | Enter the folder path relative to the clone URI that contains subfolders that hold your catalog items. <br /> The folder path is for the folder with subfolders containing catalog item manifests, not for the folder with the catalog item manifest itself. The following image shows the sample catalog folder structure.<br />*Sample catalog example:* `/Environments`<br /> :::image type="content" source="media/how-to-configure-catalog/github-folders.png" alt-text="Screenshot showing Environments sample folder in GitHub."::: The folder path can begin with or without a forward slash (`/`).|
+ | **Secret identifier**| Enter the [secret identifier](#create-a-personal-access-token) that contains your personal access token for the repository.<br /> When you copy a secret identifier, the connection string includes a version identifier at the end, like in this example: `https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat/9376b432b72441a1b9e795695708ea5a`.<br />Removing the version identifier ensures that Deployment Environments fetches the latest version of the secret from the key vault. If your personal access token expires, only the key vault needs to be updated. <br />*Example secret identifier:* `https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat`|
:::image type="content" source="media/how-to-configure-catalog/add-catalog-form-inline.png" alt-text="Screenshot that shows how to add a catalog to a dev center." lightbox="media/how-to-configure-catalog/add-catalog-form-expanded.png":::
-1. Confirm that the catalog is successfully added by checking your Azure portal notifications.
+1. In **Catalogs** for the dev center, verify that your catalog appears. If the connection is successful, **Status** is **Connected**.
## Create an environment type
healthcare-apis Device Messages Through Iot Hub https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/healthcare-apis/iot/device-messages-through-iot-hub.md
-+ Last updated 04/07/2023 # Tutorial: Receive device messages through Azure IoT Hub
-> [!NOTE]
+> [!NOTE]
> [Fast Healthcare Interoperability Resources (FHIR&#174;)](https://www.hl7.org/fhir/) is an open healthcare specification. For enhanced workflows and ease of use, you can use the MedTech service to receive messages from devices you create and manage through an IoT hub in [Azure IoT Hub](../../iot-hub/iot-concepts-and-iot-hub.md). This tutorial uses an Azure Resource Manager template (ARM template) and a **Deploy to Azure** button to deploy a MedTech service. The template deploys an IoT hub to create and manage devices, and then routes device messages to an event hub in Azure Event Hubs for the MedTech service to pick up and process.
For enhanced workflows and ease of use, you can use the MedTech service to recei
:::image type="content" source="media\device-messages-through-iot-hub\data-flow-diagram.png" border="false" alt-text="Diagram of the IoT device message flow through an IoT hub and event hub, and then into the MedTech service." lightbox="media\device-messages-through-iot-hub\data-flow-diagram.png"::: > [!TIP]
-> To learn how the MedTech service transforms and persists device message data into the FHIR service as FHIR Observations, see [Overview of the MedTech service device message processing stages](overview-of-device-message-processing-stages.md).
-
+> To learn how the MedTech service transforms and persists device message data into the FHIR service as FHIR Observations, see [Overview of the MedTech service device message processing stages](overview-of-device-message-processing-stages.md).
In this tutorial, you learn how to:
When you have these prerequisites, you're ready to configure the ARM template by
## Review the ARM template - Optional
-The ARM template used to deploy the resources in this tutorial is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors-with-iothub/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors-with-iothub).
+The ARM template used to deploy the resources in this tutorial is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors-with-iothub/) by using the _azuredeploy.json_ file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors-with-iothub).
## Use the Deploy to Azure button
To begin deployment in the Azure portal, select the **Deploy to Azure** button:
- **Region**: The Azure region of the resource group that's used for the deployment. **Region** autofills by using the resource group region.
- - **Basename**: A value that's appended to the name of the Azure resources and services that are deployed. The examples in this tutorial use the basename *azuredocsdemo*. You can choose your own basename value.
+ - **Basename**: A value that's appended to the name of the Azure resources and services that are deployed. The examples in this tutorial use the basename _azuredocsdemo_. You can choose your own basename value.
- **Location**: A supported Azure region for Azure Health Data Services (the value can be the same as or different from the region your resource group is in). For a list of Azure regions where Health Data Services is available, see [Products available by regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=health-data-services). - **Fhir Contributor Principle Id** (optional): An Azure Active Directory (Azure AD) user object ID to provide read/write permissions in the FHIR service.
-
- You can use this account to give access to the FHIR service to view the device messages that are generated in this tutorial. We recommend that you use your own Azure AD user object ID, so you can access the messages in the FHIR service. If you choose not to use the **Fhir Contributor Principle Id** option, clear the text box.
-
- To learn how to get an Azure AD user object ID, see [Find the user object ID](/partner-center/find-ids-and-domain-names#find-the-user-object-id). The user object ID that's used in this tutorial is only an example. If you use this option, use your own user object ID or the object ID of another person who you want to be able to access the FHIR service.
+
+ You can use this account to give access to the FHIR service to view the device messages that are generated in this tutorial. We recommend that you use your own Azure AD user object ID, so you can access the messages in the FHIR service. If you choose not to use the **Fhir Contributor Principle Id** option, clear the text box.
+
+ To learn how to get an Azure AD user object ID, see [Find the user object ID](/partner-center/find-ids-and-domain-names#find-the-user-object-id). The user object ID that's used in this tutorial is only an example. If you use this option, use your own user object ID or the object ID of another person who you want to be able to access the FHIR service.
- **Device mapping**: Don't change the default values for this tutorial. The mappings are set in the template to send a device message to your IoT hub later in the tutorial. - **Destination mapping**: Don't change the default values for this tutorial. The mappings are set in the template to send a device message to your IoT hub later in the tutorial.
-
+ :::image type="content" source="media\device-messages-through-iot-hub\deploy-template-options.png" alt-text="Screenshot that shows deployment options for the MedTech service for Health Data Services in the Azure portal." lightbox="media\device-messages-through-iot-hub\deploy-template-options.png"::: 2. To validate your configuration, select **Review + create**.
To begin deployment in the Azure portal, select the **Deploy to Azure** button:
When deployment is completed, the following resources and access roles are created in the template deployment: -- An Azure Event Hubs namespace and a device message event hub. In this deployment, the event hub is named *devicedata*.
+- An Azure Event Hubs namespace and a device message event hub. In this deployment, the event hub is named _devicedata_.
- - An event hub consumer group. In this deployment, the consumer group is named *$Default*.
+ - An event hub consumer group. In this deployment, the consumer group is named _$Default_.
- - An Azure Event Hubs Data Sender role. In this deployment, the sender role is named *devicedatasender* and can be used to provide access to the device event hub using a shared access signature (SAS). To learn more about authorizing access using a SAS, see [Authorizing access to Event Hubs resources using Shared Access Signatures](../../event-hubs/authorize-access-shared-access-signature.md). The Azure Event Hubs Data Sender role isn't used in this tutorial.
+ - An Azure Event Hubs Data Sender role. In this deployment, the sender role is named _devicedatasender_ and can be used to provide access to the device event hub using a shared access signature (SAS). To learn more about authorizing access using a SAS, see [Authorizing access to Event Hubs resources using Shared Access Signatures](../../event-hubs/authorize-access-shared-access-signature.md). The Azure Event Hubs Data Sender role isn't used in this tutorial.
- An Azure IoT Hub with [message routing](../../iot-hub/iot-hub-devguide-messages-d2c.md) configured to send device messages to the device message event hub. -- A [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) that provides send access from the IoT hub to the device message event hub. The managed identity has the Azure Event Hubs Data Sender role in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the device message event hub.
+- A [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) that provides send access from the IoT hub to the device message event hub. The managed identity has the Azure Event Hubs Data Sender role in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the device message event hub.
- A Health Data Services workspace.
When deployment is completed, the following resources and access roles are creat
- For the device message event hub, the Azure Events Hubs Data Receiver role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the device message event hub. - For the FHIR service, the FHIR Data Writer role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the FHIR service.
-
-- Conforming and valid MedTech service [device](how-to-configure-device-mappings.md) and [FHIR destination mappings](how-to-configure-fhir-mappings.md).+
+- Conforming and valid MedTech service [device](overview-of-device-mapping.md) and [FHIR destination mappings](how-to-configure-fhir-mappings.md). **Resolution type** is set to **Create**.
> [!IMPORTANT] > In this tutorial, the ARM template configures the MedTech service to operate in **Create** mode. A Patient resource and a Device resource are created for each device that sends data to your FHIR service.
You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
:::image type="content" source="media\device-messages-through-iot-hub\select-iot-hub.png" alt-text="Screenshot of Visual Studio Code with the Azure IoT Hub extension with the deployed IoT hub selected." lightbox="media\device-messages-through-iot-hub\select-iot-hub.png"::: 3. Select the Azure subscription where your IoT hub was provisioned.
-
-4. Select your IoT hub. The name of your IoT hub is the *basename* you provided when you provisioned the resources prefixed with **ih-**. An example hub name is *ih-azuredocsdemo*.
-5. In Explorer, in **Azure IoT Hub**, select **…** and choose **Create Device**. An example device name is *iot-001*.
+4. Select your IoT hub. The name of your IoT hub is the _basename_ you provided when you provisioned the resources prefixed with **ih-**. An example hub name is _ih-azuredocsdemo_.
+
+5. In Explorer, in **Azure IoT Hub**, select **…** and choose **Create Device**. An example device name is _iot-001_.
:::image type="content" source="media\device-messages-through-iot-hub\create-device.png" alt-text="Screenshot that shows Visual Studio Code with the Azure IoT Hub extension with Create device selected." lightbox="media\device-messages-through-iot-hub\create-device.png"::: 6. To send a test message from the device to your IoT hub, right-click the device and select **Send D2C Message to IoT Hub**. > [!NOTE]
- > In this device-to-cloud (D2C) example, *cloud* is the IoT hub in the Azure IoT Hub that receives the device message. Azure IoT Hub supports two-way communications. To set up a cloud-to-device (C2D) scenario, select **Send C2D Message to Device Cloud**.
+ > In this device-to-cloud (D2C) example, _cloud_ is the IoT hub in the Azure IoT Hub that receives the device message. Azure IoT Hub supports two-way communications. To set up a cloud-to-device (C2D) scenario, select **Send C2D Message to Device Cloud**.
:::image type="content" source="media\device-messages-through-iot-hub\select-device-to-cloud-message.png" alt-text="Screenshot that shows Visual Studio Code with the Azure IoT Hub extension and the Send D2C Message to IoT Hub option selected." lightbox="media\device-messages-through-iot-hub\select-device-to-cloud-message.png":::
You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
After you select **Send**, it might take up to five minutes for the FHIR resources to be available in the FHIR service. > [!IMPORTANT]
- > To avoid device spoofing in D2C messages, Azure IoT Hub enriches all messages with additional properties. For more information, see [Anti-spoofing properties](../../iot-hub/iot-hub-devguide-messages-construct.md#anti-spoofing-properties) and [How to use IotJsonPathContentTemplate mappings](how-to-use-iot-jsonpath-content-mappings.md).
+ > To avoid device spoofing in device-to-cloud (D2C) messages, Azure IoT Hub enriches all device messages with additional properties before sending it to the MedTech service device event hub. For example: **Properties**: `iothub-creation-time-utc` and **SystemProperties**: `iothub-connection-device-id`. For more information, see [Anti-spoofing properties](../../iot-hub/iot-hub-devguide-messages-construct.md#anti-spoofing-properties) and [How to use IotJsonPathContent mappings](how-to-use-iot-jsonpath-content-mappings.md).
+ >
+ > You do not want to send this example device message to your IoT hub as the enrichments will be duplicated by the IoT hub and cause an error with your MedTech service. This is only an example of how your device messages are enriched by the IoT hub.
+ >
+ > Example:
+ >
+ > :::image type="content" source="media\device-messages-through-iot-hub\iot-hub-enriched-device-message.png" alt-text="Screenshot of an Azure IoT Hub enriched device message." lightbox="media\device-messages-through-iot-hub\iot-hub-enriched-device-message.png":::
+ >
+ > `patientIdExpression` is only required for MedTech services in the **Create** mode, however, if **Lookup** is being used, a Device resource with a matching Device Identifier must exist in the FHIR service. This example assumes your MedTech service is in a **Create** mode. The **Resolution type** for this tutorial set to **Create**. For more information on the **Destination properties**: **Create** and **Lookup**, see [Configure Destination properties](deploy-new-config.md#destination-properties).
## Review metrics from the test message
In this tutorial, you deployed an ARM template in the Azure portal, connected to
To learn about other methods for deploying the MedTech service, see
-> [!div class="nextstepaction"]
+> [!div class="nextstepaction"]
> [Choose a deployment method for the MedTech service](deploy-new-choose.md) FHIR&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
logic-apps Create Single Tenant Workflows Visual Studio Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md
Install the following tools and versions for your specific operating system: Win
Currently, you can have both Consumption (multi-tenant) and Standard (single-tenant) extensions installed at the same time. The development experiences differ from each other in some ways, but your Azure subscription can include both Standard and Consumption logic app types. Visual Studio Code shows all the deployed logic apps in your Azure subscription, but organizes your apps under each extension, **Azure Logic Apps (Consumption)** and **Azure Logic Apps (Standard)**.
-* To use the [Inline Code Operations action](../logic-apps/logic-apps-add-run-inline-code.md) that runs JavaScript, install [Node.js versions 12.x.x or 14.x.x](https://nodejs.org/en/download/releases/).
+* To use the [Inline Code Operations action](../logic-apps/logic-apps-add-run-inline-code.md) that runs JavaScript, install [Node.js version 16.x.x unless a newer version is already installed](https://nodejs.org/en/download/releases/).
> [!TIP] > For Windows, download the MSI version. If you use the ZIP version instead, you have to
Install the following tools and versions for your specific operating system: Win
![Screenshot that shows Visual Studio Code Activity Bar and selected Azure icon.](./media/create-single-tenant-workflows-visual-studio-code/visual-studio-code-azure-icon.png)
-1. In the Azure pane, under **Azure: Logic Apps (Standard)**, select **Sign in to Azure**. When the Visual Studio Code authentication page appears, sign in with your Azure account.
+1. In the Azure pane, under **Logic Apps (Standard)**, select **Sign in to Azure**. When the Visual Studio Code authentication page appears, sign in with your Azure account.
![Screenshot that shows Azure pane and selected link for Azure sign in.](./media/create-single-tenant-workflows-visual-studio-code/sign-in-azure-subscription.png)
Before you can create your logic app, create a local project so that you can man
1. In Visual Studio Code, close all open folders.
-1. In the Azure pane, next to **Azure: Logic Apps (Standard)**, select **Create New Project** (icon that shows a folder and lightning bolt).
+1. In the Azure pane, next to **Logic Apps (Standard)**, select **Create New Project** (icon that shows a folder and lightning bolt).
![Screenshot that shows Azure pane toolbar with "Create New Project" selected.](./media/create-single-tenant-workflows-visual-studio-code/create-new-project-folder.png)
Before you can create your logic app, create a local project so that you can man
![Screenshot that shows the workflow templates list with "Stateful Workflow" selected.](./media/create-single-tenant-workflows-visual-studio-code/select-stateful-stateless-workflow.png)
-1. Provide a name for your workflow and press Enter. This example uses `Fabrikam-Stateful-Workflow` as the name.
+1. Provide a name for your workflow and press Enter. This example uses **Fabrikam-Stateful-Workflow** as the name.
![Screenshot that shows the "Create new Stateful Workflow (3/4)" box and "Fabrikam-Stateful-Workflow" as the workflow name.](./media/create-single-tenant-workflows-visual-studio-code/name-your-workflow.png)
The authoring capability is currently available only in Visual Studio Code, but
![Screenshot that shows Explorer pane with resource groups list and "Create new resource group" selected.](./media/create-single-tenant-workflows-visual-studio-code/create-select-resource-group.png)
-1. Provide a name for the resource group, and press Enter. This example uses `Fabrikam-Workflows-RG`.
+1. Provide a name for the resource group, and press Enter. This example uses **Fabrikam-Workflows-RG**.
![Screenshot that shows Explorer pane and resource group name box.](./media/create-single-tenant-workflows-visual-studio-code/enter-name-for-resource-group.png)
The workflow in this example uses this trigger and these actions:
1. Next to the designer, in the **Add a trigger** pane, under the **Choose an operation** search box, make sure that **Built-in** is selected so that you can select a trigger that runs natively.
-1. In the **Choose an operation** search box, enter `when a http request`, and select the built-in Request trigger that's named **When an HTTP request is received**.
+1. In the **Choose an operation** search box, enter **when a http request**, and select the built-in Request trigger that's named **When an HTTP request is received**.
![Screenshot that shows the workflow designer and **Add a trigger** pane with "When an HTTP request is received" trigger selected.](./media/create-single-tenant-workflows-visual-studio-code/add-request-trigger.png)
The workflow in this example uses this trigger and these actions:
> [!TIP] > To prevent future prompts, select **Don't ask again for this extension**.
- After Visual Studio Code creates your connection, some connectors show the message that `The connection will be valid for {n} days only`. This time limit applies only to the duration while you author your logic app in Visual Studio Code. After deployment, this limit no longer applies because your logic app can authenticate at runtime by using its automatically enabled [system-assigned managed identity](../logic-apps/create-managed-service-identity.md). This managed identity differs from the authentication credentials or connection string that you use when you create a connection. If you disable this system-assigned managed identity, connections won't work at runtime.
+ After Visual Studio Code creates your connection, some connectors show the message that **The connection will be valid for {n} days only**. This time limit applies only to the duration while you author your logic app in Visual Studio Code. After deployment, this limit no longer applies because your logic app can authenticate at runtime by using its automatically enabled [system-assigned managed identity](../logic-apps/create-managed-service-identity.md). This managed identity differs from the authentication credentials or connection string that you use when you create a connection. If you disable this system-assigned managed identity, connections won't work at runtime.
1. On the designer, if the **Send an email** action doesn't appear selected, select that action.
The workflow in this example uses this trigger and these actions:
| Property | Required | Value | Description | |-|-|-|-|
- | **To** | Yes | <*your-email-address*> | The email recipient, which can be your email address for test purposes. This example uses the fictitious email, `sophiaowen@fabrikam.com`. |
- | **Subject** | Yes | `An email from your example workflow` | The email subject |
- | **Body** | Yes | `Hello from your example workflow!` | The email body content |
+ | **To** | Yes | <*your-email-address*> | The email recipient, which can be your email address for test purposes. This example uses the fictitious email, **sophiaowen@fabrikam.com**. |
+ | **Subject** | Yes | **An email from your example workflow** | The email subject |
+ | **Body** | Yes | **Hello from your example workflow!** | The email body content |
|||| > [!NOTE]
To test your logic app, follow these steps to start a debugging session, and fin
1. On the **Create New** pane, under **Building Blocks**, select **Request**.
- 1. In the **Save Request** window, under **Request name**, provide a name for the request, for example, `Test workflow trigger`.
+ 1. In the **Save Request** window, under **Request name**, provide a name for the request, for example, **Test workflow trigger**.
1. Under **Select a collection or folder to save to**, select **Create Collection**.
- 1. Under **All Collections**, provide a name for the collection to create for organizing your requests, press Enter, and select **Save to <*collection-name*>**. This example uses `Logic Apps requests` as the collection name.
+ 1. Under **All Collections**, provide a name for the collection to create for organizing your requests, press Enter, and select **Save to <*collection-name*>**. This example uses **Logic Apps requests** as the collection name.
In Postman, the request pane opens so that you can send a request to the callback URL for the Request trigger.
To test your logic app, follow these steps to start a debugging session, and fin
![Screenshot that shows each step in the workflow run and their status](./media/create-single-tenant-workflows-visual-studio-code/run-history-action-status.png) > [!NOTE]
- > If a run failed and a step in monitoring view shows the `400 Bad Request` error, this problem might result
+ > If a run failed and a step in monitoring view shows the **400 Bad Request** error, this problem might result
> from a longer trigger name or action name that causes the underlying Uniform Resource Identifier (URI) to exceed > the default character limit. For more information, see ["400 Bad Request"](#400-bad-request).
To return a response to the caller that sent a request to your logic app, you ca
The **Choose an operation** prompt appears on the designer, and the **Add an action** pane reopens so that you can select the next action.
-1. On the **Add an action** pane, under the **Choose an action** search box, make sure that **Built-in** is selected. In the search box, enter `response`, and select the **Response** action.
+1. On the **Add an action** pane, under the **Choose an action** search box, make sure that **Built-in** is selected. In the search box, enter **response**, and select the **Response** action.
![Screenshot that shows the workflow designer with the Response action selected.](./media/create-single-tenant-workflows-visual-studio-code/add-response-action.png)
To find the fully qualified domain names (FQDNs) for these connections, follow t
## Deploy to Azure
-From Visual Studio Code, you can directly publish your project to Azure, which deploys your logic app using the **Logic App (Standard)** resource type. You can publish your logic app as a new resource, which automatically creates any necessary resources, such as an [Azure Storage account, similar to function app requirements](../azure-functions/storage-considerations.md). Or, you can publish your logic app to a previously deployed **Logic App (Standard)** resource, which overwrites that logic app.
+From Visual Studio Code, you can directly publish your project to Azure to deploy your Standard logic app. You can publish your logic app as a new resource, which automatically creates any necessary resources, such as an [Azure Storage account, similar to function app requirements](../azure-functions/storage-considerations.md). Or, you can publish your logic app to a previously deployed Standard logic app resource, which overwrites that logic app.
-Deployment for the **Logic App (Standard)** resource type requires a hosting plan and pricing tier, which you select during deployment. For more information, review [Hosting plans and pricing tiers](logic-apps-pricing.md#standard-pricing).
+Deployment for the Standard logic app resource requires a hosting plan and pricing tier, which you select during deployment. For more information, review [Hosting plans and pricing tiers](logic-apps-pricing.md#standard-pricing).
<a name="publish-new-logic-app"></a>
-### Publish to a new Logic App (Standard) resource
+### Publish to a new Standard logic app resource
1. On the Visual Studio Code Activity Bar, select the Azure icon.
-1. On the **Azure: Logic Apps (Standard)** pane toolbar, select **Deploy to Logic App**.
+1. On the **Logic Apps (Standard)** pane toolbar, select **Deploy to Logic App**.
- ![Screenshot that shows the "Azure: Logic Apps (Standard)" pane and pane's toolbar with "Deploy to Logic App" selected.](./media/create-single-tenant-workflows-visual-studio-code/deploy-to-logic-app.png)
+ ![Screenshot that shows the pane "Logic Apps (Standard)" pane and pane's toolbar with "Deploy to Logic App" selected.](./media/create-single-tenant-workflows-visual-studio-code/deploy-to-logic-app.png)
1. If prompted, select the Azure subscription to use for your logic app deployment.
Deployment for the **Logic App (Standard)** resource type requires a hosting pla
This example continues with **Create new Logic App (Standard) in Azure Advanced**.
- ![Screenshot that shows the "Azure: Logic Apps (Standard)" pane with a list with "Create new Logic App (Standard) in Azure" selected.](./media/create-single-tenant-workflows-visual-studio-code/select-create-logic-app-options.png)
+ ![Screenshot that shows the "Logic Apps (Standard)" pane and a list with "Create new Logic App (Standard) in Azure" selected.](./media/create-single-tenant-workflows-visual-studio-code/select-create-logic-app-options.png)
-1. To create your new **Logic App (Standard)** resource, follow these steps:
+1. To create your new Standard logic app resource, follow these steps:
- 1. Provide a globally unique name for your new logic app, which is the name to use for the **Logic App (Standard)** resource. This example uses `Fabrikam-Workflows-App`.
+ 1. Provide a globally unique name for your new logic app, which is the name to use for the **Logic App (Standard)** resource. This example uses **Fabrikam-Workflows-App**.
- ![Screenshot that shows the "Azure: Logic Apps (Standard)" pane and a prompt to provide a name for the new logic app to create.](./media/create-single-tenant-workflows-visual-studio-code/enter-logic-app-name.png)
+ ![Screenshot that shows the "Logic Apps (Standard)" pane and a prompt to provide a name for the new logic app to create.](./media/create-single-tenant-workflows-visual-studio-code/enter-logic-app-name.png)
1. Select a hosting plan for your new logic app. Either create a name for your plan, or select an existing plan (Windows-based App Service plans only). This example selects **Create new App Service Plan**.
- ![Screenshot that shows the "Azure: Logic Apps (Standard)" pane and a prompt to "Create new App Service Plan" or select an existing App Service plan.](./media/create-single-tenant-workflows-visual-studio-code/create-app-service-plan.png)
+ ![Screenshot that shows the "Logic Apps (Standard)" pane and a prompt to "Create new App Service Plan" or select an existing App Service plan.](./media/create-single-tenant-workflows-visual-studio-code/create-app-service-plan.png)
1. Provide a name for your hosting plan, and then select a pricing tier for your selected plan.
Deployment for the **Logic App (Standard)** resource type requires a hosting pla
1. For stateful workflows, select **Create new storage account** or an existing storage account.
- ![Screenshot that shows the "Azure: Logic Apps (Standard)" pane and a prompt to create or select a storage account.](./media/create-single-tenant-workflows-visual-studio-code/create-storage-account.png)
+ ![Screenshot that shows the "Logic Apps (Standard)" pane and a prompt to create or select a storage account.](./media/create-single-tenant-workflows-visual-studio-code/create-storage-account.png)
1. If your logic app's creation and deployment settings support using [Application Insights](../azure-monitor/app/app-insights-overview.md), you can optionally enable diagnostics logging and tracing for your logic app. You can do so either when you deploy your logic app from Visual Studio Code or after deployment. You need to have an Application Insights instance, but you can create this resource either [in advance](../azure-monitor/app/create-workspace-resource.md), when you deploy your logic app, or after deployment.
Deployment for the **Logic App (Standard)** resource type requires a hosting pla
| Information | Logs that track the general activity in your logic app or workflow, for example: <p><p>- When a trigger, action, or run starts and ends. <br>- When your logic app starts or ends. | | Trace | Logs that contain the most detailed messages, for example, storage requests or dispatcher activity, plus all the messages that are related to workflow execution activity. | | Warning | Logs that highlight an abnormal state in your logic app but doesn't prevent its running. |
- |||
To set the severity level, at your project's root level, open the **host.json** file, and find the `logging` object. This object controls the log filtering for all the workflows in your logic app and follows the [ASP.NET Core layout for log type filtering](/aspnet/core/fundamentals/logging/?view=aspnetcore-2.1&preserve-view=true#log-filtering).
You can have multiple workflows in your logic app project. To add a blank workfl
1. On the Visual Studio Code Activity Bar, select the Azure icon.
-1. In the Azure pane, next to **Azure: Logic Apps (Standard)**, select **Create Workflow** (icon for Azure Logic Apps).
+1. In the Azure pane, next to **Logic Apps (Standard)**, select **Create Workflow** (Azure Logic Apps icon).
1. Select the workflow type that you want to add: **Stateful** or **Stateless**
When you're done, a new workflow folder appears in your project along with a **w
In Visual Studio Code, you can view all the deployed logic apps in your Azure subscription, whether they're Consumption or Standard logic app resources, and select tasks that help you manage those logic apps. However, to access both resource types, you need both the **Azure Logic Apps (Consumption)** and the **Azure Logic Apps (Standard)** extensions for Visual Studio Code.
-1. On the left toolbar, select the Azure icon. In the **Azure: Logic Apps (Standard)** pane, expand your subscription, which shows all the deployed logic apps for that subscription.
+1. On the left toolbar, select the Azure icon. In the **Logic Apps (Standard)** pane, expand your subscription, which shows all the deployed logic apps for that subscription.
1. Open the logic app that you want to manage. From the logic app's shortcut menu, select the task that you want to perform.
Stopping a logic app affects workflow instances in the following ways:
To stop a trigger from firing on unprocessed items since the last run, clear the trigger state before you restart the logic app: 1. In Visual Studio Code, on the left toolbar, select the Azure icon.
- 1. In the **Azure: Logic Apps (Standard)** pane, expand your subscription, which shows all the deployed logic apps for that subscription.
+ 1. In the **Logic Apps (Standard)** pane, expand your subscription, which shows all the deployed logic apps for that subscription.
1. Expand your logic app, and then expand the node that's named **Workflows**. 1. Open a workflow, and edit any part of that workflow's trigger. 1. Save your changes. This step resets the trigger's current state.
logic-apps Workflow Definition Language Functions Reference https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/logic-apps/workflow-definition-language-functions-reference.md
ms.suite: integration
Previously updated : 09/20/2022 Last updated : 04/07/2023 # Reference guide to workflow expression functions in Azure Logic Apps and Power Automate
And returns this result XML:
Check XML for nodes or values that match an XPath (XML Path Language) expression, and return the matching nodes or values. An XPath expression, or just "XPath", helps you navigate an XML document structure so that you can select nodes or compute values in the XML content.
+> [!NOTE]
+>
+> In Consumption and Standard logic apps, all function expressions use the [.NET XPath library](/dotnet/api/system.xml.xpath).
+> XPath expressions are compatible with the underlying .NET library and support only the expression that the underlying .NET library supports.
+ ``` xpath('<xml>', '<xpath>') ```
machine-learning Apache Spark Azure Ml Concepts https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/machine-learning/apache-spark-azure-ml-concepts.md
After the Managed (Automatic) Spark compute resource tear-down happens, submissi
> - the *Cold start* will need about ten to fifteen minutes. > - the *Warm start*, using same conda package, will need about one minute. > - the *Warm start*, with a different conda package, will also need about ten to fifteen minutes.
+> - If the package that you're installing is large or takes a long time to install, it might affect the Spark instance's startup time.
+> - Altering the PySpark, Python, Scala/Java, .NET, or Spark version is not supported.
## Attached Synapse Spark pool
payment-hsm Deployment Scenarios https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/payment-hsm/deployment-scenarios.md
This scenario caters to regional-level failure. The usual strategy is to complet
## Next steps -- Learn more about [Azure Payment HSM](overview.md)-- See the Azure Payment HSM [Solution design](solution-design.md)-- Find out how to [get started with Azure Payment HSM](getting-started.md)-- Learn how to [Create a payment HSM](create-payment-hsm.md)-- Read the [frequently asked questions](faq.yml)
+- [What is Azure Payment HSM?](overview.md)
+- [Azure Payment HSM solution design](solution-design.md)
+- [Azure Payment HSM traffic inspection](inspect-traffic.md)
+- [Get started with Azure Payment HSM](getting-started.md)
+- [Create a payment HSM](create-payment-hsm.md)
+- [Frequently asked questions](faq.yml)
payment-hsm Fastpathenabled https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/payment-hsm/fastpathenabled.md
Title: Azure Payment HSM "fastpathenabled" feature flag and tag description: The "fastpathenabled" feature flag and tag, as it relates to Azure Payment HSM and affiliated subscriptions and virtual networks --
-tags: azure-resource-manager
+ Last updated 03/25/2023-+
payment-hsm Inspect Traffic https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/payment-hsm/inspect-traffic.md
+
+ Title: Azure Payment HSM traffic inspection
+description: Guiance on how to bypass the UDR restriction and inspect traffic destined to an Azure Payment HSM.
+++++ Last updated : 04/06/2023++
+# Azure Payment HSM traffic inspection
+
+Azure Payment Hardware Security Module (Payment HSM or PHSM) is a [bare-metal service](overview.md) providing cryptographic key operations for real-time and critical payment transactions in the Azure cloud. For more information, see [What is Azure Payment HSM?](overview.md).
+
+When Payment HSM is deployed, it comes with a host network interface and a management network interface. There are several deployment scenarios:
+
+1. [With host and management ports in same VNet](create-payment-hsm.md?tabs=azure-cli)
+2. [With host and management ports in different VNets](create-different-vnet.md?tabs=azure-cli)
+3. [With host and management port with IP addresses in different VNets](create-different-ip-addresses.md?tabs=azure-cli)
+
+In all of the above scenarios, Payment HSM is a VNet-injected service in a delegated subnet: `hsmSubnet` and `managementHsmSubnet` must be delegated to `Microsoft.HardwareSecurityModules/dedicatedHSMs` service.
+
+> [!IMPORTANT]
+> The `FastPathEnabled` feature must be [registered and approved](register-payment-hsm-resource-providers.md?tabs=azure-cli#register-the-resource-providers-and-features) on all subscriptions that need access to Payment HSM. You must also enable the `fastpathenabled` tag on the VNet hosting the Payment HSM delegated subnet and on every peered VNet requiring [connectivity to the Payment HSM devices](peer-vnets.md?tabs=azure-cli).
+>
+> For the `fastpathenabled` VNet tag to be valid, the `FastPathEnabled` feature must be enabled on the subscription where that VNet is deployed. Both steps must be completed to enable resources to connect to the Payment HSM devices. For more information, see [FastPathEnabled](fastpathenabled.md).
+
+PHSM isn't compatible with vWAN topologies or cross region VNet peering, as listed in the [topology supported](solution-design.md#supported-topologies). Payment HSM comes with some policy [restrictions](solution-design.md#constraints) on these subnets: **Network Security Groups (NSGs) and User-Defined Routes (UDRs) are currently not supported**.
+
+It's possible to bypass the current UDR restriction and inspect traffic destined to a Payment HSM. This article presents two ways: a firewall with source network address translation (SNAT), and a firewall with reverse proxy.
+
+## Firewall with source network address translation (SNAT)
+
+This design is inspired by the [Dedicated HSM solution architecture](../dedicated-hsm/networking.md#solution-architecture).
+
+The firewall **SNATs the client IP address** before forwarding traffic to the PHSM NIC, guaranteeing that the return traffic will automatically be directed back to the Firewall. Either an Azure Firewall or a third party FW NVA can be used in this design.
++
+Route tables required:
+- On-premises to PHSM: a Route Table containing a UDR for the Payment HSM VNet range and pointing to the central hub Firewall is applied to the GatewaySubnet.
+- Spoke VNet(s) to PHSM: a Route Table containing the usual default route pointing to the central hub Firewall is applied to the Spoke VNet(s) subnets.
+
+Results:
+- UDRs not being supported on the PHSM subnet is addressed by the Firewall doing SNAT on the client IP: when forwarding traffic to PHSM, the return traffic will automatically be directed back to the Firewall.
+- Filtering rules that cannot be enforced using NSGs on the PHSM subnet can be configured on the Firewall.
+- Both Spoke traffic and on-premises traffic to the PHSM environment are secured.
+
+## Firewall with reverse proxy
+
+This design is a good option when performing SNAT on a Firewall that has not been approved by network security teams, requiring instead to keep the source and destination IPs unchanged for traffic crossing the Firewall.
+
+This architecture uses a reverse proxy, deployed in a dedicated subnet in the PHSM VNet directly or in a peered VNet. Instead of sending traffic to the PHSM devices, the destination is set to the reverse proxy IP, located in a subnet that does not have the restrictions of the PHSM delegated subnet: both NSGs and UDRs can be configured, and combined with a Firewall in the central hub.
++
+This solution requires a reverse proxy, such as:
+
+- F5 (Azure Marketplace; VM-based)
+- NGINXaaS (Azure Marketplace; PaaS fully managed)
+- Reverse proxy Server using NGINX (VM-based)
+- Reverse proxy Server using HAProxy (VM-based)
+
+Example of reverse proxy Server using NGINX (VM-based) configuration:
+
+```conf
+# Nginx.conf  
+stream { 
+ server { 
+ listen 1500; 
+        proxy_pass 10.221.8.4:1500; 
+    } 
+
+    upstream phsm { 
+     server 10.221.8.5:443; 
+    } 
+
+    server { 
+     listen 443; 
+        proxy_pass phsm; 
+        proxy_next_upstream on; 
+ } 
+} 
+```
+
+Route tables required:
+- On-premises to PHSM: a Route Table containing a UDR for the Payment HSM VNet range and pointing to the central hub Firewall is applied to the GatewaySubnet.
+- Spoke VNet(s) to PHSM: a Route Table containing the usual default route pointing to the central hub Firewall is applied to the Spoke VNet(s) subnets.
+
+> [!IMPORTANT]
+> Gateway Route propagation must be disabled on the reverse proxy subnet, so that a 0/0 UDR is enough to force the return traffic via the firewall.
+
+Results:
+- UDRs not being supported on the PHSM subnet can be configured on the reverse proxy subnet.
+- The reverse proxy SNATs the client IP: when forwarding traffic to PHSM, the return traffic will automatically be directed back to the reverse proxy.
+- Filtering rules that cannot be enforced using NSGs on the PHSM subnet can be configured on the Firewall and/or on NSGs applied to the reverse proxy subnet.
+- Both Spoke traffic and on-premises traffic to the PHSM environment are secured.
+
+## Next steps
+
+- [What is Azure Payment HSM?](overview.md)
+- [Azure Payment HSM solution design](solution-design.md)
+- [Azure Payment HSM deployment scenarios](deployment-scenarios.md)
+- [Get started with Azure Payment HSM](getting-started.md)
+- [Create a payment HSM](create-payment-hsm.md)
+- [Frequently asked questions](faq.yml)
payment-hsm Overview https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/payment-hsm/overview.md
Azure Payment HSM is a "BareMetal" service delivered using [Thales payShield 10K
Payment HSMs are provisioned and connected directly to users' virtual network, and HSMs are under users' sole administration control. HSMs can be easily provisioned as a pair of devices and configured for high availability. Users of the service utilize [Thales payShield Manager](https://cpl.thalesgroup.com/encryption/hardware-security-modules/payment-hsms/payshield-manager) for secure remote access to the HSMs as part of their Azure-based subscription. Multiple subscription options are available to satisfy a broad range of performance and multiple application requirements that can be upgraded quickly in line with end-user business growth. Azure payment HSM service offers highest performance level 2500 CPS.
+Payment HSM devices are a variation of [Dedicated HSM](../dedicated-hsm/index.yml) devices, with more advanced cryptographic modules and features; for example, a payment HSM never decrypts the PIN value in transit.
+
+The Azure Payment HSM solution uses hardware from [Thales](https://cpl.thalesgroup.com/encryption/hardware-security-modules/payment-hsms/payshield-10k) as a vendor. Customers have [full control and exclusive access](overview.md#customer-managed-hsm-in-azure) to the Payment HSM.
+ > [!IMPORTANT] > Azure Payment HSM a highly specialized service. We highly recommend that you review the [Azure Payment HSM pricing page](https://azure.microsoft.com/services/payment-hsm/) and [Getting started with Azure Payment HSM](getting-started.md#support).
Azure Payment HSM supports the following SKUs:
||| | 3DS | 3D Secure | | ATM | Automated Teller Machine |
-| EMV | Europay Mastercard Visa |
+| EMV | Euro Mastercard Visa |
| FIPS | Federal Information Processing Standards | | HCE | Host Card Emulation | | HSM | Hardware Security Module |
payment-hsm Solution Design https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/payment-hsm/solution-design.md
The following table describes what's supported for each network features configu
## Next steps -- Learn more about [Azure Payment HSM](overview.md)-- See Azure Payment HSM [Deployment Scenarios](deployment-scenarios.md)-- Find out how to [get started with Azure Payment HSM](getting-started.md)-- Learn how to [Create a payment HSM](create-payment-hsm.md)-- Read the [frequently asked questions](faq.yml)
+- [What is Azure Payment HSM?](overview.md)
+- [Azure Payment HSM deployment scenarios](deployment-scenarios.md)
+- [Azure Payment HSM traffic inspection](inspect-traffic.md)
+- [Get started with Azure Payment HSM](getting-started.md)
+- [Create a payment HSM](create-payment-hsm.md)
+- [Frequently asked questions](faq.yml)
payment-hsm Solution Design https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/principles-for-ai-generated-content.md
- Title: Principles for AI generated content
-description: Describes Microsoft's approach for using AI-generated content on Microsoft Learn
---- Previously updated : 02/26/2023--
-# Our principles for using AI-generated content on Microsoft Learn
-
-Microsoft uses [Azure OpenAI Service](./cognitive-services/openai/index.yml) to generate some of the text and code examples that we publish on [Microsoft Learn](/). This article describes our approach for using Azure OpenAI to generate technical content that supports our products and services.
-
-At Microsoft, we're working to add articles to Microsoft Learn that contain AI-generated content. Over time, more articles will feature AI-generated text and code samples.
-
-For information about the broader effort at Microsoft to put our AI principles into practice, see [Microsoft's AI principles](https://www.microsoft.com/ai/responsible-ai).
-
-## Our commitment
-
-We're committed to providing you with accurate and comprehensive learning experiences for Microsoft products and services. By using AI-generated content, we can extend the content for your scenarios. We can provide more examples in more programming languages. We can cover solutions in greater detail. We can cover new scenarios more rapidly.
-
-We understand that AI-generated content isn't always accurate. We test and review AI-generated content before we publish it.
-
-## Transparency
-
-We're transparent about articles that contain AI-generated content. All articles that contain any AI-generated content include text acknowledging the role of AI. You'll see this text at the top of the article.
-
-## Augmentation
-
-For articles that contain AI-generated content, our authors use AI to augment their content creation process. For example, an author plans what to cover in the article, and then uses Azure OpenAI to generate part of the content. Or, the author runs a process to convert an existing article from one programming language to another language. The author reviews and revises the AI-generated content. Finally, the author writes any remaining sections.
-
-These articles contain a mix of authored content and AI-generated content and are clearly marked as containing AI-generated content.
-
-## Validation
-
-The author reviews all AI-generated content and revises it as needed. After the author has reviewed the content, the article goes through our standard validation process to check for formatting errors, and to make sure the terms and language are appropriate and inclusive. The article is eligible for publishing only after passing all validation tests.
-
-The author tests all AI-generated code before publishing. The author either manually tests the code or runs it through an automated test process.
-
-## AI models
-
-Currently, we're using large language models from OpenAI accessed through Azure OpenAI Service to generate content. Specifically, we're using the GPT-3 and Codex language models.
-
-We may add other AI services in the future and will update this page periodically to reflect our updated practices.
reliability Reliability Azure Storage Mover https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/reliability/reliability-azure-storage-mover.md
+
+ Title: Reliability in Azure Storage Mover
+description: Find out about reliability in Azure Storage Mover
+++++ Last updated : 03/21/2023++
+<!--
+!########################################################
+STATUS: IN REVIEW
+
+CONTENT: final
+
+REVIEW Stephen/Fabian: completed
+REVIEW Engineering: not reviewed
+EDIT PASS: completed
+
+Initial doc score: 70
+Current doc score: 100, 1130, 0
+
+!########################################################
+-->
+
+# What is reliability in Azure Storage Mover?
+
+This article describes reliability support in Azure Storage Mover and covers cross-region resiliency with disaster recovery. For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
+
+## Regional reliability
+
+When deploying an Azure Storage Mover resource, you must select a location in which the resource's instance metadata is stored. Instance metadata includes projects, endpoints, agents, job definitions, and job run history, but doesn't include the actual data to be migrated. Azure storage accounts to be used as migration targets have their own reliability support. Disaster recovery for on-premises data sources is the responsibility of the customer.
+
+Instance metadata is replicated across multiple availability zones in regions where availability zones are available. Availability zones are unique physical locations within an Azure region. Each zone is made up of one or more data centers equipped with independent power, cooling, and networking.
+
+Some regions are paired in order to allow cross-region replication. When cross-region replication is utilized, instance metadata is replicated to each region, but is never permitted to leave the geography.
+
+When a Storage Mover agent is registered, it connects to the region in which the Storage Mover resource is registered. If an agent's Azure region experiences an outage, the agent itself isn't affected, but management operations that rely on Azure may be unable to complete. In addition, any active data migrations to storage accounts located within the affected region may fail.
+
+In the unlikely event of a full region outage, you have the option of using one of the following strategies:
+
+- Wait for Azure to recover the region
+- Redeploy your resources to a different region
+- Deploy a redundant Storage Mover in advance
+
+The last two options are a matter of timing, since deployment will occur either before or after any future outage.
+
+## Determining reliability for target storage accounts
+
+Any migration target storage account may require its own recovery steps. This requirement depends on the redundancy options chosen for each storage account. See the [storage account disaster recovery](/azure/storage/common/storage-disaster-recovery-guidance) article to determine whether more steps are necessary.
+
+If a local storage was chosen in lieu of redundancy options, you may need to create a new storage account for use in migrations during the outage.
+
+### Zone down experience
+
+During a zone-wide outage, no action is required during zone recovery. Azure Storage Mover is designed to self-heal and rebalance itself to take advantage of the healthy zone automatically.
+
+## Disaster recovery: cross-region failover
+
+Azure can provide disaster recovery protection against a region-wide or large geography disaster by making use of another region. For more information on Azure disaster recovery architecture, see the article on [Azure to Azure disaster recovery architecture](/azure/site-recovery/azure-to-azure-architecture).
+
+Azure initiated disaster recovery is only applicable for those regions that have are paired with a cross-region replication region. Azure Storage Mover uses Cosmos DB for storing instance metadata. Data loss may occur only with an unrecoverable disaster in the Azure Cosmos DB region. For more information, see [Region outages](/azure/cosmos-db/high-availability). Azure initiated recovery is active-passive, and full recovery of a region may be up to 24 hours.
+
+Customers can minimize downtime by following the customer enabled disaster recovery steps described in this section. These strategies may require that further steps be taken prior to a disaster, so be sure to review and plan accordingly.
+
+## Customer enabled disaster recovery
+
+### Deploy resources to a different region
+
+Since access to your resources may be impacted during an outage. To redeploy resources to a different region, you must first have a snapshot of the resources you wish to redeploy. To ensure that you're restoring the most recent data, taking a snapshot should be done periodically, either on a schedule or after you make substantial changes. Storing the snapshots using a version control system is a good way to store and track history of the snapshots.
+
+See the documentation on [exporting templates](/azure/azure-resource-manager/templates/export-template-portal) for further instructions on exporting resources as an Azure Resource Manager (ARM) template.
+
+If your Storage Mover and related resources reside in a container with no extra resources, you should perform a **Resource Group** export to capture the current state. However, if your resource group contains unrelated resources, you may need to remove or otherwise exclude the resources from the template.
+
+Existing agents can't be redeployed to a different region. If the region in which they were originally configured experiences an outage, it may not be possible to completely unregister and re-register the agent. This document assumes that new agents are registered within a new region.
+
+To use the exported template for disaster recovery, a few changes to the template are required.
+
+- First, remove any `Microsoft.StorageMover/agents` and `Microsoft.HybridCompute/machines` resources from the template. Be sure to remove any dependency references to these resources as well.
+- Next, remove the `agentResourceId` property from all job definitions. You'll need to assign them to a new Agent after deployment.
+- After removing all references to agent and Hybrid Compute machine resources, update the location property of the top level Storage Mover resource. Replace the name of the currently deployed region with the name of the new region.
+- Finally, determine whether to keep the existing storage account resource ID. If necessary, replace it with a different storage account.
+
+After completing the previous steps and verifying that the template parameters are correct, the template is ready for deployment to a new region. You should deploy the template to a new resource group that has the same default region as the location property in the template.
+
+### Registering the new agent
+
+Follow the steps within the [deploy an Azure Storage Mover agent](/azure/storage-mover/agent-deploy) article to register a new agent in the new Storage Mover resource.
+
+### Assigning the agent to job definitions
+
+After the new agent has been registered and reports as online, use the Azure portal or PowerShell to associate the existing job definitions to the new agent. The following PowerShell example is provided for convenience.
+
+See the [define a new migration job](/azure/storage-mover/job-definition-create) for guidance on how to access the job definitions for your project.
+
+```powershell
+
+## Update the agent in a job definition resource
+$resourceGroupName = "[Your resource group name]"
+$storageMoverName = "[Your storage mover name]"
+$projectName = "[Your project name]"
+$jobDefName = "[Your job definition name]"
+$agentName = "[The name of an agent previously registered to the same storage mover resource]"
+
+Update-AzStorageMoverJobDefinition `
+ -ResourceGroupName $resourceGroupName `
+ -StorageMoverName $storageMoverName `
+ -ProjectName $projectName `
+ -Name $jobDefName `
+ -AgentName $agentName
+```
+
+### Granting agent access to the target storage container
+
+You need to assign the data contributor role to the managed identity to successfully perform a migration job. Assign the Hybrid Compute resource's system managed identity access to the target storage account resource. The [assign a managed identity access to a resource](/azure/active-directory/managed-identities-azure-resources/howto-assign-access-portal) article provides guidance on how to grant access to the target resource.
+
+You're now ready to start migration jobs using the newly deployed Storage Mover resources.
+
+## Next steps
+
+Read more about any of the following features or options.
+
+| Guide | Description |
+|||
+| [Azure resiliency and reliability](/azure/architecture/framework/resiliency/overview) | A detailed overview of resiliency and reliability in Azure.
+| [storage account disaster recovery](/azure/storage/common/storage-disaster-recovery-guidance) | Concepts and processes involved with a storage account failover and recovery. |
route-server Routing Preference https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/route-server/routing-preference.md
- Title: Routing preference-
-description: Learn about Azure Route Server routing preference feature.
---- Previously updated : 04/06/2023---
-# Azure Route Server routing preference
-
-Azure Route Server enables dynamic routing between network virtual appliances (NVAs) and virtual networks (VNets). In addition to supporting third-party NVAs, Route Server also seamlessly integrates with ExpressRoute and VPN gateways. Route Server uses built-in route selection algorithms to make routing decisions to set connection preferences.
-
-When **branch-to-branch** is enabled and Route Server learns multiple routes across site-to-site (S2S) VPN, ExpressRoute and SD-WAN NVAs, for the same on-premises destination route prefix, users can now configure connection preferences to influence Route Server route selection.
-
-> [!IMPORTANT]
-> Routing preference is only available for Route Servers deployed on or after April 7, 2023. Support for existing Route Servers, deployed before April 7, 2023, will be backfilled at a later date. For any questions, please open [a support request in the Azure Portal](https://aka.ms/azsupt).
-
-## Routing preference configuration
-
-When Route Server has multiple routes to an on-premises destination prefix, Route Server selects the best route(s) in order of preference, as follows:
-
-1. Prefer routes with the longest prefix match (LPM)
-1. Prefer static routes over BGP routes
-1. Prefer routes based on routing preference configuration:
- * **ExpressRoute**: (This is the default setting): Prefer routes learned through ExpressRoute over routes learned through VPN/SD-WAN connections
- * **VPN/SD-WAN**: Prefer routes learned through VPN/SD-WAN connections over routes learned through ExpressRoute.
- > [!IMPORTANT]
- > Routing preference doesn't allow users to set preference between routes learned over VPN and SD-WAN connections. If the same routes are learned over VPN and SD-WAN connections, Route Server will prefer the route with the shortest BGP AS-PATH.
- * **AS-Path**: Prefer routes with the shortest BGP AS-PATH length, irrespective of the source of the route advertisement.
-
-## Next steps
--- Learn how to [configure Azure Route Server](quickstart-configure-route-server-portal.md).-- Learn how to [monitor Azure Route Server](monitor-route-server.md).
sap Get Started https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/sap/workloads/get-started.md
ms.assetid: ad8e5c75-0cf6-4564-ae62-ea1246b4e5f2
vm-linux Previously updated : 03/27/2023 Last updated : 04/06/2023
In the SAP workload documentation space, you can find the following areas:
## Change Log
+- April 6, 2023: Updates for RHEL 9 in [Setting up Pacemaker on RHEL in Azure](./high-availability-guide-rhel-pacemaker.md)
- March 26, 2023: Adding recommended sector size in [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md) - March 1, 2023: Change in [HA for SAP HANA on Azure VMs on RHEL](./sap-hana-high-availability-rhel.md) to add configuration for cluster default properties - February 21, 2023: Correct link to HANA hardware directory in [SAP HANA infrastructure configurations and operations on Azure](./hana-vm-operations.md) and fixed a bug in [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md)
search Search Get Started Dotnet https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/search/search-get-started-dotnet.md
Before you begin, have the following tools and
+ An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/).
-+ An Azure Cognitive Search service. [Create a service](search-create-service-portal.md) or [find an existing service](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices). You can use a free service for this quickstart.
++ An Azure Cognitive Search service. [Create a service](search-create-service-portal.md) or [find an existing service](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices). You can use a free service for this quickstart. + [Visual Studio](https://visualstudio.microsoft.com/downloads/), any edition. Sample code was tested on the free Community edition of Visual Studio 2019. When setting up your project, you'll download the [Azure.Search.Documents NuGet package](https://www.nuget.org/packages/Azure.Search.Documents/). Azure SDK for .NET conforms to [.NET Standard 2.0](/dotnet/standard/net-standard#net-implementation-support), which means .NET Framework 4.6.1 and .NET Core 2.1 as minimum requirements.+ ## Set up your project Assemble service connection information, and then start Visual Studio to create a new Console App project that can run on. Select NET Core 3.1 for the run time.
After the project is created, add the client library. The [Azure.Search.Document
1. Start Visual Studio and create a .NET Core console application.
-1. In **Tools** > **NuGet Package Manager**, select **Manage NuGet Packages for Solution...**.
+1. In **Tools** > **NuGet Package Manager**, select **Manage NuGet Packages for Solution...**.
1. Select **Browse**.
In this example, synchronous methods of the Azure.Search.Documents library are u
+ `SearchableField` must be a string, and is always searchable and retrievable. Other attributes are off by default, but can be enabled. Because this field type is searchable, it supports synonyms and the full complement of analyzer properties. For more information, see the [SearchableFieldAttribute.cs](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/search/Azure.Search.Documents/src/Indexes/SearchableFieldAttribute.cs) in source code.
- Whether you use the basic `SearchField` API or either one of the helper models, you must explicitly enable filter, facet, and sort attributes. For example, [IsFilterable](/dotnet/api/azure.search.documents.indexes.models.searchfield.isfilterable), [IsSortable](/dotnet/api/azure.search.documents.indexes.models.searchfield.issortable), and [IsFacetable](/dotnet/api/azure.search.documents.indexes.models.searchfield.isfacetable) must be explicitly attributed, as shown in the sample above.
+ Whether you use the basic `SearchField` API or either one of the helper models, you must explicitly enable filter, facet, and sort attributes. For example, [IsFilterable](/dotnet/api/azure.search.documents.indexes.models.searchfield.isfilterable), [IsSortable](/dotnet/api/azure.search.documents.indexes.models.searchfield.issortable), and [IsFacetable](/dotnet/api/azure.search.documents.indexes.models.searchfield.isfacetable) must be explicitly attributed, as shown in the sample above.
1. Add a second empty class definition to your project: **Address.cs**. Copy the following code into the class.
In this example, synchronous methods of the Azure.Search.Documents library are u
Azure Cognitive Search searches over content stored in the service. In this step, you'll load JSON documents that conform to the hotel index you just created.
-In Azure Cognitive Search, search documents are data structures that are both inputs to indexing and outputs from queries. As obtained from an external data source, document inputs might be rows in a database, blobs in Blob storage, or JSON documents on disk. In this example, we're taking a shortcut and embedding JSON documents for four hotels in the code itself.
+In Azure Cognitive Search, search documents are data structures that are both inputs to indexing and outputs from queries. As obtained from an external data source, document inputs might be rows in a database, blobs in Blob storage, or JSON documents on disk. In this example, we're taking a shortcut and embedding JSON documents for four hotels in the code itself.
When uploading documents, you must use an [IndexDocumentsBatch](/dotnet/api/azure.search.documents.models.indexdocumentsbatch-1) object. An `IndexDocumentsBatch` object contains a collection of [Actions](/dotnet/api/azure.search.documents.models.indexdocumentsbatch-1.actions), each of which contains a document and a property telling Azure Cognitive Search what action to perform ([upload, merge, delete, and mergeOrUpload](search-what-is-data-import.md#indexing-actions)).
The [SearchResults](/dotnet/api/azure.search.documents.models.searchresults-1) c
WriteDocuments(response); ```
-1. In the second query, search on a term, add a filter that selects documents where Rating is greater than 4, and then sort by Rating in descending order. Filter is a boolean expression that is evaluated over [IsFilterable](/dotnet/api/azure.search.documents.indexes.models.searchfield.isfilterable) fields in an index. Filter queries either include or exclude values. As such, there's no relevance score associated with a filter query.
+1. In the second query, search on a term, add a filter that selects documents where Rating is greater than 4, and then sort by Rating in descending order. Filter is a boolean expression that is evaluated over [IsFilterable](/dotnet/api/azure.search.documents.indexes.models.searchfield.isfilterable) fields in an index. Filter queries either include or exclude values. As such, there's no relevance score associated with a filter query.
```csharp // Query 2
The [SearchResults](/dotnet/api/azure.search.documents.models.searchresults-1) c
WriteDocuments(response); ```
-1. The fourth query demonstrates facets, which can be used to structure a faceted navigation structure.
+1. The fourth query demonstrates facets, which can be used to structure a faceted navigation structure.
```csharp // Query 4
The [SearchResults](/dotnet/api/azure.search.documents.models.searchresults-1) c
var autoresponse = srchclient.Autocomplete("sa", "sg"); WriteDocuments(autoresponse); ```+ 1. Add **RunQueries** to Main(). ```csharp
Full text search and filters are performed using the [SearchClient.Search](/dotn
## Run the program
-Press F5 to rebuild the app and run the program in its entirety.
+Press F5 to rebuild the app and run the program in its entirety.
Output includes messages from [Console.WriteLine](/dotnet/api/system.console.writeline), with the addition of query information and results.
When you're working in your own subscription, it's a good idea at the end of a p
You can find and manage resources in the portal, using the **All resources** or **Resource groups** link in the left-navigation pane.
-If you're using a free service, remember that you're limited to three indexes, indexers, and data sources. You can delete individual items in the portal to stay under the limit.
+If you're using a free service, remember that you're limited to three indexes, indexers, and data sources. You can delete individual items in the portal to stay under the limit.
## Next steps
search Search Howto Index Sharepoint Online https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/search/search-howto-index-sharepoint-online.md
Last updated 04/04/2023
# Index data from SharePoint document libraries
-> [!IMPORTANT]
-> SharePoint indexer support is currently in public preview under [Supplemental Terms of Use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). [Request access](https://aka.ms/azure-cognitive-search/indexer-preview) to this feature, and after access is enabled, use a [preview REST API (2020-06-30-preview or later)](search-api-preview.md) to index your content. There is currently limited portal support and no .NET SDK support.
+> [!IMPORTANT]
+> SharePoint indexer support is in public preview. It's offered "as-is", under [Supplemental Terms of Use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Preview features aren't recommended for production workloads and aren't guaranteed to become generally available.
+>
+>To use this preview, [request access](https://aka.ms/azure-cognitive-search/indexer-preview), and after access is enabled, use a [preview REST API (2020-06-30-preview or later)](search-api-preview.md) to index your content. There is currently limited portal support and no .NET SDK support.
This article explains how to configure a [search indexer](search-indexer-overview.md) to index documents stored in SharePoint document libraries for full text search in Azure Cognitive Search. Configuration steps are followed by a deeper exploration of behaviors and scenarios you're likely to encounter. - ## Functionality An indexer in Azure Cognitive Search is a crawler that extracts searchable data and metadata from a data source. The SharePoint indexer will connect to your SharePoint site and index documents from one or more document libraries. The indexer provides the following functionality:
search Tutorial Csharp Create Mvc App https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/search/tutorial-csharp-create-mvc-app.md
For the connection, the app presents a query API key to your fully qualified sea
Modify `appsettings.json` to specify your search service and [query API key](search-security-api-keys.md).
- ```json
- {
- "SearchServiceName": "https://<YOUR-SEARCH-SERVICE-NAME>.search.windows.net",
- "SearchServiceQueryApiKey": "<YOUR-SEARCH-SERVICE-QUERY-API-KEY>"
- }
- ```
+```json
+{
+ "SearchServiceUri": "<YOUR-SEARCH-SERVICE-URL>",
+ "SearchServiceQueryApiKey": "<YOUR-SEARCH-SERVICE-QUERY-API-KEY>"
+}
+```
+
+You can get the [service URL and API key](search-get-started-dotnet.md#copy-a-key-and-endpoint) from the portal. Because this code is querying an index and not creating one, you can use a query key instead of an admin key.
+
+Make sure to specify the search service that has the hotels-sample-index.
## Add models
-In this step, create models that represent the schema of the hotels-search-index.
+In this step, create models that represent the schema of the hotels-sample-index.
1. In Solution explorer, right-select **Models** and add a new class named "Hotel" for the following code:
service-fabric Service Fabric Connect To Secure Cluster https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/service-fabric/service-fabric-connect-to-secure-cluster.md
catch (Exception e)
### Connect to a secure cluster non-interactively using Azure Active Directory
-The following example relies on Microsoft.IdentityModel.Clients.ActiveDirectory, Version: 2.19.208020213.
-
-> [!IMPORTANT]
-> The [Microsoft.IdentityModel.Clients.ActiveDirectory](https://www.nuget.org/packages/Microsoft.IdentityModel.Clients.ActiveDirectory) NuGet package and Azure AD Authentication Library (ADAL) have been deprecated. No new features have been added since June 30, 2020. We strongly encourage you to upgrade, see the [migration guide](../active-directory/develop/msal-migration.md) for more details.
+The following example relies on Microsoft.Identity.Client, Version: 4.37.0.
For more information on AAD token acquisition, see [Microsoft.Identity.Client](/dotnet/api/microsoft.identity.client?view=azure-dotnet&preserve-view=true).
For more information on AAD token acquisition, see [Microsoft.Identity.Client](/
string tenantId = "C15CFCEA-02C1-40DC-8466-FBD0EE0B05D2"; string clientApplicationId = "118473C2-7619-46E3-A8E4-6DA8D5F56E12"; string webApplicationId = "53E6948C-0897-4DA6-B26A-EE2A38A690B4";
+string[] scopes = new string[] { "user.read" };
+
+var pca = PublicClientApplicationBuilder.Create(clientApplicationId)
+ .WithAuthority($"https://login.microsoftonline.com/{tenantId}")
+ .WithRedirectUri("urn:ietf:wg:oauth:2.0:oob")
+ .Build();
-string token = GetAccessToken(
- tenantId,
- webApplicationId,
- clientApplicationId,
- "urn:ietf:wg:oauth:2.0:oob");
+var accounts = await pca.GetAccountsAsync();
+var result = await pca.AcquireTokenInteractive(scopes)
+ .WithAccount(accounts.FirstOrDefault())
+ .ExecuteAsync();
+
+string token = result.AccessToken;
string serverCertThumb = "A8136758F4AB8962AF2BF3F27921BE1DF67F4326"; string connection = "clustername.westus.cloudapp.azure.com:19000";
catch (Exception e)
{ Console.WriteLine("Connect failed: {0}", e.Message); }-
-...
-
-static string GetAccessToken(
- string tenantId,
- string resource,
- string clientId,
- string redirectUri)
-{
- string authorityFormat = @"https://login.microsoftonline.com/{0}";
- string authority = string.Format(CultureInfo.InvariantCulture, authorityFormat, tenantId);
- var authContext = new AuthenticationContext(authority);
-
- var authResult = authContext.AcquireToken(
- resource,
- clientId,
- new UserCredential("TestAdmin@clustenametenant.onmicrosoft.com", "TestPassword"));
- return authResult.AccessToken;
-}
- ``` ### Connect to a secure cluster without prior metadata knowledge using Azure Active Directory
claimsCredentials.ServerThumbprints.Add(serverCertThumb);
var fc = new FabricClient(claimsCredentials, connection);
-fc.ClaimsRetrieval += (o, e) =>
+fc.ClaimsRetrieval += async (o, e) =>
{
- return GetAccessToken(e.AzureActiveDirectoryMetadata);
+ var accounts = await PublicClientApplicationBuilder
+ .Create("<client_id>")
+ .WithAuthority(AzureCloudInstance.AzurePublic, "<tenant_id>")
+ .WithRedirectUri("<redirect_uri>")
+ .Build()
+ .GetAccountsAsync();
+
+ var result = await PublicClientApplicationBuilder
+ .Create("<client_id>")
+ .WithAuthority(AzureCloudInstance.AzurePublic, "<tenant_id>")
+ .WithRedirectUri("<redirect_uri>")
+ .Build()
+ .AcquireTokenInteractive(new[] { "<scope>" })
+ .WithAccount(accounts.FirstOrDefault())
+ .ExecuteAsync();
+
+ return result.AccessToken;
}; try
catch (Exception e)
{ Console.WriteLine("Connect failed: {0}", e.Message); }-
-...
-
-static string GetAccessToken(AzureActiveDirectoryMetadata aad)
-{
- var authContext = new AuthenticationContext(aad.Authority);
-
- var authResult = authContext.AcquireToken(
- aad.ClusterApplication,
- aad.ClientApplication,
- new UserCredential("TestAdmin@clustenametenant.onmicrosoft.com", "TestPassword"));
- return authResult.AccessToken;
-}
- ``` <a id="connectsecureclustersfx"></a>
service-fabric Service Fabric Get Started https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/service-fabric/service-fabric-get-started.md
For latest Runtime and SDK you can download from below:
| Package |Version| | | |
-|[Install Service Fabric Runtime for Windows](https://download.microsoft.com/download/b/8/a/b8a2fb98-0ec1-41e5-be98-9d8b5abf7856/MicrosoftServiceFabric.9.1.1583.9590.exe) | 9.1.1583 |
-|[Install Service Fabric SDK](https://download.microsoft.com/download/b/8/a/b8a2fb98-0ec1-41e5-be98-9d8b5abf7856/MicrosoftServiceFabricSDK.6.1.1583.msi) | 6.1.1583 |
+|[Install Service Fabric Runtime for Windows](https://download.microsoft.com/download/b/8/a/b8a2fb98-0ec1-41e5-be98-9d8b5abf7856/MicrosoftServiceFabric.9.1.1653.9590.exe) | 9.1.1653 |
+|[Install Service Fabric SDK](https://download.microsoft.com/download/b/8/a/b8a2fb98-0ec1-41e5-be98-9d8b5abf7856/MicrosoftServiceFabricSDK.6.1.1653.msi) | 6.1.1653 |
You can find direct links to the installers for previous releases on [Service Fabric Releases](https://github.com/microsoft/service-fabric/tree/master/release_notes)
service-fabric Service Fabric Versions https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/service-fabric/service-fabric-versions.md
If you want to find a list of all the available Service Fabric runtime versions
### Current versions | Service Fabric runtime |Can upgrade directly from|Can downgrade to*|Compatible SDK or NuGet package version|Supported .NET runtimes** |OS Version |End of support | | | | | | | | |
+| 9.1 CU3<br>9.1.1653.9590 | 8.2 CU6<br>8.2.1686.9590 | 8.2 | Less than or equal to version 6.0 | .NET 7, .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version |
| 9.1 CU2<br>9.1.1583.9590 | 8.2 CU6<br>8.2.1686.9590 | 8.2 | Less than or equal to version 6.0 | .NET 7, .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version | | 9.1 CU1<br>9.1.1436.9590 | 8.2 CU6<br>8.2.1686.9590 | 8.2 | Less than or equal to version 6.0 | .NET 6.0 (GA), >= .NET Core 3.1, <br>All >= .NET Framework 4.5 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version | | 9.1 RTO<br>9.1.1390.9590 | 8.2 CU6<br>8.2.1686.9590 | 8.2 | Less than or equal to version 6.0 | .NET 6.0 (GA), >= .NET Core 3.1, <br>All >= .NET Framework 4.5 | [See supported OS version](#supported-windows-versions-and-support-end-date) | Current version |
+| 9.0 CU8<br>9.0.1380.9590 | 8.0 CU3<br>8.0.536.9590 | 8.0 | Less than or equal to version 6.0 | .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | November 1, 2023 |
| 9.0 CU7<br>9.0.1309.9590 | 8.0 CU3<br>8.0.536.9590 | 8.0 | Less than or equal to version 6.0 | .NET 6, All, <br> >= .NET Framework 4.6.2 | [See supported OS version](#supported-windows-versions-and-support-end-date) | November 1, 2023 | | 9.0 CU6<br>9.0.1254.9590 | 8.0 CU3<br>8.0.536.9590 | 8.0 | Less than or equal to version 6.0 | .NET 6.0 (GA), >= .NET Core 3.1, <br>All >= .NET Framework 4.5 | [See supported OS version](#supported-windows-versions-and-support-end-date) | November 1, 2023 | | 9.0 CU5<br>9.0.1155.9590 | 8.0 CU3<br>8.0.536.9590 | 8.0 | Less than or equal to version 6.0 | .NET 6.0 (GA), >= .NET Core 3.1, <br>All >= .NET Framework 4.5 | [See supported OS version](#supported-windows-versions-and-support-end-date) | November 1, 2023 |
Support for Service Fabric on a specific OS ends when support for the OS version
### Current versions | Service Fabric runtime | Can upgrade directly from |Can downgrade to*|Compatible SDK or NuGet package version | Supported .NET runtimes** | OS version | End of support | | | | | | | | |
+| 9.1 CU3<br>9.1.1457.1 | 8.2 CU6<br>8.2.1485.1 | 8.2 | .NET 7, .NET 6, All | N/A | [See supported OS version](#supported-linux-versions-and-support-end-date) | Current version |
| 9.1 CU2<br>9.1.1388.1 | 8.2 CU6<br>8.2.1485.1 | 8.2 | .NET 7, .NET 6, All | N/A | [See supported OS version](#supported-linux-versions-and-support-end-date) | Current version | | 9.1 CU1<br>9.1.1230.1 | 8.2 CU6<br>8.2.1485.1 | 8.2 | Less than or equal to version 6.0 | >= .NET Core 2.1 | [See supported OS version](#supported-linux-versions-and-support-end-date) | Current version | | 9.1 RTO<br>9.1.1206.1 | 8.2 CU6<br>8.2.1485.1 | 8.2 | Less than or equal to version 6.0 | >= .NET Core 2.1 | [See supported OS version](#supported-linux-versions-and-support-end-date) | Current version |
+| 9.0 CU8<br>9.0.1317.1 | 8.0 CU3<br>8.0.527.1 | 8.2 CU 5.1<br>8.2.1483.1 | .NET 6 | N/A | [See supported OS version](#supported-linux-versions-and-support-end-date) | November 1, 2023 |
| 9.0 CU7<br>9.0.1260.1 | 8.0 CU3<br>8.0.527.1 | 8.2 CU 5.1<br>8.2.1483.1 | .NET 6 | N/A | [See supported OS version](#supported-linux-versions-and-support-end-date) | November 1, 2023 | | 9.0 CU5<br>9.0.1148.1 | 8.0 CU3<br>8.0.527.1 | 8.2 CU 5.1<br>8.2.1483.1 | Less than or equal to version 6.0 | >= .NET Core 2.1 | [See supported OS version](#supported-linux-versions-and-support-end-date) | November 1, 2023 | | 9.0 CU4<br>9.0.1114.1 | 8.0 CU3<br>8.0.527.1 | 8.2 CU 5.1<br>8.2.1483.1 | Less than or equal to version 6.0 | >= .NET Core 2.1 | [See supported OS version](#supported-linux-versions-and-support-end-date) | November 1, 2023 |
The following table lists the version names of Service Fabric and their correspo
| Version name | Windows version number | Linux version number | | | | |
-| 9.1 CU2 | 9.1.1583.9590| 9.1.1388.1 |
-| 9.1 CU1 | 9.1.1436.9590| 9.1.1230.1 |
-| 9.1 RTO | 9.1.1390.9590| 9.1.1206.1 |
+| 9.1 CU3 | 9.1.1653.9590 | 9.1.1457.1 |
+| 9.1 CU2 | 9.1.1583.9590 | 9.1.1388.1 |
+| 9.1 CU1 | 9.1.1436.9590 | 9.1.1230.1 |
+| 9.1 RTO | 9.1.1390.9590 | 9.1.1206.1 |
+| 9.0 CU8 | 9.0.1380.9590 | 9.0.1317.1 |
| 9.0 CU7 | 9.0.1309.9590 | 9.0.1260.1 | | 9.0 CU6 | 9.0.1254.9590 | Not applicable | | 9.0 CU5 | 9.0.1155.9590 | 9.0.1148.1 |
storage-mover Status Code https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/storage-mover/status-code.md
+
+ Title: Troubleshooting Azure Storage Mover job run error codes
+description: Learn how to understand and remediate errors raised by the Azure Storage Mover Agent.
++++ Last updated : 03/20/2023+++
+<!--
+!########################################################
+STATUS: IN REVIEW
+
+CONTENT: final
+
+REVIEW Stephen/Fabian: completed
+REVIEW Engineering: not reviewed
+EDIT PASS: completed
+
+Initial doc score: 79
+Current doc score: 100 (552, 0)
+
+!########################################################
+-->
+
+# Troubleshooting Storage Mover job run error codes
+
+An Azure Storage Mover agent uses string status codes for statuses that are conveyed to the end user. All status codes have the prefix *AZSM* followed by four decimal digits. The first decimal digit indicates the high-level scope of the status. Each status code should belong to one of the following scopes:
+
+- Status that applies to the entire agent.<br />These codes use the scope digit '0', and therefore and have the prefix "AZSM0".
+- Status that applies to a specific job run by the agent.<br />These codes use the scope digit '1' and therefore have the prefix "AZSM1".
+- Status that applies to a specific file or directory transferred by a job run by the agent.<br />These codes use the scope digit '2' and therefore have the prefix "AZSM2".
+
+Each of these scopes further divides statuses into categories and subcategories. Each subcategory typically reserves 20 status codes to accommodate future expansion.
+
+> [!TIP]
+> *AZSM0000* is the special scope-agnostic status code indicating successful operation. This should be used to signify successful operation at any scope/level.
+
+|Error Code |Error Message | Details/Troubleshooting steps/Mitigation |
+||--||
+| <a name="AZSM1001"></a>AZSM1001 |Failed to mount source path | Verify the provided server information, name or IP-address, is valid, or the source location is correct. |
+| <a name="AZSM1002"></a>AZSM1002 |Encountered an error while scanning the source | Retry or create a support ticket. |
+| <a name="AZSM1003"></a>AZSM1003 |Failed to access source folder due to permission issues | Check if the agent has been granted permissions correctly to the source file share. |
+| <a name="AZSM1004"></a>AZSM1004 |Source path provided is invalid | Create a new endpoint with a valid source share path and update the job definition and retry. |
+| <a name="AZSM1020"></a>AZSM1020 |Miscellaneous error while accessing source | Retry or create a support ticket. |
+| <a name="AZSM1021"></a>AZSM1021 |Failed to access target folder due to permission issues | Retry or create a support ticket. |
+| <a name="AZSM1022"></a>AZSM1022 |Target path provided is invalid | Create a new endpoint with a valid target container and path and update the job definition and retry. |
+| <a name="AZSM1023"></a>AZSM1023 |Lease expired for this agent on the target container | Retry or create a support ticket. |
+| <a name="AZSM1024"></a>AZSM1024 |Authorization failure on claiming the target container | The agent doesn't have the permission to access the target container. The role assignment is performed automatically while running jobs from the portal. If you're using the APIs/Powershell cmdlets/SDKs, then manually create a 'Storage Blob Data Contributor' role assignment for the agent to access the target storage account blob container. The [Assign an Azure role for access to blob data](/azure/storage/blobs/assign-azure-role-data-access) article may help resolve this issue. |
+| <a name="AZSM1025"></a>AZSM1025 |Authentication failure on claiming the target container | Retry or create a support ticket. |
+| <a name="AZSM1026"></a>AZSM1026 |Blob type in the target container not supported by the agent | This blob type is unsupported by the current Storage Mover agent. |
+| <a name="AZSM1040"></a>AZSM1040 |Miscellaneous error while accessing target | Retry or create a support ticket. |
+| <a name="AZSM1041"></a>AZSM1041 |Failed to send job progress | Retry or create a support ticket. |
+| <a name="AZSM1042"></a>AZSM1042 |Failed to create job | Retry or create a support ticket. |
+| <a name="AZSM1043"></a>AZSM1043 |Failed to resume job | Retry or create a support ticket. |
+| <a name="AZSM1044"></a>AZSM1044 |Failed to finalize the job | Retry or create a support ticket. |
+| <a name="AZSM1045"></a>AZSM1045 |Job was aborted while it was still running | Retry or create a support ticket. |
+| <a name="AZSM1060"></a>AZSM1060 |Miscellaneous error during job execution | Retry or create a support ticket. |
storage Anonymous Read Access Prevent https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/storage/blobs/anonymous-read-access-prevent.md
The following image shows the error that occurs if you try to create a storage a
- [Overview: Remediating anonymous public read access for blob data](anonymous-read-access-overview.md) - [Remediate anonymous public read access to blob data (classic deployments)](anonymous-read-access-prevent-classic.md)
+- [Security recommendations for Blob storage](security-recommendations.md)
storage Object Replication Prevent Cross Tenant Policies https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/storage/blobs/object-replication-prevent-cross-tenant-policies.md
Previously updated : 09/13/2022 Last updated : 04/06/2023
Object replication asynchronously copies block blobs from a container in one storage account to a container in another storage account. When you configure an object replication policy, you specify the source account and container and the destination account and container. After the policy is configured, Azure Storage automatically copies the results of create, update, and delete operations on a source object to the destination object. For more information about object replication in Azure Storage, see [Object replication for block blobs](object-replication-overview.md).
-By default, an authorized user is permitted to configure an object replication policy where the source account is in one Azure Active Directory (Azure AD) tenant, and the destination account is in a different tenant. If your security policies require that you restrict object replication to storage accounts that reside within the same tenant only, you can disallow the creation of policies where the source and destination accounts are in different tenants. By default, cross-tenant object replication is enabled for a storage account unless you explicitly disallow it.
+By default, an authorized user is permitted to configure an object replication policy where the source account is in one Azure Active Directory (Azure AD) tenant and the destination account is in a different tenant. If your security policies require that you restrict object replication to storage accounts that reside within the same tenant only, you can disallow the creation of policies where the source and destination accounts are in different tenants. By default, cross-tenant object replication is enabled for a storage account unless you explicitly disallow it.
This article describes how to remediate cross-tenant object replication for your storage accounts. It also describes how to create policies to enforce a prohibition on cross-tenant object replication for new and existing storage accounts.
The following image shows the error that occurs if you try to create a storage a
- [Object replication for block blobs](object-replication-overview.md) - [Configure object replication for block blobs](object-replication-configure.md)
+- [Security recommendations for Blob storage](security-recommendations.md)
storage Security Recommendations https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/storage/blobs/security-recommendations.md
Previously updated : 05/12/2022 Last updated : 04/06/2023
Microsoft Defender for Cloud periodically analyzes the security state of your Az
| Recommendation | Comments | Defender for Cloud | |-|-|--|
-| Use the Azure Resource Manager deployment model | Create new storage accounts using the Azure Resource Manager deployment model for important security enhancements, including superior Azure role-based access control (Azure RBAC) and auditing, Resource Manager-based deployment and governance, access to managed identities, access to Azure Key Vault for secrets, and Azure AD-based authentication and authorization for access to Azure Storage data and resources. If possible, migrate existing storage accounts that use the classic deployment model to use Azure Resource Manager. For more information about Azure Resource Manager, see [Azure Resource Manager overview](../../azure-resource-manager/management/overview.md). | - |
+| Use the Azure Resource Manager deployment model | Create new storage accounts using the Azure Resource Manager deployment model for important security enhancements, including superior Azure role-based access control (Azure RBAC) and auditing, Resource Manager-based deployment and governance, access to managed identities, access to Azure Key Vault for secrets, and Azure Active Directory (Azure AD) authentication and authorization for access to Azure Storage data and resources. If possible, migrate existing storage accounts that use the classic deployment model to use Azure Resource Manager. For more information about Azure Resource Manager, see [Azure Resource Manager overview](../../azure-resource-manager/management/overview.md). | - |
| Enable Microsoft Defender for all of your storage accounts | Microsoft Defender for Storage provides an additional layer of security intelligence that detects unusual and potentially harmful attempts to access or exploit storage accounts. Security alerts are triggered in Microsoft Defender for Cloud when anomalies in activity occur and are also sent via email to subscription administrators, with details of suspicious activity and recommendations on how to investigate and remediate threats. For more information, see [Configure Microsoft Defender for Storage](../common/azure-defender-storage-configure.md). | [Yes](../../defender-for-cloud/implement-security-recommendations.md) | | Turn on soft delete for blobs | Soft delete for blobs enables you to recover blob data after it has been deleted. For more information on soft delete for blobs, see [Soft delete for Azure Storage blobs](./soft-delete-blob-overview.md). | - | | Turn on soft delete for containers | Soft delete for containers enables you to recover a container after it has been deleted. For more information on soft delete for containers, see [Soft delete for containers](./soft-delete-container-overview.md). | - |
Microsoft Defender for Cloud periodically analyzes the security state of your Az
| Store business-critical data in immutable blobs | Configure legal holds and time-based retention policies to store blob data in a WORM (Write Once, Read Many) state. Blobs stored immutably can be read, but cannot be modified or deleted for the duration of the retention interval. For more information, see [Store business-critical blob data with immutable storage](immutable-storage-overview.md). | - | | Require secure transfer (HTTPS) to the storage account | When you require secure transfer for a storage account, all requests to the storage account must be made over HTTPS. Any requests made over HTTP are rejected. Microsoft recommends that you always require secure transfer for all of your storage accounts. For more information, see [Require secure transfer to ensure secure connections](../common/storage-require-secure-transfer.md). | - | | Limit shared access signature (SAS) tokens to HTTPS connections only | Requiring HTTPS when a client uses a SAS token to access blob data helps to minimize the risk of eavesdropping. For more information, see [Grant limited access to Azure Storage resources using shared access signatures (SAS)](../common/storage-sas-overview.md). | - |
+| Disallow cross-tenant object replication | By default, an authorized user is permitted to configure an object replication policy where the source account is in one Azure AD tenant and the destination account is in a different tenant. Disallow cross-tenant object replication to require that the source and destination accounts participating in an object replication policy are in the same tenant. For more information, see [Prevent object replication across Azure Active Directory tenants](object-replication-prevent-cross-tenant-policies.md). | - |
## Identity and access management
Microsoft Defender for Cloud periodically analyzes the security state of your Az
| Recommendation | Comments | Defender for Cloud | |-|-|--|
-| Track how requests are authorized | Enable Azure Storage logging to track how each request made against Azure Storage was authorized. The logs indicate whether a request was made anonymously, by using an OAuth 2.0 token, by using Shared Key, or by using a shared access signature (SAS). For more information, see [Monitoring Azure Blob Storage with Azure Monitor](monitor-blob-storage.md) or [Azure Storage analytics logging with Classic Monitoring](../common/storage-analytics-logging.md). | - |
+| Track how requests are authorized | Enable logging for Azure Storage to track how requests to the service are authorized. The logs indicate whether a request was made anonymously, by using an OAuth 2.0 token, by using Shared Key, or by using a shared access signature (SAS). For more information, see [Monitoring Azure Blob Storage with Azure Monitor](monitor-blob-storage.md) or [Azure Storage analytics logging with Classic Monitoring](../common/storage-analytics-logging.md). | - |
| Set up alerts in Azure Monitor | Configure log alerts to evaluate resources logs at a set frequency and fire an alert based on the results. For more information, see [Log alerts in Azure Monitor](../../azure-monitor/alerts/alerts-unified-log.md). | - | ## Next steps
storage Classic Account Migrate https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/storage/common/classic-account-migrate.md
Previously updated : 03/27/2023 Last updated : 04/06/2023
To list classic storage accounts in your subscription with PowerShell, run the f
Get-AzResource -ResourceType Microsoft.ClassicStorage/storageAccounts ```
-# [Azure CLI](#tab/azure-cli)
+
-To list classic storage accounts in your subscription with Azure CLI, run the following command:
+## Migrate a classic storage account
-```azurecli
-$ az resource list \
- --resource-type Microsoft.ClassicStorage/storageAccounts \
- --query "[].{resource_type:type, name:name}" \
- --output table
-```
+The process of migrating a classic storage account involves four steps:
-
+1. **Validate**. During the Validation phase, Azure checks the storage account to ensure that it can be migrated.
+1. **Prepare**. In the Prepare phase, Azure creates a new general-purpose v1 storage account and alerts you to any problems that may have occurred. The new account is created in a new resource group in the same region as your classic account.
-## Migrate a classic storage account
+ At this point your classic storage account still exists. If there are any problems reported, you can correct them or abort the process.
+
+1. **Check manually**. It's a good idea to make a manual check of the new storage account to make sure that the output is as you expect.
+1. **Commit or abort**. If you are satisfied that the migration has been successful, then you can commit the migration. Committing the migration permanently deletes the classic storage account.
+
+ If there are any problems with the migration, then you can abort the migration at this point. If you choose to abort, the new resource group and new storage account are deleted. Your classic account remains available. You can address any problems and attempt the migration again.
+
+For more information about the migration process, see [Understand storage account migration from the classic deployment model to Azure Resource Manager](classic-account-migration-process.md)
+
+You can migrate a classic storage account to the Azure Resource Manager deployment model with the Azure portal or PowerShell.
+
+# [Portal](#tab/azure-portal)
To migrate a classic storage account to the Azure Resource Manager deployment model with the Azure portal: 1. Navigate to your classic storage account in the Azure portal.
-1. In the **Settings** section, click **Migrate to ARM**.
-1. Click on **Validate** to determine migration feasibility.
+1. In the **Settings** section, select **Migrate to ARM**.
+1. Select **Validate** to determine migration feasibility.
:::image type="content" source="./media/classic-account-migrate/validate-storage-account.png" alt-text="Screenshot showing how to migrate your classic storage account to Azure Resource Manager." lightbox="./media/classic-account-migrate/validate-storage-account.png":::
-1. After a successful validation, click on **Prepare** button to simulate the migration.
+1. After a successful validation, select **Prepare** button to simulate the migration.
> [!IMPORTANT] > There may be a delay of a few minutes after validation is complete before the Prepare button is enabled.
To migrate a classic storage account to the Azure Resource Manager deployment mo
1. If you're not satisfied with the results of the migration, select **Abort** to delete the new storage account and resource group. You can then address any problems and try again. 1. When you're ready to commit, type **yes** to confirm, then select **Commit** to complete the migration.
+# [PowerShell](#tab/azure-powershell)
+
+To migrate a classic storage account to the Azure Resource Manager deployment model with PowerShell, you'll need to use the Azure PowerShell Service Management module. To learn how to install this module, see [Install and configure the Azure PowerShell Service Management module](/powershell/azure/servicemanagement/install-azure-ps#checking-the-version-of-azure-powershell). The key steps are included here for convenience.
+
+> [!NOTE]
+> The cmdlets in the Azure Service Management module are for managing legacy Azure resources that use Service Management APIs, including classic storage accounts. This module includes the commands needed to migrate a classic storage account to Azure Resource Manager.
+>
+> To manage Azure Resource Manager resources, we recommend that you use the Az PowerShell module. The Az module replaces the deprecated AzureRM module. For more information about moving from the AzureRM module to the Az module, see [Migrate Azure PowerShell scripts from AzureRM to Az](/powershell/azure/migrate-from-azurerm-to-az).
+
+First, install PowerShellGet if you do not already have it installed. For more information on how to install PowerShellGet, see [Installing PowerShellGet](/powershell/scripting/gallery/installing-psget#installing-the-latest-version-of-powershellget). After you install PowerShellGet, close and reopen the PowerShell console.
+
+Next, install the Azure Service Management module. If you also have the AzureRM module installed, you'll need to include the `-AllowClobber` parameter, as described in [Step 2: Install Azure PowerShell](/powershell/azure/servicemanagement/install-azure-ps#step-2-install-azure-powershell). After the installation is complete, import the Azure Service Management module.
+
+```azurepowershell
+Install-Module -Name Azure -AllowClobber
+Import-Module -Name Azure
+```
+
+Log into your account by running [Add-AzureAccount](/powershell/module/servicemanagement/azure/add-azureaccount). Then call [Select-AzureSubscription](/powershell/module/servicemanagement/azure/select-azuresubscription) to set your current subscription. Remember to replace the placeholder values in brackets with your subscription name:
+
+```azurepowershell
+Add-AzureAccount
+Select-AzureSubscription -SubscriptionName <subscription-name>
+```
+
+To validate that the account is ready for migration, call the [Move-AzureStorageAccount](/powershell/module/servicemanagement/azure/move-azurestorageaccount) command. Remember to replace the placeholder values in brackets with the name of your classic storage account:
+
+```azurepowershell
+$accountName = "<storage-account>"
+Move-AzureStorageAccount -Validate -StorageAccountName $accountName
+```
+
+Next, prepare the account for migration:
+
+```azurepowershell
+Move-AzureStorageAccount -Prepare -StorageAccountName $accountName
+```
+
+Check the configuration for the prepared storage account with either Azure PowerShell or the Azure portal. If you're not ready for migration, use the following command to revert your account to its previous state:
+
+```azurepowershell
+Move-AzureStorageAccount -Abort -StorageAccountName $accountName
+```
+
+Finally, when you are satisfied with the prepared configuration, move forward with the migration and commit the resources with the following command:
+
+```azurepowershell
+Move-AzureStorageAccount -Commit -StorageAccountName $accountName
+```
+++ ### Locate and delete disk artifacts in a classic account Classic storage accounts may contain classic (unmanaged) disks, virtual machine images, and operating system (OS) images. To migrate the account, you may need to delete these artifacts first.
storage Classic Account Migration Process https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/storage/common/classic-account-migration-process.md
There are four steps to the migration process, as shown in the following diagram
If there are any problems with the migration, then you can abort the migration at this point. If you choose to abort, the new resource group and new storage account are deleted. Your classic account remains available. You can address any problems and attempt the migration again. > [!NOTE]
-> The operations described in the following sections are all idempotent. If you have a problem other than an unsupported feature or a configuration error, retry the prepare, abort, or commit operation. Azure tries the action again.
+> The operations described in the following sections are all idempotent. If you have a problem other than an unsupported feature or a configuration error, retry the prepare, abort, or commit operation.
### Validate
To revert your changes to the classic deployment model, you can choose to abort
After you are satisfied that your classic storage account has been migrated successfully, you can commit the migration. Committing the migration deletes your classic storage account. Your data is now available only in the newly migrated account in the Resource Manager deployment model. > [!NOTE]
-> Committing the migration is an idempotent operation. If it fails, retry the operation. If it continues to fail, create a support ticket or ask a question on [Microsoft Q&A](/answers/https://docsupdatetracker.net/index.html)
+> Committing the migration is an idempotent operation. If it fails, retry the operation. If it continues to fail, create a support ticket or ask a question on [Microsoft Q&A](/answers/https://docsupdatetracker.net/index.html).
## After the migration
storage Elastic San Connect Linux https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/storage/elastic-san/elastic-san-connect-linux.md
When using multiple sessions, generally, you should aggregate them with Multipat
To create iSCSI connections from a Linux client, install the iSCSI initiator package. The exact command may vary depending on your distribution, and you should consult their documentation if necessary.
-As an example, with Ubuntu you'd use `sudo apt -y install open-iscsi` and with Red Hat Enterprise Linux (RHEL) you'd use `sudo yum install iscsi-initiator-utils -y`.
+As an example, with Ubuntu you'd use `sudo apt install open-iscsi`, with SUSE Linux Enterprise Server (SLES) you'd use `sudo zypper install open-iscsi` and with Red Hat Enterprise Linux (RHEL) you'd use `sudo yum install iscsi-initiator-utils`.
#### Multipath I/O - for multi-session connectivity
-Install the Multipath I/O package for your Linux distribution. The installation will vary based on your distribution, and you should consult their documentation. As an example, on Ubuntu the command would be `sudo apt install multipath-tools` and for RHEL the command would be `sudo yum install device-mapper-multipath`.
+Install the Multipath I/O package for your Linux distribution. The installation will vary based on your distribution, and you should consult their documentation. As an example, on Ubuntu the command would be `sudo apt install multipath-tools`, for SLES the command would be `sudo zypper install multipath-tools` and for RHEL the command would be `sudo yum install device-mapper-multipath`.
Once you've installed the package, check if **/etc/multipath.conf** exists. If **/etc/multipath.conf** doesn't exist, create an empty file and use the settings in the following example for a general configuration. As an example, `mpathconf --enable` will create **/etc/multipath.conf** on RHEL. You'll need to make some modifications to **/etc/multipath.conf**. You'll need to add the devices section in the following example, and the defaults section in the following example sets some defaults are generally applicable. If you need to make any other specific configurations, such as excluding volumes from the multipath topology, see the man page for multipath.conf.
-```
+```config
defaults { user_friendly_names yes # To create ΓÇÿmpathnΓÇÖ names for multipath devices path_grouping_policy multibus # To place all the paths in one priority group
devices {
} ```
-After creating or modifying the file, restart Multipath I/O. On Ubuntu, the command is `sudo systemctl restart multipath-tools.service` and on RHEL the command is `sudo systemctl restart multipathd`.
+After creating or modifying the file, restart Multipath I/O. On Ubuntu, the command is `sudo systemctl restart multipath-tools.service` and on RHEL and SLES the command is `sudo systemctl restart multipathd`.
### Gather information
To establish persistent iSCSI connections, modify **node.startup** in **/etc/isc
Replace **yourTargetIQN**, **yourTargetPortalHostName**, and **yourTargetPortalPort** with the values you kept, then run the following commands from your compute client to connect an Elastic SAN volume.
-```
-iscsiadm -m node --targetname yourTargetIQN --portal yourTargetPortalHostName:yourTargetPortalPort -o new
+```bash
+sudo iscsiadm -m node --targetname yourTargetIQN --portal yourTargetPortalHostName:yourTargetPortalPort -o new
-iscsiadm -m node --targetname yourTargetIQN -p yourTargetPortalHostName:yourTargetPortalPort -l
+sudo iscsiadm -m node --targetname yourTargetIQN -p yourTargetPortalHostName:yourTargetPortalPort -l
``` Then, get the session ID and create as many sessions as needed with the session ID. To get the session ID, run `iscsiadm -m session` and you should see output similar to the following:
-```
+```output
tcp:[15] <name>:port,-1 <iqn> tcp:[18] <name>:port,-1 <i