-* A Linux VM (for the test we use CentosOS based machine).

-```console

-yum install -y sssd sssd-tools sssd-ldap openldap-clients

-```console

-ldapsearch -H ldaps://contoso.com -x \

-```console

-> ldapsearch -H ldaps://contoso.com -x \

-```console

-vi /etc/sssd/sssd.conf

-```bash

-```console

-chmod 600 /etc/sssd/sssd.conf

-```console

-sss_obfuscate --domain default

-```console

-service sssd start

-```console

-authconfig --enablesssd --enablesssdauth --enablemkhomedir --updateall

-```console

-systemctl restart sssd

-```console

-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 **federatedIdpMfaBehavior** setting is an evolved version of the **SupportsMfa** property of the [Set-MsolDomainFederationSettings MSOnline v1 PowerShell cmdlet](/powershell/module/msonline/set-msoldomainfederationsettings).

- - If you select **Pass-through authentication** option button, 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**.

-| March | 99.568% | 99.998% | |

-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).

- 

-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:

-Azure AD supports 2 types of roles definitions:

-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.

-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).

-description: Assign Azure AD roles to role-assignable groups in the Azure portal, PowerShell, or Graph API.

-This section describes how an IT admin can assign Azure Active Directory (Azure AD) role to an Azure AD group.

-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.

-1. Sign in to the [Azure portal](https://portal.azure.com).

-1. Select **Azure Active Directory** > **Roles and administrators** and select the role you want to assign.

-1. On the ***role name*** page, select > **Add assignment**.

- 

-1. Select the group. Only the groups that can be assigned to Azure AD roles are displayed.

- [](./media/groups-assign-role/eligible-groups.png#lightbox)

-1. Select **Add**.

-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).

-### Create a group that can be assigned to role

-### Get the role definition for the role you want to assign

-### Create a group that can be assigned Azure AD role

-Use the [Create group](/graph/api/group-post-groups) API to create a group.

-### Get the role definition

-Use the [List unifiedRoleDefinitions](/graph/api/rbacapplication-list-roledefinitions) API to get a role definition.

-Use the [Create unifiedRoleAssignment](/graph/api/rbacapplication-post-roleassignments) API to assign the role.

- "principalId": "<Object Id of Group>",

-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.

-description: Learn how to create a role-assignable group in Azure AD. Manage Azure roles in the Azure portal, PowerShell, or Graph API.

-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).

- [](./media/groups-create-eligible/new-group.png#<lightbox>)

-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.

- [](./media/groups-create-eligible/eligible-switch.png#<lightbox>)

- [](./media/groups-create-eligible/specify-members.png#<lightbox>)

-1. After the members and owners are specified, select **Create**.

- [](./media/groups-create-eligible/create-button.png#<lightbox>)

-The group is created with any roles you might have assigned to it.

-### Create a group that can be assigned to role

-### Create a role-assignable group 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).

-# 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

-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.

- 

-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.

- 

-## 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

- 

- 

- 

- 

- 

- 

- 

-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.

-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/).

-* 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.

-[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].

-> [!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.

-az aks create --resource-group myResourceGroup --name myAKSCluster --no-uptime-sla

-# Create a new AKS cluster in the Paid tier

-az aks create --resource-group myResourceGroup --name myAKSCluster --uptime-sla

-# Sample output for --no-uptime-sla

- "name": "Basic",

-# Sample output for --uptime-sla

- "tier": "Paid"

-## Update the tier of an existing cluster

-az aks update --resource-group myResourceGroup --name myAKSCluster --no-uptime-sla

-az aks update --resource-group myResourceGroup --name myAKSCluster --uptime-sla

-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.

- "tier": "Paid"

-> [Transform and protect a published API](transform-api.md)

-> [App Service Environment v3 Networking](networking.md)

-| | |

-> [Learn more about using Terraform in Azure](/azure/developer/terraform/)

-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).

-description: This article provides an overview of the Azure Application Gateway multi-site support.

-> 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.

-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.

-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.

->[!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.

-> 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.

-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.

-* 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).

-Application Gateway supports multiple applications each listening on different ports, but this scenario requires the applications to accept traffic on non-standard ports.

-|[WAF v2 custom rules](scripts/waf-custom-rules-powershell.md)|Creates an Application Gateway Web Application Firewall v2 with custom rules.|

-| [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.|

-# Tutorial: Protect your application gateway with Azure DDoS Protection Standard

-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.

-> 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 Standard is enabled at the virtual network where the resource you want to protect reside.

- :::image type="content" source="./media/tutorial-protect-application-gateway/enable-ddos-vnet.png" alt-text="Screenshot of ddos protection.":::

-> [Configure an application gateway with TLS termination using the Azure portal](create-ssl-portal.md)

- * 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).

-> [Frequently Asked Questions](faq.yml)

-* To find other useful Azure Automation runbooks, see [Use runbooks and modules in Azure Automation](automation-runbook-gallery.md).

-* To trigger a runbook from an alert, see [Use an alert to trigger an Azure Automation runbook](automation-create-alert-triggered-runbook.md).

-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).

-1. The client VM used for testing should be *in the same region* as your Redis cache instance.

-1. Make sure the client VM you use has *at least as much compute and bandwidth* as the cache being tested.

-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. 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.

- > [!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.

-## Redis-benchmark utility

-**Redis-benchmark** documentation can be [found here](https://redis.io/docs/reference/optimization/benchmarks/).

-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).

-> The **maxmemory-reserved** and **maxfragmentationmemory-reserved** settings are available only for Standard and Premium caches.

- - 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.

-* Enterprise Flash, which uses both volatile and non-volatile memory (NVMe or SSD) to store data.

- | **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*. |

- Set **Clustering policy** to **Enterprise** for a non-clustered cache. For more information on choosing **Clustering policy**, see [Clustering Policy](#clustering-policy).

- > 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.

- >

- > [!NOTE]

-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.

-> [!div class="nextstepaction"]

-> [Create an ASP.NET web app that uses an Azure Cache for Redis.](./cache-web-app-howto.md)

-| Durable Functions | [Supported](durable/durable-functions-overview.md) | [Supported (public preview)](https://github.com/microsoft/durabletask-dotnet#usage-with-azure-functions) |

-## Use managed identity for AzureWebJobsStorage (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 (Preview)](./functions-reference.md#connecting-to-host-storage-with-an-identity-preview).

-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:

-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).

-Identity-based connections are supported by the following components:

-| Host-required storage ("AzureWebJobsStorage") - Preview | All | [Connecting to host storage with an identity](#connecting-to-host-storage-with-an-identity-preview) |

-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.

-# [Functions host storage (preview)](#tab/azurewebjobsstorage)

-| 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. |

-Additional options may be supported for a given connection type. Please refer to the documentation for the component making the connection.

-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:

-#### Connecting to host storage with an identity (Preview)

-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.

-* [Azure in your datacenter](https://azure.microsoft.com/overview/business-apps-on-azure/)

-This article explains how to review TrackAvailability() test results in the Azure portal and query the data using Log Analytics.

-> - [Azure subscription](https://azure.microsoft.com/free) and user account with the ability to create and delete resources

-* [Learn more about Container insights](../containers/container-insights-overview.md).

- curl -X POST 'https://<location>.monitoring.azure.com/<resourceId>/metrics' \

-* [Learn more about SQL Insights (preview)](/azure/azure-sql/database/sql-insights-overview).

-description: Sample Azure Resource Graph queries for Azure Monitor showing use of resource types and tables to access Azure Monitor related resources and properties.

-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).

-description: Describes recent terminology changes made to Azure monitoring services.

-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.

-## 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.

-## 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.

-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).

-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.

-[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**.

-[Management solutions](/previous-versions/azure/azure-monitor/insights/solutions) have been renamed to _monitoring solutions_, which better describes their functionality.

-## 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 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 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:

-[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.

-* [Learn more about action groups](../visualize/workbooks-overview.md).

-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).

-```

-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. |

-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|[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|

-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|

-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|

-## February 2023

-

-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.|

-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|

-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.|

-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|[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|

-Containers|[Configure Container insights cost optimization data collection rules]()|New article on preview of cost optimization settings.|

-## January 2023

-

-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.|

-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.|

-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.|

-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|

-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|[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|

-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

-

-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.|

-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.|

-Visualizations|[Creating an Azure Workbook](visualize/workbooks-create-workbook.md)|added Tutorial - resource centric logs queries in workbooks|

-## November 2022

-

-

-

-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.|

-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.|

-Autoscale|[Understand autoscale settings](autoscale/autoscale-understanding-settings.md)|Refresh and update|

-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|[Migrate from diagnostic settings storage retention to Azure Storage lifecycle management](essentials/migrate-to-azure-storage-lifecycle-policy.md)|Deprecation note added|

-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|[Azure Monitor Log Analytics API Overview](logs/api/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.|

-

-## October 2022

-

-

-

-|Sub-service| 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.|

-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.|

-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|

-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.|

-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|[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. |

-Visualizations|[Retrieve legacy Application Insights workbooks](./visualize/workbooks-retrieve-legacy-workbooks.md)|New article about how to access legacy workbooks in the Azure portal.|

-|[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).|

-|[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.|

-### Application insights

-|[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.|

-|[Java Profiler for Azure Monitor Application Insights](./app/java-standalone-profiler.md)|Our new Java Profiler was announced at Ignite. Read all about it!|

-|[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.|

-|[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

-|[Structure of transformation in Azure Monitor (preview)](./essentials/data-collection-transformations-structure.md)|New KQL functions supported.|

-### Virtual Machines

-|[Access deprecated Troubleshooting guides in Azure Workbooks](./visualize/workbooks-access-troubleshooting-guide.md)|New article: Access deprecated Troubleshooting guides in Azure Workbooks.|

-## August 2022

-|[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.|

-|[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

-|[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.|

-|[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.|

-|[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

-|[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|

-|[Monitor an Azure Kubernetes Service (AKS) cluster deployed](containers/container-insights-enable-existing-clusters.md)|Added section on using private link with Container insights.|

-|[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.|

-|[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

-|[Sources of data in Azure Monitor](data-sources.md)|Updated with Azure Monitor agent and Logs ingestion API.|

-|[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 Alerts Overview](alerts/alerts-overview.md)|Updated the logic for the time to resolve behavior in stateful log alerts.

-|[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.

-| [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.|

-|[Enable Container insights](containers/container-insights-onboard.md)|All Container insights content updated for new support of managed identity authentication using Azure Monitor agent.|

-|[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.|

-|[How to Migrate from Diagnostic Settings Storage Retention to Azure Storage Lifecycle Policy](essentials/migrate-to-azure-storage-lifecycle-policy.md)|New article.|

-|[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.

-### Virtual Machines

-|[What is VM insights?](vm/vminsights-overview.md)|All VM insights content updated for new support of Azure Monitor agent.

-## June 2022

-| [Tutorial - Editing Data Collection Rules](essentials/data-collection-rule-edit.md) | New article|

-| [Application Insights logging with .NET](app/ilogger.md) | Connection string sample code has been added.|

-| [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.|

-| [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.|

-| [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).|

-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

-| [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 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 |

-| [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. |

-| [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. |

-| [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. |

-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)

-| [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 |

-| [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 |

-| [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. |

-### Virtual Machines

-| [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 |

-For more information about the linter, see [Use Bicep linter](./linter.md).

- - [Microsoft.Insights/autoscaleSettings](/azure/templates/microsoft.insights/autoscalesettings?tabs=bicep)

-

-* To view the operations for a resource provider, see [Azure REST API](/rest/api/).

-* 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).

-To learn about the template syntax, 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).

-* To define parameters in template, see [Authoring templates](./syntax.md#parameters).

-* For a list of the available template functions, see [ARM template functions](template-functions.md).

-> [Build a serverless real-time app with authentication](./signalr-tutorial-authenticate-azure-functions.md)

-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.

-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>

-|Topology |Basic network features |

-|Connectivity to a BM over ExpressRoute gateway |Yes|

-|Connectivity from on-premises to a BM in a spoke VNet over VPN gateway| Yes |

-|Connectivity over Virtual WAN (VWAN)| No |

-|Features |Basic network features |

-description: Make job-level preparation tasks to minimize data transfer to Azure Batch compute nodes, and release tasks for node cleanup at job completion.

-# Create tasks to prepare and complete jobs 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.

-## What are job preparation and release tasks?

-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.

-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.

-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.

-> 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

-Job preparation and job release tasks are a good fit for the following situations:

-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.

-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.

-> [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.

-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.

-> 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.

-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 prep 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).

-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.

-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.

-// 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

-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:

-1. Runs the job preparation task, which first writes the node ID to a text file in a node's "shared" directory.

-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.

-Output from the sample application is similar to the following:

-```

-> 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.

-### Inspect job preparation and release tasks in the Azure portal

-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.

-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).

-Set up continuous integration (CI) using the **Configure** button on the **Publish** screen. For more information, see [Azure Pipelines documentation](/azure/devops/pipelines).

-* 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).

-* [Learn more about Anomaly Detector API service](https://go.microsoft.com/fwlink/?linkid=2080698&clcid=0x409)

-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.

-* [Authentication](authentication.md)

-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.

-Early media is not supported by a web-based client.

-> [View log streams from the Azure portal](log-streaming.md)

-### <a name="tcp"></a>TCP (preview)

-> 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).

-> [Log storage and monitoring options in Azure Container Apps](log-monitoring.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 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)

-> [!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 "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`.

-## Example

-[azure-cli]: /cli/azure

-> [Tutorial: Create a container image for deployment to Azure Container Instances](./container-instances-tutorial-prepare-app.md)

-[az-keyvault-secret-set]: /cli/azure/keyvault/secret#az_keyvault_secret_set

-| 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. |

-| noReuse | Hash will not be generated. Object's domain label can't be reused within resource group, subscription, or tenant. |

-* Learn more about [Conditional Access policy components](../active-directory/conditional-access/concept-conditional-access-policies.md).

-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.

-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.

-A very simple code samples using the `LeaseCollectionPrefix` attribute in C#, would look like this:

-using Microsoft.Azure.Documents;

- collectionName: "Items",

- ConnectionStringSetting = "CosmosDBConnection",

- LeaseCollectionName = "leases",

- LeaseCollectionPrefix = "emails")]IReadOnlyList<Document> documents,

- collectionName: "Items",

- ConnectionStringSetting = "CosmosDBConnection",

- LeaseCollectionName = "leases",

- LeaseCollectionPrefix = "materialized")]IReadOnlyList<Document> documents,

-And for JavaScript, you can apply the configuration on the `function.json` file, with the `leaseCollectionPrefix` attribute:

- "leaseCollectionName": "leases",

- "connectionStringSetting": "CosmosDBConnection",

- "collectionName": "Items",

- "leaseCollectionPrefix": "emails"

- "leaseCollectionName": "leases",

- "connectionStringSetting": "CosmosDBConnection",

- "collectionName": "Items",

- "leaseCollectionPrefix": "materialized"

-1. Verify the `ConnectionStringSetting` attribute and that it references a setting that exists in your Azure function app.

-1. Verify that the `databaseName` and `collectionName` values exist in your Azure Cosmos DB account.

-1. If you don't specify a `LeaseCollectionName/leaseCollectionName` 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.

-* Note: you need concatenated or if you've more than two dependency activities, for instance,

-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.

-| [Multiple changes to identity recommendations](#multiple-changes-to-identity-recommendations) | April 2023 |

-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:

-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**:

- | **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 (`/`).|

-1. On **Catalogs** for the dev center, verify that your catalog appears. If the connection is successful, **Status** is **Connected**.

-1. On the Create key vault page provide the following information:

-1. In the **Add catalog** pane, enter the following information, and then select **Add**.

- | Name | Value |

- | **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*|

-1. Confirm that the catalog is successfully added by checking your Azure portal notifications.

-> [!NOTE]

-> 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).

-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).

- - **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.

-

- 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.

-

- - 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.

-

-

-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*.

- > 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**.

- > 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).

-> [!div class="nextstepaction"]

-* 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/).

-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, next to **Azure: Logic Apps (Standard)**, select **Create New Project** (icon that shows a folder and lightning bolt).

-1. Provide a name for your workflow and press Enter. This example uses `Fabrikam-Stateful-Workflow` as the name.

-1. Provide a name for the resource group, and press Enter. This example uses `Fabrikam-Workflows-RG`.

-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**.

- 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.

- | **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 |

- 1. In the **Save Request** window, under **Request name**, provide a name for the request, for example, `Test workflow trigger`.

- 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.

- > If a run failed and a step in monitoring view shows the `400 Bad Request` error, this problem might result

-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.

-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.

-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).

-### Publish to a new Logic App (Standard) resource

-1. On the **Azure: Logic Apps (Standard)** pane toolbar, select **Deploy to Logic App**.

- 

- 

-1. To create your new **Logic App (Standard)** 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. In the Azure pane, next to **Azure: Logic Apps (Standard)**, select **Create Workflow** (icon for Azure Logic Apps).

-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. In the **Azure: Logic Apps (Standard)** pane, expand your subscription, which shows all the deployed logic apps for that subscription.

-tags: azure-resource-manager

-| EMV | Europay Mastercard Visa |

-description: Describes Microsoft's approach for using AI-generated content on Microsoft Learn

-# 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.

-description: Learn about Azure Route Server routing preference feature.

-# 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

-+ 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.

-1. In **Tools** > **NuGet Package Manager**, select **Manage NuGet Packages for Solution...**.

- 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.

-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.

-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. The fourth query demonstrates facets, which can be used to structure a faceted navigation structure.

-Press F5 to rebuild the app and run the program in its entirety.

-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.

-> [!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.

- ```json

- {

- "SearchServiceName": "https://<YOUR-SEARCH-SERVICE-NAME>.search.windows.net",

- "SearchServiceQueryApiKey": "<YOUR-SEARCH-SERVICE-QUERY-API-KEY>"

- }

- ```

-In this step, create models that represent the schema of the hotels-search-index.

-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.

-string token = GetAccessToken(

- tenantId,

- webApplicationId,

- clientApplicationId,

- "urn:ietf:wg:oauth:2.0:oob");

-...

-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;

-}

-fc.ClaimsRetrieval += (o, e) =>

- return GetAccessToken(e.AzureActiveDirectoryMetadata);

-...

-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;

-}

-|[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 |

-| 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 |

-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.

-| 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). | - |

-| 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). | - |

-# [Azure CLI](#tab/azure-cli)

-To list classic storage accounts in your subscription with Azure CLI, run the following command:

-```azurecli

-$ az resource list \

- --resource-type Microsoft.ClassicStorage/storageAccounts \

- --query "[].{resource_type:type, name:name}" \

- --output table

-```

-## Migrate a classic storage account

-1. In the **Settings** section, click **Migrate to ARM**.

-1. Click on **Validate** to determine migration feasibility.

-1. After a successful validation, click on **Prepare** button to simulate the migration.

-> 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.

-> 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)

-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`.

-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`.

-```

-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`.

-```

-iscsiadm -m node --targetname yourTargetIQN --portal yourTargetPortalHostName:yourTargetPortalPort -o new

-iscsiadm -m node --targetname yourTargetIQN -p yourTargetPortalHostName:yourTargetPortalPort -l

-```