- > For Workday scenario, please provide "WID" of the user in Workday.

-1. If you have access to multiple tenants, use the **Directory + subscription** filter :::image type="icon" source="./media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to select the tenant in which you want to register an application.

-#Customer intent: As a tenant admin, I want to walk through the B2B invitation workflow so that I can understand how to add a guest user in the portal, and understand the end user experience.

-# Quickstart: Add guest users to your directory in the Azure portal

-You can invite anyone to collaborate with your organization by adding them to your directory as a guest user. Then you can either send an invitation email that contains a redemption link or send a direct link to an app you want to share. Guest users can sign in with their own work, school, or social identities. Along with this quickstart, you can learn more about adding guest users [in the Azure portal](add-users-administrator.md), via [PowerShell](b2b-quickstart-invite-powershell.md), or [in bulk](tutorial-bulk-invite.md).

-In this quickstart, you'll add a new guest user to your Azure AD directory via the Azure portal, send an invitation, and see what the guest user's invitation redemption process looks like.

-To complete the scenario in this tutorial, you need:

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

-2. In the left pane, select **Azure Active Directory**.

-3. Under **Manage**, select **Users**.

-4. Select **New guest user**.

- 

-5. On the **New user** page, select **Invite user** and then add the guest user's information.

- - **Directory role**: If you require Azure AD administrative permissions for the user, you can add them to an Azure AD role.

-6. Select **Invite** to automatically send the invitation to the guest user. A notification appears in the upper right with the message **Successfully invited user**.

-7. After you send the invitation, the user account is automatically added to the directory as a guest.

-## Assign an app to the guest user

-Add the Salesforce app to your test tenant and assign the test guest user to the app.

-1. Sign in to the Azure portal as an Azure AD administrator.

-2. In the left pane, select **Enterprise applications**.

-3. Select **New application**.

-4. Under **Add from the gallery**, search for **Salesforce**, and then select it.

- 

-5. Select **Add**.

-6. Under **Manage**, select **Single sign-on**, and under **Single Sign-on Mode**, select **Password-based Sign-on**, and click **Save**.

-7. Under **Manage**, select **Users and groups** > **Add user** > **Users and groups**.

-8. Use the search box to search for the test user (if necessary) and select the test user in the list. Then click **Select**.

-9. Select **Assign**.

-1. Sign in to your test guest user's email account.

-2. In your inbox, find the "You're invited" email.

-3. In the email body, select **Get Started**. A **Review permissions** page opens in the browser.

- 

-4. Select **Accept**. The Access Panel opens, which lists the applications the guest user can access.

-When no longer needed, delete the test guest user and the test app.

-1. Sign in to the Azure portal as an Azure AD administrator.

-2. In the left pane, select **Azure Active Directory**.

-3. Under **Manage**, select **Enterprise applications**.

-4. Open the application **Salesforce**, and then select **Delete**.

-5. In the left pane, select **Azure Active Directory**.

-6. Under **Manage**, select **Users**.

-7. Select the test user, and then select **Delete user**.

-In this tutorial, you created a guest user in the Azure portal, and sent an invitation to share apps. Then you viewed the redemption process from the guest user's perspective and verified that the app appeared on the guest user's Access Panel. To learn more about adding guest users for collaboration, see [Add Azure Active Directory B2B collaboration users in the Azure portal](add-users-administrator.md).

-5. Use the guidance shared below to map phone number attribute values from Azure AD to Workday.

- | WorkphoneLandlineCountryCodeName | [Three-letter ISO 3166-1 country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3) | Constant or expression mapping whose output is a three letter country code. |

- | WorkphoneLandlineCountryCodeNumber | [International country calling code](https://en.wikipedia.org/wiki/List_of_country_calling_codes) | Constant or expression mapping whose output is a valid country code (without the + sign). |

- | WorkphoneLandlineNumber | Full phone number including the area code | Map to *telephoneNumber* attribute. Use regex to remove whitespace, brackets and country code. See example below. |

- | WorkphoneMobileNumber | Full phone number including the area code | Map to *mobile* attribute. Use regex to remove whitespace, brackets and country code. See example below. |

- **Reference regex expressions - Example 1**

- Use the below regular expression, if phone number in Azure AD is set using the format required for Self Service Password Reset (SSPR). <br>

- Example: if the phone number value is +1 1112223333 -> then the regex expression will output 1112223333

- ```C#

- Replace([telephoneNumber], , "\\+(?<isdCode>\\d* )(?<phoneNumber>\\d{10})", , "${phoneNumber}", , )

- ```

- **Reference regex expressions - Example 2**

- Use the below regular expression, if phone number in Azure AD is set using the format (XXX) XXX-XXXX. <br>

- Example: if the phone number value is (111) 222-3333 -> then the regex expression will output 1112223333

- ```C#

- Replace([mobile], , "[()\\s-]+", , "", , )

- ```

-> By default when you turn on the provisioning service, it will initiate provisioning operations for all users in scope. If there are errors in the mapping or Workday data issues, then the provisioning job might fail and go into the quarantine state. To avoid this, as a best practice, we recommend configuring **Source Object Scope** filter and testing your attribute mappings with a few test users before launching the full sync for all users. Once you have verified that the mappings work and are giving you the desired results, then you can either remove the filter or gradually expand it to include more users.

-## April

-> Rotating your certificates using `az aks rotate-certs` will recreate all of your nodes and their OS Disks and can cause up to 30 minutes of downtime for your AKS cluster.

-You're able to configure the maximum number of pods per node at cluster deployment time or as you add new node pools. If you deploy with the Azure CLI or with a Resource Manager template, you can set the maximum pods per node value as high as 250.

-* **Azure portal**: You can't change the maximum number of pods per node when you deploy a cluster with the Azure portal. Azure CNI networking clusters are limited to 110 pods per node when you deploy using the Azure portal.

-* The AKS cluster must use the Standard SKU load balancer to use multiple node pools, the feature is not supported with Basic SKU load balancers.

-* Azure Network Policy is not supported.

-* Kube-proxy is designed for a single contiguous CIDR and optimizes rules based on that value. When using multiple non-contiguous ranges, these optimizations cannot occur. See this [K.E.P.](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2450-Remove-knowledge-of-pod-cluster-CIDR-from-iptables-rules) and the documentation for the [`--cluster-cidr` `kube-proxy` argument](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/) for more details. In clusters configured with Azure CNI, `kube-proxy` will be configured with the subnet of the first node pool at cluster creation.

- * The node pool version cannot be greater than the control `major.minor.patch` version.

- * You cannot downgrade the control plane or a node pool Kubernetes version.

- * If a node pool Kubernetes version is not specified, behavior depends on the client being used. Declaration in Resource Manager templates falls back to the existing version defined for the node pool if used, if none is set the control plane version is used to fall back on.

- * You can either upgrade or scale a control plane or a node pool at a given time, you cannot submit multiple operations on a single control plane or node pool resource simultaneously.

-Associating a system node pool with an existing capacity reservation group can be done using [az aks create][az-aks-create] command. If the capacity reservation group specified does not exist, then a warning is issued and the cluster gets created without any capacity reservation group association.

-* Container Images on the FIPS nodes have not been assessed for FIPS compliance.

-The following example output shows the *fipsnp* node pool is FIPS-enabled and *nodepool1* is not.

-Deploy this template using the [az deployment group create][az-deployment-group-create] command, as shown in the following example. You are prompted for the existing AKS cluster name and location:

-AKS nodes do not require their own public IP addresses for communication. However, scenarios may require nodes in a node pool to receive their own dedicated public IP addresses. A common scenario is for gaming workloads, where a console needs to make a direct connection to a cloud virtual machine to minimize hops. This scenario can be achieved on AKS by using Node Public IP.

-1. Next select 'Authentication / Authorization' (under 'Settings').

-1. Turn on the App Service Authentication feature.

-1. Set the Action to take when request is not authenticated dropdown to "Log in with Azure Active Directory".

-1. Under 'Authentication Providers', choose ΓÇÿAzure Active DirectoryΓÇÖ.

-1. Choose ΓÇÿAdvancedΓÇÖ from the Management Mode switch.

-1. Paste the Backend application's [Application] Client ID (from Azure AD B2C) into the ΓÇÿClient IDΓÇÖ box

-1. Click 'Show Secret' and paste the Backend application's client secret into the appropriate box.

-1. Select OK, which takes you back to the identity provider selection blade/screen.

-1. Leave [Token Store](../app-service/overview-authentication-authorization.md#token-store) enabled under advanced settings (default).

- > You added additional defense-in-depth security in EasyAuth by configuring the 'Login With Azure AD' option to handle unauthenticated requests. Be aware that this will change the unauthorized request behavior between the Backend Function App and Frontend SPA as EasyAuth will issue a 302 redirect to Azure Active Directory instead of a 401 Not Authorized response, we will correct this by using API Management later.

-1. Close the 'Authentication / Authorization' blade

-* [Manage your first API](import-and-publish.md).

-| [!INCLUDE [Create app service step 1](<./includes/quickstart-python/create-app-service-visual-studio-code-1.md>)] | :::image type="content" source="./media/quickstart-python/create-app-service-visual-studio-code-1-240px.png" alt-text="A Screenshot of the Azure Tools icon in the left toolbar of VS Code." lightbox="./media/quickstart-python/create-app-service-visual-studio-code-1.png"::: |

-| [!INCLUDE [Create app service step 2](<./includes/quickstart-python/create-app-service-visual-studio-code-2.md>)] | :::image type="content" source="./media/quickstart-python/create-app-service-visual-studio-code-2-240px.png" alt-text="A screenshot of the App Service section of Azure Tools extension and the context menu used to create a new web app." lightbox="./media/quickstart-python/create-app-service-visual-studio-code-2.png"::: |

-| [!INCLUDE [Create app service step 4](<./includes/quickstart-python/create-app-service-visual-studio-code-3.md>)] | :::image type="content" source="./media/quickstart-python/create-app-service-visual-studio-code-3-240px.png" alt-text="A screenshot of dialog box used to enter the name of the new web app in Visual Studio Code." lightbox="./media/quickstart-python/create-app-service-visual-studio-code-3.png"::: |

-| [!INCLUDE [Create app service step 5](<./includes/quickstart-python/create-app-service-visual-studio-code-4.md>)] | :::image type="content" source="./media/quickstart-python/create-app-service-visual-studio-code-4-240px.png" alt-text="A screenshot of the dialog box in VS Code used to select the runtime for the new web app." lightbox="./media/quickstart-python/create-app-service-visual-studio-code-4.png"::: |

-| [!INCLUDE [Create app service step 6](<./includes/quickstart-python/create-app-service-visual-studio-code-5.md>)] | :::image type="content" source="./media/quickstart-python/create-app-service-visual-studio-code-5-240px.png" alt-text="A screenshot of the dialog in VS Code used to select the App Service plan for the new web app." lightbox="./media/quickstart-python/create-app-service-visual-studio-code-5.png"::: |

-To deploy a web app from VS Code, you must have the [Azure Tools extension pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-node-azure-pack) installed and be signed into Azure from VS Code.

-> [!div class="nextstepaction"]

-> [Download Azure Tools extension pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-node-azure-pack)

-| Instructions | Screenshot |

-|:-|--:|

-| [!INCLUDE [VS Code deploy step 1](<./includes/quickstart-python/deploy-visual-studio-code-1.md>)] | :::image type="content" source="./media/quickstart-python/deploy-visual-studio-code-1-240px.png" alt-text="A screenshot of the location of the Azure Tools icon in the left toolbar of VS Code." lightbox="./media/quickstart-python/deploy-visual-studio-code-1.png"::: |

-| [!INCLUDE [VS Code deploy step 2](<./includes/quickstart-python/deploy-visual-studio-code-2.md>)] | :::image type="content" source="./media/quickstart-python/deploy-visual-studio-code-2-240px.png" alt-text="A screenshot of the context menu of an App Service and the deploy to web app menu option." lightbox="./media/quickstart-python/deploy-visual-studio-code-2.png"::: |

-| [!INCLUDE [VS Code deploy step 3](<./includes/quickstart-python/deploy-visual-studio-code-3.md>)] | :::image type="content" source="./media/quickstart-python/deploy-visual-studio-code-3-240px.png" alt-text="A screenshot dialog in VS Code used to choose the app to deploy." lightbox="./media/quickstart-python/deploy-visual-studio-code-3.png"::: |

-| [!INCLUDE [VS Code deploy step 4](<./includes/quickstart-python/deploy-visual-studio-code-4.md>)] | :::image type="content" source="./media/quickstart-python/deploy-visual-studio-code-4-240px.png" alt-text="A screenshot of a dialog box in VS Code asking if you want to update your workspace to run build commands." lightbox="./media/quickstart-python/deploy-visual-studio-code-4.png"::: |

-| [!INCLUDE [VS Code deploy step 5](<./includes/quickstart-python/deploy-visual-studio-code-5.md>)] | :::image type="content" source="./media/quickstart-python/deploy-visual-studio-code-5-240px.png" alt-text="A screenshot showing the confirmation dialog when the app code has been deployed to Azure." lightbox="./media/quickstart-python/deploy-visual-studio-code-5.png"::: |

-The cookie-based session affinity feature is useful when you want to keep a user session on the same server. By using gateway-managed cookies, the Application Gateway can direct subsequent traffic from a user session to the same server for processing. This is important in cases where session state is saved locally on the server for a user session.

-* [Log in to Azure CLI](/cli/azure/authenticate-azure-cli) using the identity (user or service principal) that you want to use for connecting your cluster to Azure Arc.

- * The identity used needs to at least have 'Read' and 'Write' permissions on the Azure Arc-enabled Kubernetes resource type (`Microsoft.Kubernetes/connectedClusters`).

- * The [Kubernetes Cluster - Azure Arc Onboarding built-in role](../../role-based-access-control/built-in-roles.md#kubernetes-clusterazure-arc-onboarding) is useful for at-scale onboarding as it has the granular permissions required to only connect clusters to Azure Arc. This role doesn't have the permissions to update, delete, or modify any other clusters or other Azure resources.

-## Meet network requirements

-> [!IMPORTANT]

-> Azure Arc agents require the following outbound URLs on `https://:443` to function.

-> For `*.servicebus.windows.net`, websockets need to be enabled for outbound access on firewall and proxy.

-| Endpoint (DNS) | Description |

-| -- | - |

-| `https://management.azure.com` (for Azure Cloud), `https://management.usgovcloudapi.net` (for Azure US Government) | Required for the agent to connect to Azure and register the cluster. |

-| `https://<region>.dp.kubernetesconfiguration.azure.com` (for Azure Cloud), `https://<region>.dp.kubernetesconfiguration.azure.us` (for Azure US Government) | Data plane endpoint for the agent to push status and fetch configuration information. |

-| `https://login.microsoftonline.com`, `https://<region>.login.microsoft.com`, `login.windows.net` (for Azure Cloud), `https://login.microsoftonline.us`, `<region>.login.microsoftonline.us` (for Azure US Government) | Required to fetch and update Azure Resource Manager tokens. |

-| `https://mcr.microsoft.com`, `https://*.data.mcr.microsoft.com` | Required to pull container images for Azure Arc agents. |

-| `https://gbl.his.arc.azure.com` (for Azure Cloud), `https://gbl.his.arc.azure.us` (for Azure US Government) | Required to get the regional endpoint for pulling system-assigned Managed Identity certificates. |

-| `https://*.his.arc.azure.com` (for Azure Cloud), `https://usgv.his.arc.azure.us` (for Azure US Government) | Required to pull system-assigned Managed Identity certificates. |

-|`*.servicebus.windows.net`, `guestnotificationservice.azure.com`, `*.guestnotificationservice.azure.com`, `sts.windows.net` | For [Cluster Connect](cluster-connect.md) and for [Custom Location](custom-locations.md) based scenarios. |

-|`https://k8connecthelm.azureedge.net` | `az connectedk8s connect` uses Helm 3 to deploy Azure Arc agents on the Kubernetes cluster. This endpoint is needed for Helm client download to facilitate deployment of the agent helm chart. |

-## Generate an onboarding script and configuration file from Azure Portal

-After you have successfully installed the agent and configure it to connect to Azure Arc-enabled servers, go to the Azure portal to verify that the servers in your Organizational Unit have successfully connected. View your machines in the [Azure portal](https://aka.ms/hybridmachineportal).

-It's often not practical in a real-world cloud app to avoid storing some form of state for a user session, but some approaches impact performance and scalability more than others. If you have to store state, the best solution is to keep the amount of state small and store it in cookies. If that isn't feasible, the next best solution is to use ASP.NET session state with a provider for distributed, in-memory cache. The worst solution from a performance and scalability standpoint is to use a database backed session state provider. This topic provides guidance on using the ASP.NET Session State Provider for Azure Cache for Redis. For information on other session state options, see [ASP.NET Session State options](#aspnet-session-state-options).

-> If you are using the clustering feature from the premium tier, you must use [RedisSessionStateProvider](https://www.nuget.org/packages/Microsoft.Web.RedisSessionStateProvider) 2.0.1 or higher or an exception is thrown. Moving to 2.0.1 or higher is a breaking change; for more information, see [v2.0.0 Breaking Change Details](https://github.com/Azure/aspnet-redis-providers/wiki/v2.0.0-Breaking-Change-Details). At the time of this article update, the current version of this package is 2.2.3.

-The Redis Session State Provider NuGet package has a dependency on the StackExchange.Redis package. If the StackExchange.Redis package is not present in your project, it is installed.

- * The non-TLS port is disabled by default for new caches. Specify true for this setting to use the TLS port. For more information about enabling the non-TLS port, see the [Access Ports](cache-configure.md#access-ports) section in the [Configure a cache](cache-configure.md) topic.

-* **throwOnError** ΓÇô true if you want an exception to be thrown if there is a failure, or false if you want the operation to fail silently. You can check for a failure by checking the static Microsoft.Web.Redis.RedisSessionStateProvider.LastException property. The default is true.

-* **retryTimeoutInMilliseconds** ΓÇô Operations that fail are retried during this interval, specified in milliseconds. The first retry occurs after 20 milliseconds, and then retries occur every second until the retryTimeoutInMilliseconds interval expires. Immediately after this interval, the operation is retried one final time. If the operation still fails, the exception is thrown back to the caller, depending on the throwOnError setting. The default value is 0, which means no retries.

-* **applicationName** ΓÇô Keys are stored in redis as `{<Application Name>_<Session ID>}_Data`. This naming scheme enables multiple applications to share the same Redis instance. This parameter is optional and if you do not provide it a default value is used.

-* **connectionTimeoutInMilliseconds** ΓÇô This setting allows you to override the connectTimeout setting in the StackExchange.Redis client. If not specified, the default connectTimeout setting of 5000 is used. For more information, see [StackExchange.Redis configuration model](https://go.microsoft.com/fwlink/?LinkId=398705).

-* **operationTimeoutInMilliseconds** ΓÇô This setting allows you to override the syncTimeout setting in the StackExchange.Redis client. If not specified, the default syncTimeout setting of 1000 is used. For more information, see [StackExchange.Redis configuration model](https://go.microsoft.com/fwlink/?LinkId=398705).

-DonΓÇÖt forget to comment out the standard InProc session state provider section in your web.config.

-Once these steps are performed, your application is configured to use the Azure Cache for Redis Session State Provider. When you use session state in your application, it is stored in an Azure Cache for Redis instance.

-* In Memory Session State Provider - This provider stores the Session State in memory. The benefit of using this provider is it is simple and fast. However you cannot scale your Web Apps if you are using in memory provider since it is not distributed.

-* Sql Server Session State Provider - This provider stores the Session State in Sql Server. Use this provider if you want to store the Session state in persistent storage. You can scale your Web App but using Sql Server for Session has a performance impact on your Web App. You can also use this provider with an [In-Memory OLTP configuration](/archive/blogs/sqlserverstorageengine/asp-net-session-state-with-sql-server-in-memory-oltp) to help improve performance.

-Select **Activity log** to view actions done to your cache. You can also use filtering to expand this view to include other resources. For more information on working with audit logs, see [Audit operations with Resource Manager](../azure-monitor/essentials/activity-log.md). For more information on monitoring Azure Cache for Redis events, see [Operations and alerts](cache-how-to-monitor.md#operations-and-alerts).

-Geo-replication links together two Premium Azure Cache for Redis instances and creates a data replication relationship. These cache instances are usually located in different Azure regions, though they aren't required to. One instance acts as the primary, and the other as the secondary. The primary handles read and write requests and propagates changes to the secondary. This process continues until the link between the two instances is removed.

-1. To link two caches together for geo-replication, fist click **Geo-replication** from the Resource menu of the cache that you intend to be the primary linked cache. Next, click **Add cache replication link** from **Geo-replication** on the left.

-1. To remove the link between two caches and stop geo-replication, click **Unlink caches** from the **Geo-replication** on the left .

- - If the VNets are in different regions, geo-replication using VNet peering is supported, but a client VM in VNet 1 (region 1) is not able to access the cache in VNet 2 (region 2) using it's 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 to use a VPN Gateway VNet-to-VNet connection.

-Replication is incremental, asynchronous, and continuous and the time taken isn't much different from the latency across regions. Under certain circumstances, the secondary cache can be required to do a full sync of the data from the primary. The replication time in this case is depends on a number of factors like: load on the primary cache, available network bandwidth, and inter-region latency. We have found replication time for a full 53-GB geo-replicated pair can be anywhere between 5 to 10 minutes.

-When using geo-replication, data from the primary linked cache is replicated to the secondary linked cache. There's no charge for the data transfer if the two linked caches are in the same region. If the two linked caches are in different regions, the data transfer charge is the network egress cost of data moving across either region. For more information, see [Bandwidth Pricing Details](https://azure.microsoft.com/pricing/details/bandwidth/).

-Automatic failover across Azure regions isn't supported for geo-replicated caches. In a disaster-recovery scenario, customers should bring up the entire application stack in a coordinated manner in their backup region. Letting individual application components decide when to switch to their backups on their own can negatively impact performance.

-One of the key benefits of Redis is that it's a very low-latency store. If the customer's main application is in a different region than its cache, the added round-trip time would have a noticeable impact on performance. For this reason, we avoid failing over automatically because of transient availability issues.

-Metrics for Azure Cache for Redis instances are collected using the Redis [INFO](https://redis.io/commands/info) command. Metrics are collected approximately twice per minute and automatically stored for 30 days so they can be displayed in the metrics charts and evaluated by alert rules.

-<a name="view-cache-metrics"></a>

-

-

-

-

-For more information on working with metrics using Azure Monitor, see [Overview of metrics in Microsoft Azure](../azure-monitor/data-platform.md).

-<a name="enable-cache-diagnostics"></a>

-

-<a name="operations-and-alerts"></a>

-

-<!--

-## Activity Logs

-Activity logs provide insight into the operations that completed on your Azure Cache for Redis instances. It was previously known as "audit logs" or "operational logs". Using activity logs, you can determine the "what, who, and when" for any write operations (PUT, POST, DELETE) taken on your Azure Cache for Redis instances.

-> [!NOTE]

-> Activity logs do not include read (GET) operations.

->

-To view activity logs for your cache, select **Activity logs** from the **Resource menu**.

-For more information about Activity logs, see [Overview of the Azure Activity Log](../azure-monitor/essentials/platform-logs-overview.md).

- Once the cache is created, you connect to it and use it just like a non-clustered cache. Redis distributes the data throughout the Cache shards. If diagnostics is [enabled](cache-how-to-monitor.md#enable-cache-diagnostics), metrics are captured separately for each shard and can be [viewed](cache-how-to-monitor.md) in Azure Cache for Redis on the left.

-By default, a newly created ExpressRoute circuit doesn't do forced tunneling (advertisement of a default route, 0.0.0.0/0) on a virtual network. As a result, outbound internet connectivity is allowed directly from the virtual network. Client applications can connect to other Azure endpoints, which include an Azure Cache for Redis instance.

-#Customer intent: As a developer new to Azure Cache for Redis, I want to create an instance of Azure Cache for Redis Enterprise tier.

-> [!div class="nextstepaction"]

-| Data Service | 50 | 50 | 50 |

-| Elevation Service | 50 | 50 | 50 |

-| Render Service - Contour tiles, DEM tiles, Elevation tiles, Customer tiles, Traffic tiles and Static maps | 50 | 50 | 50 |

-| Render Service - Satellite tiles | 250 | 250 | 50 |

-| Route Service - Batch | 10 | 10 | 10 |

-| Search Service - Batch | 10 | 10 | 10 |

-| Spatial Service | 50 | 50 | 50 |

-az rest --method post --url /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.OperationalInsights/workspaces/<workspaceName>/alertsversion?api-version=2017-04-26-preview --body '{"scheduledQueryRulesEnabled": true}'

-Automatic web snippet injection allows you to enable [Application Insights Usage Experiences](usage-overview.md) and Browser Diagnostic Experiences with a simple configuration. It provides an easier alternative to manually adding the JavaScript snippet or NPM package to your JavaScript web code. For node server with configuration, set `enableAutoWebSnippetInjection` to `true` or alternatively set environment variable `APPLICATIONINSIGHTS_WEB_SNIPPET_ENABLED = true`. Automatic web snippet injection is available in Application Insights Node.js SDK version 2.3.0 or greater. See [Application Insights Node.js Github Readme](https://github.com/microsoft/ApplicationInsights-node.js#automatic-web-snippet-injectionpreview) for more information.

-# Tutorial: Ingestion-time transformations in Azure Monitor Logs (preview)

-[Ingestion-time transformations](ingestion-time-transformations.md) allow you to manipulate incoming data before it's stored in a Log Analytics workspace. You can add data filtering, parsing and extraction, and control the structure of the data that gets ingested.in

- TabelName_RST

-If you're in the global Azure cloud, and you delete a _published_ dashboard in the Azure portal, you can recover that dashboard within 14 days of the delete. If you're in an Azure Government cloud or the dashboard isn't published, you cannot recover it, and you must rebuild it. For more information about publishing a dashboard, see [Publish dashboard](azure-portal-dashboard-share-access.md#publish-a-dashboard). Follow these steps to recover a published dashboard:

-### managementGrouopResourceID example

- workspaceId: ((!empty(logAnalytics)) ? reference(logAnalytics, '2015-11-01-preview').customerId : json('null'))

- workspaceKey: ((!empty(logAnalytics)) ? listKeys(logAnalytics, '2015-11-01-preview').primarySharedKey : json('null'))

-For limits specific to Media Services v2 (legacy), see [Media Services v2 (legacy)](/media-services/previous/media-services-quotas-and-limitations)

-> | networksecuritygroups | Yes | Yes | Yes <br/><br/> Use [Azure Resource Mover](../../resource-mover/tutorial-move-region-virtual-machines.md) to move network security groups (NGSs). |

-The integer number that decides the width of the bucket combined with *datepart* argument. This represents the width of the datepart buckets from the origin time. **`This argument cannot be a negative integer value`**.

-* Unlimited paid Azure Video Indexer account (classic account).

- * To perform the connect to the ARM (Azure Resource Manager) action, you should have owner's permissions on the Azure Video Indexer account.

-* Azure Subscription.

-* User assigned managed identity (can be created along the flow).

-After the transition state ends, users will only be able to generate a valid access token through through ARM, making Azure RBAC the exclusive way to manage role-based access control on the account.

- 

- 

- * If you followed the steps the fields should be auto-populated, make sure to validate the eligible values.

- 

-When creating an Azure Video Indexer (formerly Azure Video Analyzer for Media) account, you can choose a free trial account (where you get a certain number of free indexing minutes) or a paid option (where you're not limited by the quota). With a free trial, Azure Video Indexer provides up to 600 minutes of free indexing to users and up to 2400 minutes of free indexing to users that subscribe to the Video Analyzer API on the [developer portal](https://aka.ms/avam-dev-portal). With the paid options, Azure Video Indexer offers two types of accounts: classic accounts(General Availability), and ARM-based accounts(Public Preview). Main difference between the two is account management platform. While classic accounts are built on the API Management, ARM-based accounts management is built on Azure, enables to apply access control to all services with role-based access control (Azure RBAC) natively.

- 

- 

- 

- 

- 

- 

-

-> Azure VMware Solution vCenter will be available in global search but will NOT be available in the list of vCenters for ARc for VMware.

-1. Locate the arc appliance VM, which should be in the resource pool that was configured during onboarding.

-This article describes how to back up Azure Database for PostgreSQL server.

-The following table summarizes the supported operating systems when backing up Windows Azure VMs.

-<a name="tvm-backup">Trusted Launch VM</a> | Backup supported. <br><br> Backup of Trusted Launch VM is supported through [Enhanced policy](backup-azure-vms-enhanced-policy.md). You can enable backup through [Recovery Services vault](./backup-azure-arm-vms-prepare.md), [VM Manage blade](./backup-during-vm-creation.md#start-a-backup-after-creating-the-vm), and [Create VM blade](backup-during-vm-creation.md#create-a-vm-with-backup-configured). <br><br> **Feature details** <br> <ul><li> Backup is supported in all regions where Trusted Launch VM is available. </li><li> Configurations of Backup, Alerts, and Monitoring for Trusted Launch VM are currently not supported through Backup center. </li><li> Migration of an existing [Generation 2](../virtual-machines/generation-2.md) VM (protected with Azure Backup) to Trusted Launch VM is currently not supported. Learn about how to [create a Trusted Launch VM](../virtual-machines/trusted-launch-portal.md?tabs=portal#deploy-a-trusted-vm). </li></ul>

-[red]: ./media/backup-support-matrix/red.png

-This functionality is not supported in our current Generally Available (GA) stable release. Check out QnA Maker managed to test out this functionality.

- * Update dependencies

-| `1.7.0-amd64-preview` | |

-The following table details the available Communication Services packages along with corresponding reference documentation:

-<!--note that this table also exists here and should be synced: https://github.com/Azure/Communication/blob/master/README.md -->

-| Area | JavaScript | .NET | Python | Java SE | iOS | Android | Other |

-| -- | - | - | | - | -- | -- | |

-| Azure Resource Manager | - | [NuGet](https://www.nuget.org/packages/Azure.ResourceManager.Communication) | [PyPi](https://pypi.org/project/azure-mgmt-communication/) | - | - | - | [Go via GitHub](https://github.com/Azure/azure-sdk-for-go/releases/tag/v46.3.0) |

-| Common | [npm](https://www.npmjs.com/package/@azure/communication-common) | [NuGet](https://www.nuget.org/packages/Azure.Communication.Common/) | N/A | [Maven](https://search.maven.org/search?q=a:azure-communication-common) | [GitHub](https://github.com/Azure/azure-sdk-for-ios/releases) | [Maven](https://search.maven.org/artifact/com.azure.android/azure-communication-common) | - |

-| Identity | [npm](https://www.npmjs.com/package/@azure/communication-identity) | [NuGet](https://www.nuget.org/packages/Azure.Communication.Identity) | [PyPi](https://pypi.org/project/azure-communication-identity/) | [Maven](https://search.maven.org/search?q=a:azure-communication-identity) | - | - | - |

-| Phone numbers | [npm](https://www.npmjs.com/package/@azure/communication-phone-numbers) | [NuGet](https://www.nuget.org/packages/Azure.Communication.phonenumbers) | [PyPi](https://pypi.org/project/azure-communication-phonenumbers/) | [Maven](https://search.maven.org/search?q=a:azure-communication-phonenumbers) | - | - | - |

-| Chat | [npm](https://www.npmjs.com/package/@azure/communication-chat) | [NuGet](https://www.nuget.org/packages/Azure.Communication.Chat) | [PyPi](https://pypi.org/project/azure-communication-chat/) | [Maven](https://search.maven.org/search?q=a:azure-communication-chat) | [GitHub](https://github.com/Azure/azure-sdk-for-ios/releases) | [Maven](https://search.maven.org/search?q=a:azure-communication-chat) | - |

-| SMS | [npm](https://www.npmjs.com/package/@azure/communication-sms) | [NuGet](https://www.nuget.org/packages/Azure.Communication.Sms) | [PyPi](https://pypi.org/project/azure-communication-sms/) | [Maven](https://search.maven.org/artifact/com.azure/azure-communication-sms) | - | - | - |

-| Calling | [npm](https://www.npmjs.com/package/@azure/communication-calling) | - | - | - | [GitHub](https://github.com/Azure/Communication/releases) ([docs](/objectivec/communication-services/calling/)) | [Maven](https://search.maven.org/artifact/com.azure.android/azure-communication-calling/) | - |

-| Reference Documentation | [docs](https://azure.github.io/azure-sdk-for-js/communication.html) | [docs](https://azure.github.io/azure-sdk-for-net/communication.html) | - | [docs](http://azure.github.io/azure-sdk-for-java/communication.html) | - | - | - |

-### Job submission flow

-2. The Job is classified and a [JobClassified Event][job_classified_event] is sent via Event Grid.

- :::image type="content" source="../media/router/acs-router-job-submission.png" alt-text="Diagram of job submission.":::

-A Worker is the supply available to handle a Job. Each worker registers with one or more queues to receive jobs.

-A real-world example is an agent in a call center.

-### Worker registration flow

-1. When your Worker is ready to take on work, you can register the worker via the Job Router SDK.

-2. Job Router then sends a [WorkerRegistered Event][worker_registered_event]

- :::image type="content" source="../media/router/acs-router-worker-registration.png" alt-text="Diagram of worker registration.":::

-A Queue is an ordered list of jobs, that are waiting to be served by a worker. Workers register with a queue to receive work from it.

-[worker-scoring]: ../../how-tos/router-sdk/customize-worker-scoring.md

-<a name="connection-security-encyrption"></a>

- The SFTP-SSH connector supports both private key authentication and password authentication. However, the SFTP-SSH connector supports *only* these private key formats, encryption algorithms, fingerprints, and key exchange algorithms:

- * **Key exchange algorithms**: Review [Key Exchange Method - SSH.NET](https://github.com/sshnet/SSH.NET#key-exchange-method).

-## How SFTP-SSH triggers work

-<a name="polling-behavior"></a>

-### Polling behavior

-SFTP-SSH triggers poll the SFTP file system and look for any file that changed since the last poll. Some tools let you preserve the timestamp when the files change. In these cases, you have to disable this feature so your trigger can work. Here are some common settings:

-| SFTP client | Action |

-|-|--|

-| Winscp | Go to **Options** > **Preferences** > **Transfer** > **Edit** > **Preserve timestamp** > **Disable** |

-| FileZilla | Go to **Transfer** > **Preserve timestamps of transferred files** > **Disable** |

-|||

-When a trigger finds a new file, the trigger checks that the new file is complete, and not partially written. For example, a file might have changes in progress when the trigger checks the file server. To avoid returning a partially written file, the trigger notes the timestamp for the file that has recent changes, but doesn't immediately return that file. The trigger returns the file only when polling the server again. Sometimes, this behavior might cause a delay that is up to twice the trigger's polling interval.

-<a name="trigger-recurrence-shift-drift"></a>

-## Trigger recurrence shift and drift (daylight saving time)

-Recurring connection-based triggers where you need to create a connection first, such as the managed SFTP-SSH trigger, differ from built-in triggers that run natively in Azure Logic Apps, such as the [Recurrence trigger](../connectors/connectors-native-recurrence.md). In recurring connection-based triggers, the recurrence schedule isn't the only driver that controls execution, and the time zone only determines the initial start time. Subsequent runs depend on the recurrence schedule, the last trigger execution, *and* other factors that might cause run times to drift or produce unexpected behavior. For example, unexpected behavior can include failure to maintain the specified schedule when daylight saving time (DST) starts and ends.

-To make sure that the recurrence time doesn't shift when DST takes effect, manually adjust the recurrence. That way, your workflow continues to run at the expected time or specified start time. Otherwise, the start time shifts one hour forward when DST starts and one hour backward when DST ends. For more information, see [Recurrence for connection-based triggers](../connectors/apis-list.md#recurrence-for-connection-based-triggers).

-1. If you haven't done so already, [download the latest PuTTY Generator (puttygen.exe) tool](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html), and then launch the tool.

-1. On this screen, select **Load**.

- 

- 

-1. Save the private key file with the `.pem` file name extension.

-## Considerations

-This section describes considerations to review when you use this connector's triggers and actions.

-<a name="different-folders-trigger-processing-file-storage"></a>

-### Use different SFTP folders for file upload and processing

-On your SFTP server, use separate folders for storing uploaded files and for the trigger to monitor those files for processing. Otherwise, the trigger won't fire and behaves unpredictably, for example, skipping a random number of files that the trigger processes. However, this requirement means that you need a way to move files between those folders.

-If this trigger problem happens, remove the files from the folder that the trigger monitors, and use a different folder to store the uploaded files.

-<a name="create-file"></a>

-### Create file

-To create a file on your SFTP server, you can use the SFTP-SSH **Create file** action. When this action creates the file, the Logic Apps service also automatically calls your SFTP server to get the file's metadata. However, if you move the newly created file before the Logic Apps service can make the call to get the metadata, you get a `404` error message, `'A reference was made to a file or folder which does not exist'`. To skip reading the file's metadata after file creation, follow the steps to [add and set the **Get all file metadata** property to **No**](#file-does-not-exist).

-> [!IMPORTANT]

-> If you use chunking with SFTP-SSH operations that create files on your SFTP server,

-> these operations create temporary `.partial` and `.lock` files. These files help

-> the operations use chunking. Don't remove or change these files. Otherwise,

-> the file operations fail. When the operations finish, they delete the temporary files.

-## Current supported Dapr version

-Azure Container Apps supports Dapr version 1.4.2.

-Version upgrades are handled transparently by Azure Container Apps. You can find the current version via the Azure portal and the CLI. See [known limitations](#limitations) around versioning.

-The optional [failureThreshold](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) setting defines the number of attempts Kubernetes tries if the probe if execution fails. Attempts that exceed the `failureThreshold` amount cause different results for each probe. Refer to [Configure Liveness, Readiness and Startup Probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) for details.

-| `minReplicas` | Minimum number of replicas running for your container app. | 0 | 1 | 10 |

-> [!IMPORTANT]

-> Replica quantities are a target amount, not a guarantee. Even if you set `maxReplicas` to `1`, there is no assurance of thread safety.

-In the following sections, use the Azure CLI to deploy an Azure NAT gateway in the virtual network. For background, see [Tutorial: Create a NAT gateway using Azure CLI](../virtual-network/nat-gateway/tutorial-create-nat-gateway-cli.md).

-1. Go to template **Extract data from PDF**. Create a **New** connection to your source storage store or choose an existing connection. The source storage store is where you want to copy files from.

- :::image type="content" source="media/solution-template-extract-data-from-pdf/extract-data-from-pdf-1.png" alt-text="Screenshot of how to create a new connection or select an existing connection from a drop down menu to the source in template set up.":::

-2. Create a **New** connection to your destination storage store or choose an existing connection.

- :::image type="content" source="media/solution-template-extract-data-from-pdf/extract-data-from-pdf-2.png" alt-text="Screenshot of how to create a new connection or select existing connection from a drop down menu to Form Recognizer in template set up.":::

-## Steps to move existing Azure integration runtime to an Azure integration runtime in a managed virtual network

-[Learn about creating rules to disable findings from the integrated vulnerability assessment tool](defender-for-container-registries-usage.md#disable-specific-findings).

-> [Scan your images for vulnerabilities](defender-for-container-registries-usage.md)

-| Required roles and permissions: | ΓÇó To auto provision the required components, [Contributor](../role-based-access-control/built-in-roles.md#contributor), [Log Analytics Contributor](../role-based-access-control/built-in-roles.md#log-analytics-contributor), or [Azure Kubernetes Service Contributor Role](../role-based-access-control/built-in-roles.md#azure-kubernetes-service-contributor-role). See also the [permissions for each of the components](enable-data-collection.md?tabs=autoprovision-containers)<br> ΓÇó **Security admin** can dismiss alerts<br> ΓÇó **Security reader** can view vulnerability assessment findings<br> See also [Azure Container Registry roles and permissions](../container-registry/container-registry-roles.md) |

-Learn more in [Vulnerability assessment](defender-for-container-registries-usage.md).

-| Release state: | ΓÇó Defender profile is in preview<br> ΓÇó Azure Policy add-on: Generally available (GA) | ΓÇó Defender extension: Preview<br> ΓÇó Azure Policy extension: Preview |

-| Required roles and permissions (subscription-level): | [Owner](../role-based-access-control/built-in-roles.md#owner) or [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator) | [Owner](../role-based-access-control/built-in-roles.md#owner) |

-| Supported destinations: | The AKS Defender profile only supports [AKS clusters that have RBAC enabled](../aks/concepts-identity.md#kubernetes-rbac). | [Any Cloud Native Computing Foundation (CNCF) certified Kubernetes clusters](defender-for-containers-introduction.md?tabs=defender-for-container-arch-aks#microsoft-defender-for-containers-plan-availability) |

-* Azure Container Registry images - see [Use Microsoft Defender for container registries to scan your images for vulnerabilities](defender-for-container-registries-usage.md)

- - Microsoft Defender for Servers enabled on your subscription. Learn how to enable plans in the [Enable enhanced security features](enable-enhanced-security.md) article.

- - (Recommended) Use the auto provisioning process to install Azure Arc on all of your existing, and future EC2 instances managed by AWS Systems Manager (SSM) and using the SSM agent. Some Amazon Machine Images (AMIs) already have the SSM agent pre-installed. If that is the case, their AMI's are listed in [AMIs with SSM Agent preinstalled](https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-agent-technical-details.html#ami-preinstalled-agent). If your EC2 instances don't have the SSM Agent, you will need to install it using either of the following relevant instructions from Amazon:

- - To manually install Azure Arc on your existing and future EC2 instances, follow the instructions in the [EC2 instances should be connected to Azure Arc](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/231dee23-84db-44d2-bd9d-c32fbcfb42a3) recommendation.

- - Additional extensions should be enabled on the Arc-connected machines. These extensions are currently configured in the subscription level. It means that all the multicloud accounts and projects (from both AWS and GCP) under the same subscription will inherit the subscription settings with regards to these components.

-> [!Note]

-> Without the Arc agent, you will be unable to take advantage of Defender for server's value. The Arc agent can also be installed manually, and not by the auto-provisioning process.

- These extensions are currently configured as auto-provisioning settings on the subscription level. All GCP projects and AWS accounts under this subscription will inherit the subscription settings. Learn how to [configure auto-provisioning on your subscription](enable-data-collection.md#configure-auto-provisioning-for-agents-and-extensions-from-microsoft-defender-for-cloud).

-Azure Defender for container registries includes a vulnerability scanner to scan images in your Azure Container Registry registries. Learn how to scan your registries and remediate findings in [Use Azure Defender for container registries to scan your images for vulnerabilities](defender-for-container-registries-usage.md).

-Learn more in [Identify vulnerable container images in your CI/CD workflows](defender-for-container-registries-cicd.md).

-Learn more about this scanner in [Use Azure Defender for container registries to scan your images for vulnerabilities](defender-for-container-registries-usage.md).

-Learn more in [Disable specific findings for your container images](defender-for-container-registries-usage.md#disable-specific-findings) and [Disable specific findings for your virtual machines](remediate-vulnerability-findings-vm.md#disable-specific-findings).

-Learn more in [Use Microsoft Defender for Container to scan your images for vulnerabilities](defender-for-container-registries-usage.md).

-| Compliance | Docker CIS | VMs | GA | X | Log Analytics agent | Defender for Servers Plan 2 | |

-| - [Microsoft Defender for container registries scanning of images in CI/CD workflows](./defender-for-container-registries-cicd.md) ^{[3](#footnote3)} | Public Preview | Not Available | Not Available |

-The rest of this section walks you through these steps.

-To clean up after this quickstart, choose which resources you want to remove based on what you want to do next.

-* If you don't need your Azure Digital Twins instance anymore, you can delete it using the Azure portal.

-| **[Webair](https://www.webair.com/microsoft-express-route-partnership/)**| Megaport | New York |

-| [Packets per second](#packets) | Performance | CountPerSecond | Average | Packet count of ExpressRoute Gateway | roleInstance | No |

-| [BitsInPerSecond](#connectionbandwidth) | Traffic | BitsPerSecond | Average | Bits ingressing Azure per second | ConnectionName | No |

-| [BitsOutPerSecond](#connectionbandwidth) | Traffic | BitsPerSecond | Average | Bits egressing Azure per second | ConnectionName | No |

-### <a name = "cpu"></a>CPU Utilization - Split Instance

-### <a name = "packets"></a>Packets Per Second - Split by Instance

-### <a name = "advertisedroutes"></a>Count of Routes Advertised to Peer - Split by Instance

-### <a name = "learnedroutes"></a>Count of Routes Learned from Peer - Split by Instance

-### <a name = "frequency"></a>Frequency of Routes change - Split by Instance

-This metric shows the bandwidth usage for a specific connection to an ExpressRoute circuit.

-published. This cmdlet requires a 'Code Signing' certificate.

-$Cert = Get-ChildItem -Path cert:\LocalMachine\My | Where-Object {($_.Subject-eq "CN=mycert") }

-Protect-GuestConfigurationPackage -Path .\package\AuditWindowsService\AuditWindowsService.zip -Certificate $Cert -Verbose

-`/usr/local/share/ca-certificates/extra` on Linux machines. For the node to

-Search-AzGraph -Query "Resources | where type == 'microsoft.compute/virtualmachines' | extend JoinID = toupper(id), OSName = tostring(properties.osProfile.computerName), OSType = tostring(properties.storageProfile.osDisk.osType), VMSize = tostring(properties.hardwareProfile.vmSize) | join kind=leftouter( Resources | where type == 'microsoft.compute/virtualmachines/extensions' | extend VMId = toupper(substring(id, 0, indexof(id, '/extensions'))), ExtensionName = name ) on $left.JoinID == $right.VMId | summarize Extensions = make_list(ExtensionName) by id, OSName, OSType, VMSize | order by tolower(OSName) asc"

- * [Hive LLAP deep dive](https://community.cloudera.com/t5/Community-Articles/Hive-LLAP-deep-dive/ta-p/248893)

-| Windows 10 Pro |  | | |

-| Windows 10 Enterprise |  | | |

-| Windows 10 IoT Enterprise |  | | |

-| Windows Server 2019 |  | | |

-| Windows 10 Pro |  | | ¹ |

-| Windows 10 Enterprise |  | | ¹ |

-| Windows 10 IoT Enterprise |  | | ¹ |

-| Windows Server 2019 |  | | |

-7. In the **IP addresses** tab, under **Subnet name** select **default**.

-8. In the **Edit subnet** pane, under **Subnet name** enter **myBackendSubnet**.

-9. Select **Save**.

-10. Select the **Security** tab, or the **Next: Security** button at the bottom of the page.

-11. In the **Security** tab, in **BastionHost** select **Enable**.

-12. Enter or select the following information:

-13. Select the **Review + create** tab, or the blue **Review + create** button at the bottom of the page.

-14. Select **Create**.

-4. Select **Next: Frontend IP configuration** at the bottom of the page.

-5. In **Frontend IP configuration**, select **+ Add a frontend IP**.

- > In regions with [Availability Zones](../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json#availability-zones), you have the option to select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear. </br> For more information on availability zones, see [Availability zones overview](../availability-zones/az-overview.md).

-15. Select **Next: Backend pools** at the bottom of the page.

-22. Select the **Next: Inbound rules** button at the bottom of the page.

- > In this example we created a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed as it's optional isn't needed with the NAT gateway. For more information on Azure NAT gateway, see [What is Azure Virtual Network NAT?](../virtual-network/nat-gateway/nat-overview.md)

-8. Repeat steps 1 through seven to create the second virtual machine of the set. Replace the settings for the VM with the following information:

-8. Repeat steps 1 through seven to create the second virtual machine of the set. Replace the settings for the VM with the following information:

-5. Select **Use Bastion**.

-6. Enter the **Username** and **Password** you created when you created the virtual machine.

-7. Select **Connect**.

-8. Close the Bastion session with **myVM1**.

-9. Repeat steps 1 through eight for **myVM2**, **myVM3**, and **myVM4**.

-1. On the page that shows test details, select **Run** or **Run test**.

- :::image type="content" source="./media/quickstart-create-and-run-loadtest/run-test.png" alt-text="Screenshot that shows the button for running a load test." :::

-1. On the **Run** confirmation page, optionally modify the test details. Then, select **Run** to start the load test.

-1. On the page that shows test details, select **Run** or **Run test**.

-1. Select **Run** on the run summary page to start the load test. You'll then see the list of test runs.

- :::image type="content" source="./media/tutorial-identify-bottlenecks-azure-portal/test-run-list.png" alt-text="Screenshot that shows the run summary page." :::

-1. Return to the page that shows test run details and select **Rerun**. Then select **Run** on the run summary page.

-To prevent others from changing or deleting your logic app, you can use [Azure Resource Lock](../azure-resource-manager/management/lock-resources.md). This capability prevents others from changing or deleting production resources. For more information about connection security, review [Connection configuration in Azure Logic Apps](../connectors/apis-list.md#connection-configuration) and [Connection security and encryption](../connectors/apis-list.md#connection-security-encyrption).

-In the **Best model summary** section, **StackEnsemble** is considered the best model in the context of this experiment, based on the **Normalized root mean squared error** metric.

-1. Select **StackEnsemble** to open the model-specific page.

-Azure Migrate supports agentless dependency analysis by using Azure Migrate: Discovery and assessment.[Learn more](how-to-create-group-machine-dependencies-agentless.md) about how to perform agentless dependency analysis.

-Upon initial deployment, an Azure for MySQL server includes systems tables for time zone information, but these tables are not populated. The time zone tables can be populated by calling the `mysql.az_load_timezone` stored procedure from a tool like the MySQL command line or MySQL Workbench. Refer to the [Azure portal](howto-server-parameters.md#working-with-the-time-zone-parameter) or [Azure CLI](howto-configure-server-parameters-using-cli.md#working-with-the-time-zone-parameter) articles for how to call the stored procedure and set the global or session-level time zones.

-Password plugins such as "validate_password" and "caching_sha2_password" are not supported by the service.

-Many server parameters and settings can inadvertently degrade server performance or negate ACID properties of the MySQL server. To maintain the service integrity and SLA at a product level, this service does not expose multiple roles.

-The MySQL service does not allow direct access to the underlying file system. Some data manipulation commands are not supported.

-|**Authentication** | 1. Define a service principal. <br /> 2. Create a GitHub secret. |

- branches: [ master ]

- branches: [ master ]

- branches: [ master ]

- branches: [ master ]

- branches: [ master ]

- branches: [ master ]

- rayCast.EndPos = {0, 0, 1};

- rayCast.MaxHits = 10;

-| Parameter name | Description |

-| `defaultLanguageCode` | A string indicating the language to return. The service returns recognition results in a specified language. If this parameter is not specified, the default value is "en". <br/><br/>Supported languages are: <br/>*en* - English (default) <br/> *es* - Spanish <br/> *ja* - Japanese <br/> *pt* - Portuguese <br/> *zh* - Simplified Chinese|

-| `visualFeatures` | An array of strings indicating the visual feature types to return. Valid visual feature types include: <ul><li>*adult* - detects if the image is pornographic in nature (depicts nudity or a sex act), or is gory (depicts extreme violence or blood). Sexually suggestive content (also known as racy content) is also detected.</li><li>*brands* - detects various brands within an image, including the approximate location. The *brands* visual feature is only available in English.</li><li> *categories* - categorizes image content according to a taxonomy defined in the Cognitive Services [Computer Vision documentation](../cognitive-services/computer-vision/category-taxonomy.md). </li><li>*description* - describes the image content with a complete sentence in supported languages.</li><li>*faces* - detects if faces are present. If present, generates coordinates, gender and age.</li><li> *objects* - detects various objects within an image, including the approximate location. The *objects* visual feature is only available in English.</li><li> *tags* - tags the image with a detailed list of words related to the image content.</li></ul> Names of visual features are case-sensitive. Note that the *color* and *imageType* visual features have been deprecated, but this functionality could still be accessed via a [custom skill](./cognitive-search-custom-skill-interface.md).|

-| `image` | Complex Type. Currently only works with "/document/normalized_images" field, produced by the Azure Blob indexer when ```imageAction``` is set to a value other than ```none```. See the [sample](#sample-output) for more information.|

-<!-- ## Skill outputs

-| Output name | Description |

-| `categories` | Complex type that ... |

-| `tags` | Complex type that ... |

-| `description` | Complex type that ... |

-| `faces` | Complex type that ... |

-| `brands` | Complex type that ... | -->

- "description": "Extract image analysis.",

- "@odata.type": "#Microsoft.Skills.Vision.ImageAnalysisSkill",

- "context": "/document/normalized_images/*",

- "defaultLanguageCode": "en",

- "visualFeatures": [

- "tags",

- "categories",

- "description",

- "faces",

- "brands"

- ],

- "inputs": [

- {

- "name": "image",

- "source": "/document/normalized_images/*"

- }

- ],

- "outputs": [

- {

- "name": "categories"

- },

- {

- "name": "tags"

- },

- {

- "name": "description"

- },

- {

- "name": "faces"

- },

- {

- "name": "brands"

- }

- ]

-### Sample index (for only the categories, description, faces and tags fields)

-### Sample output field mapping (for the above index)

- "outputFieldMappings": [

- {

- "sourceFieldName": "/document/normalized_images/*/categories/*",

- "targetFieldName": "categories"

- },

- {

- "sourceFieldName": "/document/normalized_images/*/tags/*",

- "targetFieldName": "tags"

- },

- {

- "sourceFieldName": "/document/normalized_images/*/description",

- "targetFieldName": "description"

- },

- {

- "sourceFieldName": "/document/normalized_images/*/faces/*",

- "targetFieldName": "faces"

- },

- {

- "sourceFieldName": "/document/normalized_images/*/brands/*/name",

- "targetFieldName": "brands"

- }

-You can define output field mappings to lower-level properties, such as just landmarks or celebrities. In this case, make sure your index schema has a field to contain landmarks specifically.

- "outputFieldMappings": [

- {

- "sourceFieldName": "/document/normalized_images/*/categories/detail/celebrities/*",

- "targetFieldName": "celebrities"

- }

- "landmarks": [

- {

- "name": "Forbidden City",

- "confidence": 0.9978346

- }

- ]

- "requestId": "0dbec5ad-a3d3-4f7e-96b4-dfd57efe967d",

- "metadata": {

- "width": 1500,

- "height": 1000,

- "format": "Jpeg"

- },

-| `NotSupportedLanguage` | The language provided is not supported. |

-| `InvalidImageFormat` | Input data is not a valid image. |

-| `NotSupportedVisualFeature` | Specified feature type is not valid. |

-| `detectOrientation` | Enables autodetection of image orientation. <br/> Valid values: true / false.|

-| `defaultLanguageCode` | <p> Language code of the input text. Supported languages include: <br/> zh-Hans (ChineseSimplified) <br/> zh-Hant (ChineseTraditional) <br/>cs (Czech) <br/>da (Danish) <br/>nl (Dutch) <br/>en (English) <br/>fi (Finnish) <br/>fr (French) <br/> de (German) <br/>el (Greek) <br/> hu (Hungarian) <br/> it (Italian) <br/> ja (Japanese) <br/> ko (Korean) <br/> nb (Norwegian) <br/> pl (Polish) <br/> pt (Portuguese) <br/> ru (Russian) <br/> es (Spanish) <br/> sv (Swedish) <br/> tr (Turkish) <br/> ar (Arabic) <br/> ro (Romanian) <br/> sr-Cyrl (SerbianCyrillic) <br/> sr-Latn (SerbianLatin) <br/> sk (Slovak) <br/> unk (Unknown) <br/><br/> If the language code is unspecified or null, the language will be set to English. If the language is explicitly set to "unk", the language will be auto-detected. </p> |

-| `lineEnding` | The value to use between each detected line. Possible values: "Space", "CarriageReturn", "LineFeed". The default is "Space". |

-Previously, there was a parameter called "textExtractionAlgorithm" for specifying whether the skill should extract "printed" or "handwritten" text. This parameter is deprecated and no longer necessary as the latest Read API algorithm is capable of extracting both types of text at once. If your skill definition already includes this parameter, you do not need to remove it, but it will no longer be used and both types of text will be extracted going forward regardless of what it is set to.

-| `image` | Complex Type. Currently only works with "/document/normalized_images" field, produced by the Azure Blob indexer when ```imageAction``` is set to a value other than ```none```. See the [sample](#sample-output) for more information.|

-## Sample: Merging text extracted from embedded images with the content of the document.

-A common use case for Text Merger is the ability to merge the textual representation of images (text from an OCR skill, or the caption of an image) into the content field of a document.

-description: Migrate code to the Azure Search .NET SDK version 1.1 from older API versions. Learn what's new and what code changes are required.

-# Upgrade to Azure Search .NET SDK version 1.1

-If you're using version 1.0.2-preview or older of the [Azure Search .NET SDK](/dotnet/api/overview/azure/search), this article will help you upgrade your application to use version 1.1.

-For a more general walkthrough of the SDK including examples, see [How to use Azure Search from a .NET Application](search-howto-dotnet-sdk.md).

-> [!NOTE]

-> Once you upgrade to version 1.1, or if you're already using a version between 1.1 and 2.0-preview inclusive, you should upgrade to version 3. See [Upgrading to the Azure Search .NET SDK version 3](search-dotnet-sdk-migration.md) for instructions.

->

-First, update your NuGet reference for `Microsoft.Azure.Search` using either the NuGet Package Manager Console or by right-clicking on your project references and selecting "Manage NuGet Packages..." in Visual Studio.

-Once NuGet has downloaded the new packages and their dependencies, rebuild your project.

-If you were previously using version 1.0.0-preview, 1.0.1-preview, or 1.0.2-preview, the build should succeed and you're ready to go!

-If you were previously using version 0.13.0-preview or older, you should see build errors like the following:

-```output

-Program.cs(137,56,137,62): error CS0117: 'Microsoft.Azure.Search.Models.IndexBatch' does not contain a definition for 'Create'

-Program.cs(137,99,137,105): error CS0117: 'Microsoft.Azure.Search.Models.IndexAction' does not contain a definition for 'Create'

-Program.cs(146,41,146,54): error CS1061: 'Microsoft.Azure.Search.IndexBatchException' does not contain a definition for 'IndexResponse' and no extension method 'IndexResponse' accepting a first argument of type 'Microsoft.Azure.Search.IndexBatchException' could be found (are you missing a using directive or an assembly reference?)

-Program.cs(163,13,163,42): error CS0246: The type or namespace name 'DocumentSearchResponse' could not be found (are you missing a using directive or an assembly reference?)

-```

-The next step is to fix the build errors one by one. Most will require changing some class and method names that have been renamed in the SDK. [List of breaking changes in version 1.1](#ListOfChangesV1) contains a list of these name changes.

-If you're using custom classes to model your documents, and those classes have properties of non-nullable primitive types (for example, `int` or `bool` in C#), there is a bug fix in the 1.1 version of the SDK of which you should be aware. See [Bug fixes in version 1.1](#BugFixesV1) for more details.

-Finally, once you've fixed any build errors, you can make changes to your application to take advantage of new functionality if you wish.

-<a name="ListOfChangesV1"></a>

-## List of breaking changes in version 1.1

-The following list is ordered by the likelihood that the change will affect your application code.

-### IndexBatch and IndexAction changes

-`IndexBatch.Create` has been renamed to `IndexBatch.New` and no longer has a `params` argument. You can use `IndexBatch.New` for batches that mix different types of actions (merges, deletes, etc.). In addition, there are new static methods for creating batches where all the actions are the same: `Delete`, `Merge`, `MergeOrUpload`, and `Upload`.

-`IndexAction` no longer has public constructors and its properties are now immutable. You should use the new static methods for creating actions for different purposes: `Delete`, `Merge`, `MergeOrUpload`, and `Upload`. `IndexAction.Create` has been removed. If you used the overload that takes only a document, make sure to use `Upload` instead.

-#### Example

-If your code looks like this:

-```csharp

-var batch = IndexBatch.Create(documents.Select(doc => IndexAction.Create(doc)));

-indexClient.Documents.Index(batch);

-```

-You can change it to this to fix any build errors:

-```csharp

-var batch = IndexBatch.New(documents.Select(doc => IndexAction.Upload(doc)));

-indexClient.Documents.Index(batch);

-```

-If you want, you can further simplify it to this:

-```csharp

-var batch = IndexBatch.Upload(documents);

-indexClient.Documents.Index(batch);

-```

-### IndexBatchException changes

-The `IndexBatchException.IndexResponse` property has been renamed to `IndexingResults`, and its type is now `IList<IndexingResult>`.

-#### Example

-If your code looks like this:

-```csharp

-catch (IndexBatchException e)

-{

- Console.WriteLine(

- "Failed to index some of the documents: {0}",

- String.Join(", ", e.IndexResponse.Results.Where(r => !r.Succeeded).Select(r => r.Key)));

-}

-```

-You can change it to this to fix any build errors:

-```csharp

-catch (IndexBatchException e)

-{

- Console.WriteLine(

- "Failed to index some of the documents: {0}",

- String.Join(", ", e.IndexingResults.Where(r => !r.Succeeded).Select(r => r.Key)));

-}

-```

-<a name="OperationMethodChanges"></a>

-### Operation method changes

-Each operation in the Azure Search .NET SDK is exposed as a set of method overloads for synchronous and asynchronous callers. The signatures and factoring of these method overloads has changed in version 1.1.

-For example, the "Get Index Statistics" operation in older versions of the SDK exposed these signatures:

-In `IIndexOperations`:

-```csharp

-// Asynchronous operation with all parameters

-Task<IndexGetStatisticsResponse> GetStatisticsAsync(

- string indexName,

- CancellationToken cancellationToken);

-```

-In `IndexOperationsExtensions`:

-```csharp

-// Asynchronous operation with only required parameters

-public static Task<IndexGetStatisticsResponse> GetStatisticsAsync(

- this IIndexOperations operations,

- string indexName);

-// Synchronous operation with only required parameters

-public static IndexGetStatisticsResponse GetStatistics(

- this IIndexOperations operations,

- string indexName);

-```

-The method signatures for the same operation in version 1.1 look like this:

-In `IIndexesOperations`:

-```csharp

-// Asynchronous operation with lower-level HTTP features exposed

-Task<AzureOperationResponse<IndexGetStatisticsResult>> GetStatisticsWithHttpMessagesAsync(

- string indexName,

- SearchRequestOptions searchRequestOptions = default(SearchRequestOptions),

- Dictionary<string, List<string>> customHeaders = null,

- CancellationToken cancellationToken = default(CancellationToken));

-```

-In `IndexesOperationsExtensions`:

-```csharp

-// Simplified asynchronous operation

-public static Task<IndexGetStatisticsResult> GetStatisticsAsync(

- this IIndexesOperations operations,

- string indexName,

- SearchRequestOptions searchRequestOptions = default(SearchRequestOptions),

- CancellationToken cancellationToken = default(CancellationToken));

-// Simplified synchronous operation

-public static IndexGetStatisticsResult GetStatistics(

- this IIndexesOperations operations,

- string indexName,

- SearchRequestOptions searchRequestOptions = default(SearchRequestOptions));

-```

-Starting with version 1.1, the Azure Search .NET SDK organizes operation methods differently:

-* Optional parameters are now modeled as default parameters rather than additional method overloads. This reduces the number of method overloads, sometimes dramatically.

-* The extension methods now hide a lot of the extraneous details of HTTP from the caller. For example, older versions of the SDK returned a response object with an HTTP status code, which you often didn't need to check because operation methods throw `CloudException` for any status code that indicates an error. The new extension methods just return model objects, saving you the trouble of having to unwrap them in your code.

-* Conversely, the core interfaces now expose methods that give you more control at the HTTP level if you need it. You can now pass in custom HTTP headers to be included in requests, and the new `AzureOperationResponse<T>` return type gives you direct access to the `HttpRequestMessage` and `HttpResponseMessage` for the operation. `AzureOperationResponse` is defined in the `Microsoft.Rest.Azure` namespace and replaces `Hyak.Common.OperationResponse`.

-### ScoringParameters changes

-A new class named `ScoringParameter` has been added in the latest SDK to make it easier to provide parameters to scoring profiles in a search query. Previously the `ScoringProfiles` property of the `SearchParameters` class was typed as `IList<string>`; Now it is typed as `IList<ScoringParameter>`.

-#### Example

-If your code looks like this:

-```csharp

-var sp = new SearchParameters();

-sp.ScoringProfile = "jobsScoringFeatured"; // Use a scoring profile

-sp.ScoringParameters = new[] { "featuredParam-featured", "mapCenterParam-" + lon + "," + lat };

-```

-You can change it to this to fix any build errors:

-```csharp

-var sp = new SearchParameters();

-sp.ScoringProfile = "jobsScoringFeatured"; // Use a scoring profile

-sp.ScoringParameters =

- new[]

- {

- new ScoringParameter("featuredParam", new[] { "featured" }),

- new ScoringParameter("mapCenterParam", GeographyPoint.Create(lat, lon))

- };

-```

-### Model class changes

-Due to the signature changes described in [Operation method changes](#OperationMethodChanges), many classes in the `Microsoft.Azure.Search.Models` namespace have been renamed or removed. For example:

-* `IndexDefinitionResponse` has been replaced by `AzureOperationResponse<Index>`

-* `DocumentSearchResponse` has been renamed to `DocumentSearchResult`

-* `IndexResult` has been renamed to `IndexingResult`

-* `Documents.Count()` now returns a `long` with the document count instead of a `DocumentCountResponse`

-* `IndexGetStatisticsResponse` has been renamed to `IndexGetStatisticsResult`

-* `IndexListResponse` has been renamed to `IndexListResult`

-To summarize, `OperationResponse`-derived classes that existed only to wrap a model object have been removed. The remaining classes have had their suffix changed from `Response` to `Result`.

-#### Example

-If your code looks like this:

-```csharp

-IndexerGetStatusResponse statusResponse = null;

-try

-{

- statusResponse = _searchClient.Indexers.GetStatus(indexer.Name);

-}

-catch (Exception ex)

-{

- Console.WriteLine("Error polling for indexer status: {0}", ex.Message);

- return;

-}

-IndexerExecutionResult lastResult = statusResponse.ExecutionInfo.LastResult;

-```

-You can change it to this to fix any build errors:

-```csharp

-IndexerExecutionInfo status = null;

-try

-{

- status = _searchClient.Indexers.GetStatus(indexer.Name);

-}

-catch (Exception ex)

-{

- Console.WriteLine("Error polling for indexer status: {0}", ex.Message);

- return;

-}

-IndexerExecutionResult lastResult = status.LastResult;

-```

-#### Response classes and IEnumerable

-An additional change that may affect your code is that response classes that hold collections no longer implement `IEnumerable<T>`. Instead, you can access the collection property directly. For example, if your code looks like this:

-```csharp

-DocumentSearchResponse<Hotel> response = indexClient.Documents.Search<Hotel>(searchText, sp);

-foreach (SearchResult<Hotel> result in response)

-{

- Console.WriteLine(result.Document);

-}

-```

-You can change it to this to fix any build errors:

-```csharp

-DocumentSearchResult<Hotel> response = indexClient.Documents.Search<Hotel>(searchText, sp);

-foreach (SearchResult<Hotel> result in response.Results)

-{

- Console.WriteLine(result.Document);

-}

-```

-#### Special case for web applications

-If you have a web application that serializes `DocumentSearchResponse` directly to send search results to the browser, you will need to change your code or the results will not serialize correctly. For example, if your code looks like this:

-```csharp

-public ActionResult Search(string q = "")

-{

- // If blank search, assume they want to search everything

- if (string.IsNullOrWhiteSpace(q))

- q = "*";

- return new JsonResult

- {

- JsonRequestBehavior = JsonRequestBehavior.AllowGet,

- Data = _featuresSearch.Search(q)

- };

-}

-```

-You can change it by getting the `.Results` property of the search response to fix search result rendering:

-```csharp

-public ActionResult Search(string q = "")

-{

- // If blank search, assume they want to search everything

- if (string.IsNullOrWhiteSpace(q))

- q = "*";

- return new JsonResult

- {

- JsonRequestBehavior = JsonRequestBehavior.AllowGet,

- Data = _featuresSearch.Search(q).Results

- };

-}

-```

-You will have to look for such cases in your code yourself; **The compiler will not warn you** because `JsonResult.Data` is of type `object`.

-### CloudException changes

-The `CloudException` class has moved from the `Hyak.Common` namespace to the `Microsoft.Rest.Azure` namespace. Also, its `Error` property has been renamed to `Body`.

-### SearchServiceClient and SearchIndexClient changes

-The type of the `Credentials` property has changed from `SearchCredentials` to its base class, `ServiceClientCredentials`. If you need to access the `SearchCredentials` of a `SearchIndexClient` or `SearchServiceClient`, please use the new `SearchCredentials` property.

-In older versions of the SDK, `SearchServiceClient` and `SearchIndexClient` had constructors that took an `HttpClient` parameter. These have been replaced with constructors that take an `HttpClientHandler` and an array of `DelegatingHandler` objects. This makes it easier to install custom handlers to pre-process HTTP requests if necessary.

-Finally, the constructors that took a `Uri` and `SearchCredentials` have changed. For example, if you have code that looks like this:

-```csharp

-var client =

- new SearchServiceClient(

- new SearchCredentials("abc123"),

- new Uri("http://myservice.search.windows.net"));

-```

-You can change it to this to fix any build errors:

-```csharp

-var client =

- new SearchServiceClient(

- new Uri("http://myservice.search.windows.net"),

- new SearchCredentials("abc123"));

-```

-Also note that the type of the credentials parameter has changed to `ServiceClientCredentials`. This is unlikely to affect your code since `SearchCredentials` is derived from `ServiceClientCredentials`.

-### Passing a request ID

-In older versions of the SDK, you could set a request ID on the `SearchServiceClient` or `SearchIndexClient` and it would be included in every request to the REST API. This is useful for troubleshooting issues with your search service if you need to contact support. However, it is more useful to set a unique request ID for every operation rather than to use the same ID for all operations. For this reason, the `SetClientRequestId` methods of `SearchServiceClient` and `SearchIndexClient` have been removed. Instead, you can pass a request ID to each operation method via the optional `SearchRequestOptions` parameter.

-> [!NOTE]

-> In a future release of the SDK, we will add a new mechanism for setting a request ID globally on the client objects that is consistent with the approach used by other Azure SDKs.

->

->

-### Example

-If you have code that looks like this:

-```csharp

-client.SetClientRequestId(Guid.NewGuid());

-...

-long count = client.Documents.Count();

-```

-You can change it to this to fix any build errors:

-```csharp

-long count = client.Documents.Count(new SearchRequestOptions(requestId: Guid.NewGuid()));

-```

-### Interface name changes

-The operation group interface names have all changed to be consistent with their corresponding property names:

-* The type of `ISearchServiceClient.Indexes` has been renamed from `IIndexOperations` to `IIndexesOperations`.

-* The type of `ISearchServiceClient.Indexers` has been renamed from `IIndexerOperations` to `IIndexersOperations`.

-* The type of `ISearchServiceClient.DataSources` has been renamed from `IDataSourceOperations` to `IDataSourcesOperations`.

-* The type of `ISearchIndexClient.Documents` has been renamed from `IDocumentOperations` to `IDocumentsOperations`.

-This change is unlikely to affect your code unless you created mocks of these interfaces for test purposes.

-<a name="BugFixesV1"></a>

-## Bug fixes in version 1.1

-There was a bug in older versions of the Azure Search .NET SDK relating to serialization of custom model classes. The bug could occur if you created a custom model class with a property of a non-nullable value type.

-### Steps to reproduce

-Create a custom model class with a property of non-nullable value type. For example, add a public `UnitCount` property of type `int` instead of `int?`.

-If you index a document with the default value of that type (for example, 0 for `int`), the field will be null in Azure Search. If you subsequently search for that document, the `Search` call will throw `JsonSerializationException` complaining that it can't convert `null` to `int`.

-Also, filters may not work as expected since null was written to the index instead of the intended value.

-### Fix details

-We have fixed this issue in version 1.1 of the SDK. Now, if you have a model class like this:

-```csharp

-public class Model

-{

- public string Key { get; set; }

- public int IntValue { get; set; }

-}

-```

-and you set `IntValue` to 0, that value is now correctly serialized as 0 on the wire and stored as 0 in the index. Round tripping also works as expected.

-There is one potential issue to be aware of with this approach: If you use a model type with a non-nullable property, you have to **guarantee** that no documents in your index contain a null value for the corresponding field. Neither the SDK nor the Azure Search REST API will help you to enforce this.

-This is not just a hypothetical concern: Imagine a scenario where you add a new field to an existing index that is of type `Edm.Int32`. After updating the index definition, all documents will have a null value for that new field (since all types are nullable in Azure Search). If you then use a model class with a non-nullable `int` property for that field, you will get a `JsonSerializationException` like this when trying to retrieve documents:

-```output

-Error converting value {null} to type 'System.Int32'. Path 'IntValue'.

-```

-For this reason, we still recommend that you use nullable types in your model classes as a best practice.

-For more details on this bug and the fix, please see [this issue on GitHub](https://github.com/Azure/azure-sdk-for-net/issues/1063).

-description: Migrate code to the Azure Cognitive Search .NET SDK version 10 from older versions. Learn what is new and which code changes are required.

-# Upgrade to Azure Cognitive Search .NET SDK version 10

-> [!IMPORTANT]

-> Version 10 is the last version of the Microsoft.Azure.Search package and it's now deprecated. It's succeeded by Azure.Search.Documents. If you're using older versions of Microsoft.Azure.Search, we recommend a sequential migration path. For example, if you're using version 8.0-preview or older, you should upgrade to version 9 first, and then to version 10, and finally to version 11.

-If you're using version 9.0 or older of the [.NET SDK](/dotnet/api/overview/azure/search), this article will help you upgrade your application to use version 10.

-"Azure Search" is renamed to "Azure Cognitive Search" in version 10, but namespaces and package names are unchanged. Previous versions of the SDK (9.0 and earlier) continue to use the "Microsoft.Search" prefix. For more information about using the SDK, including examples, see [How to use Azure Cognitive Search from a .NET Application](search-howto-dotnet-sdk.md).

-Version 10 adds several features and bug fixes, bringing it to the same functional level as the REST API version `2019-05-06`. In cases where a change breaks existing code, we'll walk you through the [steps required to resolve the issue](#UpgradeSteps).

-<a name="WhatsNew"></a>

-## What's new in version 10

-Version 10 of the Azure Cognitive Search .NET SDK targets REST API `2019-05-06` with these updates:

-* Introduction of two new skills - [Conditional skill](cognitive-search-skill-conditional.md) and [Text Translation skill](cognitive-search-skill-text-translation.md).

-* [Shaper skill](cognitive-search-skill-shaper.md) inputs have been restructured to accommodate consolidation from nested contexts. For more information, see this [example JSON definition](./cognitive-search-skill-shaper.md#scenario-3-input-consolidation-from-nested-contexts).

-* Addition of two new [field mapping functions](search-indexer-field-mappings.md):

- - [urlEncode](./search-indexer-field-mappings.md#urlencode-function)

- - [urlDecode](./search-indexer-field-mappings.md#urldecode-function)

-* On certain occasions, errors and warnings that show up in [indexer execution status](/rest/api/searchservice/get-indexer-status) can have additional details that help in debugging. `IndexerExecutionResult` has been updated to reflect this behavior.

-* Individual skills defined within a [skillset](cognitive-search-defining-skillset.md) can optionally be identified by specifying a `name` property.

-* `ServiceLimits` shows limits for [complex types](./search-howto-complex-data-types.md) and `IndexerExecutionInfo` shows pertinent indexer limits/quotas.

-<a name="UpgradeSteps"></a>

-## Steps to upgrade

-1. Update your NuGet reference for `Microsoft.Azure.Search` using either the NuGet Package Manager Console or by right-clicking on your project references and selecting "Manage NuGet Packages..." in Visual Studio.

-2. Once NuGet has downloaded the new packages and their dependencies, rebuild your project.

-3. If your build fails, you will need to fix each build error. See [Breaking changes in version 10](#ListOfChanges) for details on how to resolve each potential build error.

-4. Once you've fixed any build errors or warnings, you can make changes to your application to take advantage of new functionality if you wish. New features in the SDK are detailed in [What's new in version 10](#WhatsNew).

-<a name="ListOfChanges"></a>

-## Breaking changes in version 10

-There are several breaking changes in version 10 that may require code changes in addition to rebuilding your application.

-> [!NOTE]

-> The list of changes below is not exhaustive. Some changes will likely not result in build errors, but are technically breaking since they break binary compatibility with assemblies that depend on earlier versions of the Azure Cognitive Search .NET SDK assemblies. Significant changes that fall under this category are also listed along with recommendations. Please rebuild your application when upgrading to version 10 to avoid any binary compatibility issues.

-### Custom Web API skill definition

-The definition of the [Custom Web API skill](cognitive-search-custom-skill-web-api.md) was incorrectly specified in version 9 and older.

-The model for `WebApiSkill` specified `HttpHeaders` as an object property that _contains_ a dictionary. Creating a skillset with a `WebApiSkill` constructed in this manner would result in an exception because the REST API would consider the request badly formed. This issue has been corrected, by making `HttpHeaders` **a top-level dictionary property** on the `WebApiSkill` model itself - which is considered a valid request from the REST API.

-For example, if you previously attempted to instantiate a `WebApiSkill` as follows:

-```csharp

-var webApiSkill = new WebApiSkill(

- inputs,

- outputs,

- uri: "https://contoso.example.org")

-{

- HttpHeaders = new WebApiHttpHeaders()

- {

- Headers = new Dictionary<string, string>()

- {

- ["header"] = "value"

- }

- }

-};

-```

-change it to the following, to avoid the validation error from the REST API:

-```csharp

-var webApiSkill = new WebApiSkill(

- inputs,

- outputs,

- uri: "https://contoso.example.org")

-{

- HttpHeaders = new Dictionary<string, string>()

- {

- ["header"] = "value"

- }

-};

-```

-## Shaper skill allows nested context consolidation

-Shaper skill can now allow input consolidation from nested contexts. To enable this change, we modified `InputFieldMappingEntry` so that it can be instantiated by specifying just a `Source` property, or both the `SourceContext` and `Inputs` properties.

-You will most likely not need to make any code changes; however note that only one of these two combinations is allowed. This means:

-If you decide to start making use of this new capability, make sure all your clients are updated to use version 10 first, before rolling out that change. Otherwise, there is a possibility that an update by a client (using an older version of the SDK) to the Shaper skill may result in validation errors.

-> [!NOTE]

-> Even though the underlying `InputFieldMappingEntry` model has been modified to allow consolidation from nested contexts, it's use is only valid within the definition of a Shaper skill. Using this capability in other skills, while valid at compile time, will result in a validation error at runtime.

-## Skills can be identified by a name

-Each skill within a skillset now has a new property `Name`, which can be initialized in your code to help identify the skill. This is optional - when unspecified (which is the default, if no explicit code change was made), it is assigned a default name using the 1-based index of the skill in the skillset, prefixed with the '#' character. For example, in the following skillset definition (most initializations skipped for brevity):

-```csharp

-var skillset = new Skillset()

-{

- Skills = new List<Skill>()

- {

- new SentimentSkill(),

- new WebApiSkill(),

- new ShaperSkill(),

- ...

- }

-}

-```

-`SentimentSkill` is assigned a name `#1`, `WebApiSkill` is assigned `#2`, `ShaperSkill` is assigned `#3` and so on.

-If you choose to identify skills by a custom name, make sure to update all instances of your clients to version 10 of the SDK first. Otherwise, there is a possibility that a client using an older version of the SDK could `null` out the `Name` property of a skill, causing the client to fall back on the default naming scheme.

-## Details about errors and warnings

-`ItemError` and `ItemWarning` models that encapsulate details of errors and warnings (respectively) that occur during an indexer execution have been modified to include three new properties with the objective to aid in debugging the indexer. These properties are:

-> [!NOTE]

-> We have started to structure our errors and warnings to include these useful details whenever possible. We are working to make sure that for all errors and warnings these details are present, but it is a work in progress and these additional details may not always be populated.

-## Next steps

-description: Migrate code to the Azure Search .NET SDK version 5 from older versions. Learn what is new and which code changes are required.

-# Upgrade to Azure Search .NET SDK version 5

-If you're using version 4.0-preview or older of the [.NET SDK](/dotnet/api/overview/azure/search), this article will help you upgrade your application to use version 5.

-For a more general walkthrough of the SDK including examples, see [How to use Azure Search from a .NET Application](search-howto-dotnet-sdk.md).

-Version 5 of the Azure Search .NET SDK contains some changes from earlier versions. These are mostly minor, so changing your code should require only minimal effort. See [Steps to upgrade](#UpgradeSteps) for instructions on how to change your code to use the new SDK version.

-> [!NOTE]

-> If you're using version 2.0-preview or older, you should upgrade to version 3 first, and then upgrade to version 5. See [Upgrading to the Azure Search .NET SDK version 3](search-dotnet-sdk-migration.md) for instructions.

->

-> Your Azure Search service instance supports several REST API versions, including the latest one. You can continue to use a version when it is no longer the latest one, but we recommend that you migrate your code to use the newest version. When using the REST API, you must specify the API version in every request via the api-version parameter. When using the .NET SDK, the version of the SDK you're using determines the corresponding version of the REST API. If you are using an older SDK, you can continue to run that code with no changes even if the service is upgraded to support a newer API version.

-<a name="WhatsNew"></a>

-## What's new in version 5

-Version 5 of the Azure Search .NET SDK targets the latest generally available version of the Azure Search REST API, specifically 2017-11-11. This makes it possible to use new features of Azure Search from a .NET application, including the following:

-* [Synonyms](search-synonyms.md).

-* You can now programmatically access warnings in indexer execution history (see the `Warning` property of `IndexerExecutionResult` in the [.NET reference](/dotnet/api/microsoft.azure.search.models.indexerexecutionresult) for more details).

-* Support for .NET Core 2.

-* New package structure supports using only the parts of the SDK that you need (see [Breaking changes in version 5](#ListOfChanges) for details).

-<a name="UpgradeSteps"></a>

-## Steps to upgrade

-First, update your NuGet reference for `Microsoft.Azure.Search` using either the NuGet Package Manager Console or by right-clicking on your project references and selecting "Manage NuGet Packages..." in Visual Studio.

-Once NuGet has downloaded the new packages and their dependencies, rebuild your project. Depending on how your code is structured, it may rebuild successfully. If so, you're ready to go!

-If your build fails, you should see a build error like the following:

-```output

-The name 'SuggesterSearchMode' does not exist in the current context

-```

-The next step is to fix this build error. See [Breaking changes in version 5](#ListOfChanges) for details on what causes the error and how to fix it.

-Please note that due to changes in the packaging of the Azure Search .NET SDK, you must rebuild your application in order to use version 5. These changes are detailed in [Breaking changes in version 5](#ListOfChanges).

-You may see additional build warnings related to obsolete methods or properties. The warnings will include instructions on what to use instead of the deprecated feature. For example, if your application uses the `IndexingParametersExtensions.DoNotFailOnUnsupportedContentType` method, you should get a warning that says "This behavior is now enabled by default, so calling this method is no longer necessary."

-Once you've fixed any build errors or warnings, you can make changes to your application to take advantage of new functionality if you wish. New features in the SDK are detailed in [What's new in version 5](#WhatsNew).

-<a name="ListOfChanges"></a>

-## Breaking changes in version 5

-### New Package Structure

-The most substantial breaking change in version 5 is that the `Microsoft.Azure.Search` assembly and its contents have been divided into four separate assemblies that are now distributed as four separate NuGet packages:

-

-This change is technically breaking since many types were moved between assemblies. This is why rebuilding your application is necessary in order to upgrade to version 5 of the SDK.

-There a small number of other breaking changes in version 5 that may require code changes in addition to rebuilding your application.

-### Change to Suggesters

-The `Suggester` constructor no longer has an `enum` parameter for `SuggesterSearchMode`. This enum only had one value, and was therefore redundant. If you see build errors as a result of this, simply remove references to the `SuggesterSearchMode` parameter.

-### Removed obsolete members

-You may see build errors related to methods or properties that were marked as obsolete in earlier versions and subsequently removed in version 5. If you encounter such errors, here is how to resolve them:

-### Removed preview features

-If you are upgrading from version 4.0-preview to version 5, be aware that JSON array and CSV parsing support for Blob Indexers has been removed since these features are still in preview. Specifically, the following methods of the `IndexingParametersExtensions` class have been removed:

-If your application has a hard dependency on these features, you will not be able to upgrade to version 5 of the Azure Search .NET SDK. You can continue to use version 4.0-preview. However, please keep in mind that **we do not recommend using preview SDKs in production applications**. Preview features are for evaluation only and may change.

-## Conclusion

-If you need more details on using the Azure Search .NET SDK, see the [.NET How-to](search-howto-dotnet-sdk.md).

-We welcome your feedback on the SDK. If you encounter problems, feel free to ask us for help on [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-search). If you find a bug, you can file an issue in the [Azure .NET SDK GitHub repository](https://github.com/Azure/azure-sdk-for-net/issues). Make sure to prefix your issue title with "[Azure Search]".

-Thank you for using Azure Search!

-description: Migrate code to the Azure Search .NET SDK version 9 from older versions. Learn what is new and which code changes are required.

-# Upgrade to Azure Search .NET SDK version 9

-If you're using version 7.0-preview or older of the [Azure Search .NET SDK](/dotnet/api/overview/azure/search), this article will help you upgrade your application to use version 9.

-> [!NOTE]

-> If you wish to use version 8.0-preview to evaluate features that are not generally available yet, you can also follow the instructions in this article to upgrade to 8.0-preview from prior versions.

-For a more general walkthrough of the SDK including examples, see [How to use Azure Search from a .NET Application](search-howto-dotnet-sdk.md).

-Version 9 of the Azure Search .NET SDK contains many changes from earlier versions. Some of these are breaking changes, but they should only require relatively minor changes to your code. See [Steps to upgrade](#UpgradeSteps) for instructions on how to change your code to use the new SDK version.

-> [!NOTE]

-> If you're using version 4.0-preview or older, you should upgrade to version 5 first, and then upgrade to version 9. See [Upgrading to the Azure Search .NET SDK version 5](search-dotnet-sdk-migration-version-5.md) for instructions.

->

-> Your Azure Search service instance supports several REST API versions, including the latest one. You can continue to use a version when it is no longer the latest one, but we recommend that you migrate your code to use the newest version. When using the REST API, you must specify the API version in every request via the api-version parameter. When using the .NET SDK, the version of the SDK you're using determines the corresponding version of the REST API. If you are using an older SDK, you can continue to run that code with no changes even if the service is upgraded to support a newer API version.

-<a name="WhatsNew"></a>

-## What's new in version 9

-Version 9 of the Azure Search .NET SDK targets 2019-05-06 version of Azure Search REST API, with the following features:

-* [AI enrichment](cognitive-search-concept-intro.md) is the ability to extract text from images, blobs, and other unstructured data sources - enriching the content to make it more searchable in an Azure Search index.

-* Support for [complex types](search-howto-complex-data-types.md) allows you to model almost any nested JSON structure in an Azure Search index.

-* [Autocomplete](search-add-autocomplete-suggestions.md) provides an alternative to the **Suggest** API for implementing search-as-you-type behavior. Autocomplete "finishes" the word or phrase that a user is currently typing.

-* [JsonLines parsing mode](search-howto-index-json-blobs.md), part of blob indexing, creates one search document per JSON entity that is separated by a newline.

-### New preview features in version 8.0-preview

-Version 8.0-preview of the Azure Search .NET SDK targets API version 2017-11-11-Preview. This version includes all the same features of version 9, plus:

-* [Customer-managed encryption keys](search-security-manage-encryption-keys.md) for service-side encryption-at-rest is a new preview feature. In addition to the built-in encryption-at-rest managed by Microsoft, you can apply an additional layer of encryption where you are the sole owner of the keys.

-<a name="UpgradeSteps"></a>

-## Steps to upgrade

-First, update your NuGet reference for `Microsoft.Azure.Search` using either the NuGet Package Manager Console or by right-clicking on your project references and selecting "Manage NuGet Packages..." in Visual Studio.

-Once NuGet has downloaded the new packages and their dependencies, rebuild your project. Depending on how your code is structured, it may rebuild successfully. If so, you're ready to go!

-If your build fails, you will need to fix each build error. See [Breaking changes in version 9](#ListOfChanges) for details on how to resolve each potential build error.

-You may see additional build warnings related to obsolete methods or properties. The warnings will include instructions on what to use instead of the deprecated feature. For example, if your application uses the `DataSourceType.DocumentDb` property, you should get a warning that says "This member is deprecated. Use CosmosDb instead".

-Once you've fixed any build errors or warnings, you can make changes to your application to take advantage of new functionality if you wish. New features in the SDK are detailed in [What's new in version 9](#WhatsNew).

-<a name="ListOfChanges"></a>

-## Breaking changes in version 9

-There are several breaking changes in version 9 that may require code changes in addition to rebuilding your application.

-> [!NOTE]

-> The list of changes below is not exhaustive. Some changes will likely not result in build errors, but are technically breaking since they break binary compatibility with assemblies that depend on earlier versions of the Azure Search .NET SDK assemblies. Such changes are not listed below. Please rebuild your application when upgrading to version 9 to avoid any binary compatibility issues.

-### Immutable properties

-The public properties of several model classes are now immutable. If you need to create custom instances of these classes for testing, you can use the new parameterized constructors:

- - `AutocompleteItem`

- - `DocumentSearchResult`

- - `DocumentSuggestResult`

- - `FacetResult`

- - `SearchResult`

- - `SuggestResult`

-### Changes to Field

-The `Field` class has changed now that it can also represent complex fields.

-The following `bool` properties are now nullable:

- - `IsFilterable`

- - `IsFacetable`

- - `IsSearchable`

- - `IsSortable`

- - `IsRetrievable`

- - `IsKey`

-This is because these properties must now be `null` in the case of complex fields. If you have code that reads these properties, it has to be prepared to handle `null`. Note that all other properties of `Field` have always been and continue to be nullable, and some of those will also be `null` in the case of complex fields -- specifically the following:

- - `Analyzer`

- - `SearchAnalyzer`

- - `IndexAnalyzer`

- - `SynonymMaps`

-The parameterless constructor of `Field` has been made `internal`. From now on, every `Field` requires an explicit name and data type at the time of construction.

-### Simplified batch and results types

-In version 7.0-preview and earlier, the various classes that encapsulate groups of documents were structured into parallel class hierarchies:

- - `DocumentSearchResult` and `DocumentSearchResult<T>` inherited from `DocumentSearchResultBase`

- - `DocumentSuggestResult` and `DocumentSuggestResult<T>` inherited from `DocumentSuggestResultBase`

- - `IndexAction` and `IndexAction<T>` inherited from `IndexActionBase`

- - `IndexBatch` and `IndexBatch<T>` inherited from `IndexBatchBase`

- - `SearchResult` and `SearchResult<T>` inherited from `SearchResultBase`

- - `SuggestResult` and `SuggestResult<T>` inherited from `SuggestResultBase`

-The derived types without a generic type parameter were meant to be used in "dynamically-typed" scenarios and assumed usage of the `Document` type.

-Starting with version 8.0-preview, the base classes and non-generic derived classes have all been removed. For dynamically-typed scenarios, you can use `IndexBatch<Document>`, `DocumentSearchResult<Document>`, and so on.

-

-### Removed ExtensibleEnum

-The `ExtensibleEnum` base class has been removed. All classes that derived from it are now structs, such as `AnalyzerName`, `DataType`, and `DataSourceType` for example. Their `Create` methods have also been removed. You can just remove calls to `Create` since these types are implicitly convertible from strings. If that results in compiler errors, you can explicitly invoke the conversion operator via casting to disambiguate types. For example, you can change code like this:

-```csharp

-var index = new Index()

-{

- Fields = new[]

- {

- new Field("id", DataType.String) { IsKey = true },

- new Field("message", AnalyzerName.Create("my_email_analyzer")) { IsSearchable = true }

- },

- ...

-}

-```

-to this:

-```csharp

-var index = new Index()

-{

- Fields = new[]

- {

- new Field("id", DataType.String) { IsKey = true },

- new Field("message", (AnalyzerName)"my_email_analyzer") { IsSearchable = true }

- },

- ...

-}

-```

-Properties that held optional values of these types are now explicitly typed as nullable so they continue to be optional.

-### Removed FacetResults and HitHighlights

-The `FacetResults` and `HitHighlights` classes have been removed. Facet results are now typed as `IDictionary<string, IList<FacetResult>>` and hit highlights as `IDictionary<string, IList<string>>`. A quick way to resolve build errors introduced by this change is to add `using` aliases at the top of each file that uses the removed types. For example:

-```csharp

-using FacetResults = System.Collections.Generic.IDictionary<string, System.Collections.Generic.IList<Models.FacetResult>>;

-using HitHighlights = System.Collections.Generic.IDictionary<string, System.Collections.Generic.IList<string>>;

-```

-### Change to SynonymMap

-The `SynonymMap` constructor no longer has an `enum` parameter for `SynonymMapFormat`. This enum only had one value, and was therefore redundant. If you see build errors as a result of this, simply remove references to the `SynonymMapFormat` parameter.

-### Miscellaneous model class changes

-The `AutocompleteMode` property of `AutocompleteParameters` is no longer nullable. If you have code that assigns this property to `null`, you can simply remove it and the property will automatically be initialized to the default value.

-The order of the parameters to the `IndexAction` constructor has changed now that this constructor is auto-generated. Instead of using the constructor, we recommend using the factory methods `IndexAction.Upload`, `IndexAction.Merge`, and so on.

-### Removed preview features

-If you are upgrading from version 8.0-preview to version 9, be aware that encryption with customer-managed keys has been removed since this feature is still in preview. Specifically, the `EncryptionKey` properties of `Index` and `SynonymMap` have been removed.

-If your application has a hard dependency on this feature, you will not be able to upgrade to version 9 of the Azure Search .NET SDK. You can continue to use version 8.0-preview. However, please keep in mind that **we do not recommend using preview SDKs in production applications**. Preview features are for evaluation only and may change.

-> [!NOTE]

-> If you created encrypted indexes or synonym maps using version 8.0-preview of the SDK, you will still be able use them and modify their definitions using version 9 of the SDK without adversely affecting their encryption status. Version 9 of the SDK will not send the `encryptionKey` property to the REST API, and as a result the REST API will not change the encryption status of the resource.

-### Behavioral change in data retrieval

-If you're using the "dynamically typed" `Search`, `Suggest`, or `Get` APIs that return instances of type `Document`, be aware that they now deserialize empty JSON arrays to `object[]` instead of `string[]`.

-## Conclusion

-If you need more details on using the Azure Search .NET SDK, see the [.NET How-to](search-howto-dotnet-sdk.md).

-We welcome your feedback on the SDK. If you encounter problems, feel free to ask us for help on [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-search). If you find a bug, you can file an issue in the [Azure .NET SDK GitHub repository](https://github.com/Azure/azure-sdk-for-net/issues). Make sure to prefix your issue title with "[Azure Search]".

-Thank you for using Azure Search!

-description: Migrate code to the Azure Search .NET SDK version 3 from older versions. Learn what's new and which code changes are required.

-# Upgrade to Azure Search .NET SDK version 3

-<! DETAILS in the word doc

-cosmosdb

-NER v1 skill

-Indexer execution result errors no longer have status

-the data source API will no longer return in the response of any REST operation, the connection string specified by the user.

->

-If you're using version 2.0-preview or older of the [Azure Search .NET SDK](/dotnet/api/overview/azure/search), this article will help you upgrade your application to use version 3.

-For a more general walkthrough of the SDK including examples, see [How to use Azure Search from a .NET Application](search-howto-dotnet-sdk.md).

-Version 3 of the Azure Search .NET SDK contains some changes from earlier versions. These are mostly minor, so changing your code should require only minimal effort. See [Steps to upgrade](#UpgradeSteps) for instructions on how to change your code to use the new SDK version.

-> [!NOTE]

-> If you're using version 1.0.2-preview or older, you should upgrade to version 1.1 first, and then upgrade to version 3. See [Upgrading to the Azure Search .NET SDK version 1.1](search-dotnet-sdk-migration-version-1.md) for instructions.

->

-> Your Azure Search service instance supports several REST API versions, including the latest one. You can continue to use a version when it is no longer the latest one, but we recommend that you migrate your code to use the newest version. When using the REST API, you must specify the API version in every request via the api-version parameter. When using the .NET SDK, the version of the SDK you're using determines the corresponding version of the REST API. If you are using an older SDK, you can continue to run that code with no changes even if the service is upgraded to support a newer API version.

-<a name="WhatsNew"></a>

-## What's new in version 3

-Version 3 of the Azure Search .NET SDK targets the latest generally available version of the Azure Search REST API, specifically 2016-09-01. This makes it possible to use many new features of Azure Search from a .NET application, including the following:

-* [Custom analyzers](index-add-custom-analyzers.md)

-* [Azure Blob Storage](search-howto-indexing-azure-blob-storage.md) and [Azure Table Storage](search-howto-indexing-azure-tables.md) indexer support

-* Indexer customization via [field mappings](search-indexer-field-mappings.md)

-* ETags support to enable safe concurrent updating of index definitions, indexers, and data sources

-* Support for building index field definitions declaratively by decorating your model class and using the new `FieldBuilder` class.

-* Support for .NET Core and .NET Portable Profile 111

-<a name="UpgradeSteps"></a>

-## Steps to upgrade

-First, update your NuGet reference for `Microsoft.Azure.Search` using either the NuGet Package Manager Console or by right-clicking on your project references and selecting "Manage NuGet Packages..." in Visual Studio.

-Once NuGet has downloaded the new packages and their dependencies, rebuild your project. Depending on how your code is structured, it may rebuild successfully. If so, you're ready to go!

-If your build fails, you should see a build error like the following:

-```output

-Program.cs(31,45,31,86): error CS0266: Cannot implicitly convert type 'Microsoft.Azure.Search.ISearchIndexClient' to 'Microsoft.Azure.Search.SearchIndexClient'. An explicit conversion exists (are you missing a cast?)

-```

-The next step is to fix this build error. See [Breaking changes in version 3](#ListOfChanges) for details on what causes the error and how to fix it.

-You may see additional build warnings related to obsolete methods or properties. The warnings will include instructions on what to use instead of the deprecated feature. For example, if your application uses the `IndexingParameters.Base64EncodeKeys` property, you should get a warning that says `"This property is obsolete. Please create a field mapping using 'FieldMapping.Base64Encode' instead."`

-Once you've fixed any build errors, you can make changes to your application to take advantage of new functionality if you wish. New features in the SDK are detailed in [What's new in version 3](#WhatsNew).

-<a name="ListOfChanges"></a>

-## Breaking changes in version 3

-There a small number of breaking changes in version 3 that may require code changes in addition to rebuilding your application.

-### Indexes.GetClient return type

-The `Indexes.GetClient` method has a new return type. Previously, it returned `SearchIndexClient`, but this was changed to `ISearchIndexClient` in version 2.0-preview, and that change carries over to version 3. This is to support customers that wish to mock the `GetClient` method for unit tests by returning a mock implementation of `ISearchIndexClient`.

-#### Example

-If your code looks like this:

-```csharp

-SearchIndexClient indexClient = serviceClient.Indexes.GetClient("hotels");

-```

-You can change it to this to fix any build errors:

-```csharp

-ISearchIndexClient indexClient = serviceClient.Indexes.GetClient("hotels");

-```

-### AnalyzerName, DataType, and others are no longer implicitly convertible to strings

-There are many types in the Azure Search .NET SDK that derive from `ExtensibleEnum`. Previously these types were all implicitly convertible to type `string`. However, a bug was discovered in the `Object.Equals` implementation for these classes, and fixing the bug required disabling this implicit conversion. Explicit conversion to `string` is still allowed.

-#### Example

-If your code looks like this:

-```csharp

-var customTokenizerName = TokenizerName.Create("my_tokenizer");

-var customTokenFilterName = TokenFilterName.Create("my_tokenfilter");

-var customCharFilterName = CharFilterName.Create("my_charfilter");

-

-var index = new Index();

-index.Analyzers = new Analyzer[]

-{

- new CustomAnalyzer(

- "my_analyzer",

- customTokenizerName,

- new[] { customTokenFilterName },

- new[] { customCharFilterName }),

-};

-```

-You can change it to this to fix any build errors:

-```csharp

-const string CustomTokenizerName = "my_tokenizer";

-const string CustomTokenFilterName = "my_tokenfilter";

-const string CustomCharFilterName = "my_charfilter";

-

-var index = new Index();

-index.Analyzers = new Analyzer[]

-{

- new CustomAnalyzer(

- "my_analyzer",

- CustomTokenizerName,

- new TokenFilterName[] { CustomTokenFilterName },

- new CharFilterName[] { CustomCharFilterName })

-};

-```

-### Removed obsolete members

-You may see build errors related to methods or properties that were marked as obsolete in version 2.0-preview and subsequently removed in version 3. If you encounter such errors, here is how to resolve them:

-### Removed preview features

-If you are upgrading from version 2.0-preview to version 3, be aware that JSON and CSV parsing support for Blob Indexers has been removed since these features are still in preview. Specifically, the following methods of the `IndexingParametersExtensions` class have been removed:

-If your application has a hard dependency on these features, you will not be able to upgrade to version 3 of the Azure Search .NET SDK. You can continue to use version 2.0-preview. However, please keep in mind that **we do not recommend using preview SDKs in production applications**. Preview features are for evaluation only and may change.

-## Conclusion

-If you need more details on using the Azure Search .NET SDK, see the [.NET How-to](search-howto-dotnet-sdk.md).

-We welcome your feedback on the SDK. If you encounter problems, feel free to ask us for help on [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-search). If you find a bug, you can file an issue in the [Azure .NET SDK GitHub repository](https://github.com/Azure/azure-sdk-for-net/issues). Make sure to prefix your issue title with "[Azure Search]".

-Thank you for using Azure Search!

-description: This C# quickstart uses the version 10 client library (Microsoft.Azure.Search) to create, load, and query a search index.

-# Quickstart: Create a search index using the legacy Microsoft.Azure.Search v10 client library

-This article is the C# quickstart for the legacy [**Microsoft.Azure.Search**](/dotnet/api/overview/azure/search/client10) (version 10) client library, now superseded by the [**Azure.Search.Documents**](/dotnet/api/overview/azure/search.documents-readme) (version 11) client library.

-> [!NOTE]

-> If you have existing or inflight development projects, you can continue to use version 10. But for new projects, or to use new features, you should transition to the [new library](/dotnet/api/overview/azure/search.documents-readme).

-## About this quickstart

-Create a .NET Core console application in C# that creates, loads, and queries an Azure Cognitive Search index using Visual Studio and the [Microsoft.Azure.Search client libraries](/dotnet/api/overview/azure/search/client10).

-This article explains how to create the application. You could also [download and run the complete application](https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/master/quickstart/v10).

-> [!NOTE]

-> The demo code in this article uses the synchronous methods of the Azure Cognitive Search version 10 .NET SDK for simplicity. However, for production scenarios, we recommend using the asynchronous methods in your own applications to keep them scalable and responsive. For example, you could use `CreateAsync` and `DeleteAsync` instead of `Create` and `Delete`.

-## Prerequisites

-Before you begin, you must have the following:

-+ An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/).

-+ An Azure Cognitive Search service. [Create a service](search-create-service-portal.md) or [find an existing service](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices) under your current subscription. You can use a free service for this quickstart.

-+ [Visual Studio](https://visualstudio.microsoft.com/downloads/), any edition. Sample code and instructions were tested on the free Community edition.

-<a name="get-service-info"></a>

-## Get a key and URL

-Calls to the service require a URL endpoint and an access key on every request. A search service is created with both, so if you added Azure Cognitive Search to your subscription, follow these steps to get the necessary information:

-1. [Sign in to the Azure portal](https://portal.azure.com/), and in your search service **Overview** page, get the URL. An example endpoint might look like `https://mydemo.search.windows.net`.

-2. In **Settings** > **Keys**, get an admin key for full rights on the service. There are two interchangeable admin keys, provided for business continuity in case you need to roll one over. You can use either the primary or secondary key on requests for adding, modifying, and deleting objects.

- Get the query key as well. It's a best practice to issue query requests with read-only access.

-

-All requests require an api-key on every request sent to your service. Having a valid key establishes trust, on a per request basis, between the application sending the request and the service that handles it.

-## Set up your environment

-Begin by opening Visual Studio and creating a new Console App project that can run on .NET Core.

-### Install NuGet packages

-The [Microsoft.Azure.Search package](https://www.nuget.org/packages/Microsoft.Azure.Search/) consists of a few client libraries that are distributed as NuGet packages.

-For this project, use version 10 of the `Microsoft.Azure.Search` NuGet package and the latest `Microsoft.Extensions.Configuration.Json` NuGet package.

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

-1. Click **Browse**.

-1. Search for `Microsoft.Azure.Search` and select version 10.

-1. Click **Install** on the right to add the assembly to your project and solution.

-1. Repeat for `Microsoft.Extensions.Configuration.Json`, selecting version 2.2.0 or later.

-### Add Azure Cognitive Search service information

-1. In Solution Explorer, right click on the project and select **Add** > **New Item...** .

-1. In Add New Item, search for "JSON" to return a JSON-related list of item types.

-1. Choose **JSON File**, name the file "appsettings.json", and click **Add**.

-1. Add the file to your output directory. Right-click appsettings.json and select **Properties**. In **Copy to Output Directory**, select **Copy if newer**.

-1. Copy the following JSON into your new JSON file.

- ```json

- {

- "SearchServiceName": "<YOUR-SEARCH-SERVICE-NAME>",

- "SearchServiceAdminApiKey": "<YOUR-ADMIN-API-KEY>",

- "SearchIndexName": "hotels-quickstart"

- }

- ```

-1. Replace the search service name (YOUR-SEARCH-SERVICE-NAME) and admin API key (YOUR-ADMIN-API-KEY) with valid values. If your service endpoint is `https://mydemo.search.windows.net`, the service name would be "`mydemo`".

-### Add class ".Method" files to your project

-This step is required to produce meaningful output in the console. When printing results to the console window, individual fields from the Hotel object must be returned as strings. This step implements [ToString()](/dotnet/api/system.object.tostring) to perform this task, which you do by copying the necessary code to two new files.

-1. Add two empty class definitions to your project: Address.Methods.cs, Hotel.Methods.cs

-1. In Address.Methods.cs, overwrite the default contents with the following code, [lines 1-25](https://github.com/Azure-Samples/azure-search-dotnet-samples/blob/master/quickstart/v10/AzureSearchQuickstart/Address.Methods.cs#L1-L25).

-1. In Hotel.Methods.cs, copy [lines 1-68](https://github.com/Azure-Samples/azure-search-dotnet-samples/blob/master/quickstart/v10/AzureSearchQuickstart/Hotel.Methods.cs#L1-L68).

-## 1 - Create index

-The hotels index consists of simple and complex fields, where a simple field is "HotelName" or "Description", and complex fields are an address with subfields, or a collection of rooms. When an index includes complex types, isolate the complex field definitions in separate classes.

-1. Add two empty class definitions to your project: Address.cs, Hotel.cs

-1. In Address.cs, overwrite the default contents with the following code:

- ```csharp

- using System;

- using Microsoft.Azure.Search;

- using Microsoft.Azure.Search.Models;

- using Newtonsoft.Json;

- namespace AzureSearchQuickstart

- {

- public partial class Address

- {

- [IsSearchable]

- public string StreetAddress { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string City { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string StateProvince { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string PostalCode { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string Country { get; set; }

- }

- }

- ```

-1. In Hotel.cs, the class defines the overall structure of the index, including references to the address class.

- ```csharp

- namespace AzureSearchQuickstart

- {

- using System;

- using Microsoft.Azure.Search;

- using Microsoft.Azure.Search.Models;

- using Newtonsoft.Json;

- public partial class Hotel

- {

- [System.ComponentModel.DataAnnotations.Key]

- [IsFilterable]

- public string HotelId { get; set; }

- [IsSearchable, IsSortable]

- public string HotelName { get; set; }

- [IsSearchable]

- [Analyzer(AnalyzerName.AsString.EnMicrosoft)]

- public string Description { get; set; }

- [IsSearchable]

- [Analyzer(AnalyzerName.AsString.FrLucene)]

- [JsonProperty("Description_fr")]

- public string DescriptionFr { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string Category { get; set; }

- [IsSearchable, IsFilterable, IsFacetable]

- public string[] Tags { get; set; }

- [IsFilterable, IsSortable, IsFacetable]

- public bool? ParkingIncluded { get; set; }

- [IsFilterable, IsSortable, IsFacetable]

- public DateTimeOffset? LastRenovationDate { get; set; }

- [IsFilterable, IsSortable, IsFacetable]

- public double? Rating { get; set; }

- public Address Address { get; set; }

- }

- }

- ```

- Attributes on the field determine how it is used in an application. For example, the `IsSearchable` attribute must be assigned to every field that should be included in a full text search.

-

- > [!NOTE]

- > In the .NET SDK, fields must be explicitly attributed as [`IsSearchable`](/dotnet/api/microsoft.azure.search.models.field.issearchable), [`IsFilterable`](/dotnet/api/microsoft.azure.search.models.field.isfilterable), [`IsSortable`](/dotnet/api/microsoft.azure.search.models.field.issortable), and [`IsFacetable`](/dotnet/api/microsoft.azure.search.models.field.isfacetable). This behavior is in contrast with the REST API which implicitly enables attribution based on data type (for example, simple string fields are automatically searchable).

- Exactly one field in your index of type `string` must be the *key* field, uniquely identifying each document. In this schema, the key is `HotelId`.

- In this index, the description fields use the optional [`analyzer`](/dotnet/api/microsoft.azure.search.models.field.analyzer) property, specified when you want to override the default standard Lucene analyzer. The `description_fr` field is using the French Lucene analyzer ([FrLucene](/dotnet/api/microsoft.azure.search.models.analyzername.frlucene)) because it stores French text. The `description` is using the optional Microsoft language analyzer ([EnMicrosoft](/dotnet/api/microsoft.azure.search.models.analyzername.enmicrosoft)).

-1. In Program.cs, create an instance of the [`SearchServiceClient`](/dotnet/api/microsoft.azure.search.searchserviceclient) class to connect to the service, using values that are stored in the application's config file (appsettings.json).

- `SearchServiceClient` has an [`Indexes`](/dotnet/api/microsoft.azure.search.searchserviceclient.indexes) property, providing all the methods you need to create, list, update, or delete Azure Cognitive Search indexes.

- ```csharp

- using System;

- using System.Linq;

- using System.Threading;

- using Microsoft.Azure.Search;

- using Microsoft.Azure.Search.Models;

- using Microsoft.Extensions.Configuration;

- namespace AzureSearchQuickstart

- {

- class Program {

- // Demonstrates index delete, create, load, and query

- // Commented-out code is uncommented in later steps

- static void Main(string[] args)

- {

- IConfigurationBuilder builder = new ConfigurationBuilder().AddJsonFile("appsettings.json");

- IConfigurationRoot configuration = builder.Build();

- SearchServiceClient serviceClient = CreateSearchServiceClient(configuration);

- string indexName = configuration["SearchIndexName"];

- Console.WriteLine("{0}", "Deleting index...\n");

- DeleteIndexIfExists(indexName, serviceClient);

- Console.WriteLine("{0}", "Creating index...\n");

- CreateIndex(indexName, serviceClient);

- // Uncomment next 3 lines in "2 - Load documents"

- // ISearchIndexClient indexClient = serviceClient.Indexes.GetClient(indexName);

- // Console.WriteLine("{0}", "Uploading documents...\n");

- // UploadDocuments(indexClient);

- // Uncomment next 2 lines in "3 - Search an index"

- // Console.WriteLine("{0}", "Searching index...\n");

- // RunQueries(indexClient);

- Console.WriteLine("{0}", "Complete. Press any key to end application...\n");

- Console.ReadKey();

- }

- // Create the search service client

- private static SearchServiceClient CreateSearchServiceClient(IConfigurationRoot configuration)

- {

- string searchServiceName = configuration["SearchServiceName"];

- string adminApiKey = configuration["SearchServiceAdminApiKey"];

- SearchServiceClient serviceClient = new SearchServiceClient(searchServiceName, new SearchCredentials(adminApiKey));

- return serviceClient;

- }

- // Delete an existing index to reuse its name

- private static void DeleteIndexIfExists(string indexName, SearchServiceClient serviceClient)

- {

- if (serviceClient.Indexes.Exists(indexName))

- {

- serviceClient.Indexes.Delete(indexName);

- }

- }

- // Create an index whose fields correspond to the properties of the Hotel class.

- // The Address property of Hotel will be modeled as a complex field.

- // The properties of the Address class in turn correspond to sub-fields of the Address complex field.

- // The fields of the index are defined by calling the FieldBuilder.BuildForType() method.

- private static void CreateIndex(string indexName, SearchServiceClient serviceClient)

- {

- var definition = new Microsoft.Azure.Search.Models.Index()

- {

- Name = indexName,

- Fields = FieldBuilder.BuildForType<Hotel>()

- };

- serviceClient.Indexes.Create(definition);

- }

- }

- }

- ```

- If possible, share a single instance of `SearchServiceClient` in your application to avoid opening too many connections. Class methods are thread-safe to enable such sharing.

- The class has several constructors. The one you want takes your search service name and a `SearchCredentials` object as parameters. `SearchCredentials` wraps your api-key.

- In the index definition, the easiest way to create the `Field` objects is by calling the `FieldBuilder.BuildForType` method, passing a model class for the type parameter. A model class has properties that map to the fields of your index. This mapping allows you to bind documents from your search index to instances of your model class.

- > [!NOTE]

- > If you don't plan to use a model class, you can still define your index by creating `Field` objects directly. You can provide the name of the field to the constructor, along with the data type (or analyzer for string fields). You can also set other properties like `IsSearchable`, `IsFilterable`, to name a few.

- >

-1. Press F5 to build the app and create the index.

- If the project builds successfully, a console window opens, writing status messages to the screen for deleting and creating the index.

-<a name="load-documents"></a>

-## 2 - Load documents

-In Azure Cognitive Search, documents are data structures that are both inputs to indexing and outputs from queries. As obtained from an external data source, document inputs might be rows in a database, blobs in Blob storage, or JSON documents on disk. In this example, we're taking a shortcut and embedding JSON documents for four hotels in the code itself.

-When uploading documents, you must use an [`IndexBatch`](/dotnet/api/microsoft.azure.search.models.indexbatch) object. An `IndexBatch` contains a collection of [`IndexAction`](/dotnet/api/microsoft.azure.search.models.indexaction) objects, each of which contains a document and a property telling Azure Cognitive Search what action to perform ([upload, merge, delete, and mergeOrUpload](search-what-is-data-import.md#indexing-actions)).

-1. In Program.cs, create an array of documents and index actions, and then pass the array to `IndexBatch`. The documents below conform to the hotel-quickstart index, as defined by the hotel and address classes.

- ```csharp

- // Upload documents as a batch

- private static void UploadDocuments(ISearchIndexClient indexClient)

- {

- var actions = new IndexAction<Hotel>[]

- {

- IndexAction.Upload(

- new Hotel()

- {

- HotelId = "1",

- HotelName = "Secret Point Motel",

- Description = "The hotel is ideally located on the main commercial artery of the city in the heart of New York. A few minutes away is Time's Square and the historic centre of the city, as well as other places of interest that make New York one of America's most attractive and cosmopolitan cities.",

- DescriptionFr = "L'hôtel est idéalement situé sur la principale artère commerciale de la ville en plein cœur de New York. A quelques minutes se trouve la place du temps et le centre historique de la ville, ainsi que d'autres lieux d'intérêt qui font de New York l'une des villes les plus attractives et cosmopolites de l'Amérique.",

- Category = "Boutique",

- Tags = new[] { "pool", "air conditioning", "concierge" },

- ParkingIncluded = false,

- LastRenovationDate = new DateTimeOffset(1970, 1, 18, 0, 0, 0, TimeSpan.Zero),

- Rating = 3.6,

- Address = new Address()

- {

- StreetAddress = "677 5th Ave",

- City = "New York",

- StateProvince = "NY",

- PostalCode = "10022",

- Country = "USA"

- }

- }

- ),

- IndexAction.Upload(

- new Hotel()

- {

- HotelId = "2",

- HotelName = "Twin Dome Motel",

- Description = "The hotel is situated in a nineteenth century plaza, which has been expanded and renovated to the highest architectural standards to create a modern, functional and first-class hotel in which art and unique historical elements coexist with the most modern comforts.",

- DescriptionFr = "L'hôtel est situé dans une place du XIXe siècle, qui a été agrandie et rénovée aux plus hautes normes architecturales pour créer un hôtel moderne, fonctionnel et de première classe dans lequel l'art et les éléments historiques uniques coexistent avec le confort le plus moderne.",

- Category = "Boutique",

- Tags = new[] { "pool", "free wifi", "concierge" },

- ParkingIncluded = false,

- LastRenovationDate = new DateTimeOffset(1979, 2, 18, 0, 0, 0, TimeSpan.Zero),

- Rating = 3.60,

- Address = new Address()

- {

- StreetAddress = "140 University Town Center Dr",

- City = "Sarasota",

- StateProvince = "FL",

- PostalCode = "34243",

- Country = "USA"

- }

- }

- ),

- IndexAction.Upload(

- new Hotel()

- {

- HotelId = "3",

- HotelName = "Triple Landscape Hotel",

- Description = "The Hotel stands out for its gastronomic excellence under the management of William Dough, who advises on and oversees all of the HotelΓÇÖs restaurant services.",

- DescriptionFr = "L'hôtel est situé dans une place du XIXe siècle, qui a été agrandie et rénovée aux plus hautes normes architecturales pour créer un hôtel moderne, fonctionnel et de première classe dans lequel l'art et les éléments historiques uniques coexistent avec le confort le plus moderne.",

- Category = "Resort and Spa",

- Tags = new[] { "air conditioning", "bar", "continental breakfast" },

- ParkingIncluded = true,

- LastRenovationDate = new DateTimeOffset(2015, 9, 20, 0, 0, 0, TimeSpan.Zero),

- Rating = 4.80,

- Address = new Address()

- {

- StreetAddress = "3393 Peachtree Rd",

- City = "Atlanta",

- StateProvince = "GA",

- PostalCode = "30326",

- Country = "USA"

- }

- }

- ),

- IndexAction.Upload(

- new Hotel()

- {

- HotelId = "4",

- HotelName = "Sublime Cliff Hotel",

- Description = "Sublime Cliff Hotel is located in the heart of the historic center of Sublime in an extremely vibrant and lively area within short walking distance to the sites and landmarks of the city and is surrounded by the extraordinary beauty of churches, buildings, shops and monuments. Sublime Cliff is part of a lovingly restored 1800 palace.",

- DescriptionFr = "Le sublime Cliff Hotel est situé au coeur du centre historique de sublime dans un quartier extrêmement animé et vivant, à courte distance de marche des sites et monuments de la ville et est entouré par l'extraordinaire beauté des églises, des bâtiments, des commerces et Monuments. Sublime Cliff fait partie d'un Palace 1800 restauré avec amour.",

- Category = "Boutique",

- Tags = new[] { "concierge", "view", "24-hour front desk service" },

- ParkingIncluded = true,

- LastRenovationDate = new DateTimeOffset(1960, 2, 06, 0, 0, 0, TimeSpan.Zero),

- Rating = 4.6,

- Address = new Address()

- {

- StreetAddress = "7400 San Pedro Ave",

- City = "San Antonio",

- StateProvince = "TX",

- PostalCode = "78216",

- Country = "USA"

- }

- }

- ),

- };

- var batch = IndexBatch.New(actions);

- try

- {

- indexClient.Documents.Index(batch);

- }

- catch (IndexBatchException e)

- {

- // When a service is under load, indexing might fail for some documents in the batch.

- // Depending on your application, you can compensate by delaying and retrying.

- // For this simple demo, we just log the failed document keys and continue.

- Console.WriteLine(

- "Failed to index some of the documents: {0}",

- String.Join(", ", e.IndexingResults.Where(r => !r.Succeeded).Select(r => r.Key)));

- }

- // Wait 2 seconds before starting queries

- Console.WriteLine("Waiting for indexing...\n");

- Thread.Sleep(2000);

- }

- ```

- Once you initialize the`IndexBatch` object, you can send it to the index by calling [`Documents.Index`](/dotnet/api/microsoft.azure.search.documentsoperationsextensions.index) on your [`SearchIndexClient`](/dotnet/api/microsoft.azure.search.searchindexclient) object. `Documents` is a property of `SearchIndexClient` that provides methods for adding, modifying, deleting, or querying documents in your index.

- The `try`/`catch` surrounding the call to the `Index` method catches indexing failures, which might happen if your service is under heavy load. In production code, you could delay and then retry indexing the documents that failed, or log and continue like the sample does, or handle it in some other way that meets your application's data consistency requirements.

- The 2-second delay compensates for indexing, which is asynchronous, so that all documents can be indexed before the queries are executed. Coding in a delay is typically only necessary in demos, tests, and sample applications.

-1. In Program.cs, in main, uncomment the lines for "2 - Load documents".

- ```csharp

- // Uncomment next 3 lines in "2 - Load documents"

- ISearchIndexClient indexClient = serviceClient.Indexes.GetClient(indexName);

- Console.WriteLine("{0}", "Uploading documents...\n");

- UploadDocuments(indexClient);

- ```

-1. Press F5 to rebuild the app.

- If the project builds successfully, a console window opens, writing status messages, this time with a message about uploading documents. In the Azure portal, in the search service **Overview** page, the hotels-quickstart index should now have 4 documents.

-For more information about document processing, see ["How the .NET SDK handles documents"](search-howto-dotnet-sdk-v10.md#how-dotnet-handles-documents).

-## 3 - Search an index

-You can get query results as soon as the first document is indexed, but actual testing of your index should wait until all documents are indexed.

-This section adds two pieces of functionality: query logic, and results. For queries, use the [`Search`](/dotnet/api/microsoft.azure.search.documentsoperationsextensions.search) method. This method takes search text as well as other [parameters](/dotnet/api/microsoft.azure.search.models.searchparameters).

-The [`DocumentsSearchResult`](/dotnet/api/microsoft.azure.search.models.documentsearchresult-1) class represents the results.

-1. In Program.cs, create a WriteDocuments method that prints search results to the console.

- ```csharp

- private static void WriteDocuments(DocumentSearchResult<Hotel> searchResults)

- {

- foreach (SearchResult<Hotel> result in searchResults.Results)

- {

- Console.WriteLine(result.Document);

- }

- Console.WriteLine();

- }

- ```

-1. Create a RunQueries method to execute queries and return results. Results are Hotel objects. You can use the select parameter to surface individual fields. If a field is not included in the select parameter, its corresponding Hotel property will be null.

- ```csharp

- private static void RunQueries(ISearchIndexClient indexClient)

- {

- SearchParameters parameters;

- DocumentSearchResult<Hotel> results;

- // Query 1

- Console.WriteLine("Query 1: Search for term 'Atlanta' with no result trimming");

- parameters = new SearchParameters();

- results = indexClient.Documents.Search<Hotel>("Atlanta", parameters);

- WriteDocuments(results);

- // Query 2

- Console.WriteLine("Query 2: Search on the term 'Atlanta', with trimming");

- Console.WriteLine("Returning only these fields: HotelName, Tags, Address:\n");

- parameters =

- new SearchParameters()

- {

- Select = new[] { "HotelName", "Tags", "Address" },

- };

- results = indexClient.Documents.Search<Hotel>("Atlanta", parameters);

- WriteDocuments(results);

- // Query 3

- Console.WriteLine("Query 3: Search for the terms 'restaurant' and 'wifi'");

- Console.WriteLine("Return only these fields: HotelName, Description, and Tags:\n");

- parameters =

- new SearchParameters()

- {

- Select = new[] { "HotelName", "Description", "Tags" }

- };

- results = indexClient.Documents.Search<Hotel>("restaurant, wifi", parameters);

- WriteDocuments(results);

- // Query 4 -filtered query

- Console.WriteLine("Query 4: Filter on ratings greater than 4");

- Console.WriteLine("Returning only these fields: HotelName, Rating:\n");

- parameters =

- new SearchParameters()

- {

- Filter = "Rating gt 4",

- Select = new[] { "HotelName", "Rating" }

- };

- results = indexClient.Documents.Search<Hotel>("*", parameters);

- WriteDocuments(results);

- // Query 5 - top 2 results

- Console.WriteLine("Query 5: Search on term 'boutique'");

- Console.WriteLine("Sort by rating in descending order, taking the top two results");

- Console.WriteLine("Returning only these fields: HotelId, HotelName, Category, Rating:\n");

- parameters =

- new SearchParameters()

- {

- OrderBy = new[] { "Rating desc" },

- Select = new[] { "HotelId", "HotelName", "Category", "Rating" },

- Top = 2

- };

- results = indexClient.Documents.Search<Hotel>("boutique", parameters);

- WriteDocuments(results);

- }

- ```

- There are two [ways of matching terms in a query](search-query-overview.md#types-of-queries): full-text search, and filters. A full-text search query searches for one or more terms in `IsSearchable` fields in your index. A filter is a boolean expression that is evaluated over `IsFilterable` fields in an index. You can use full-text search and filters together or separately.

- Both searches and filters are performed using the `Documents.Search` method. A search query can be passed in the `searchText` parameter, while a filter expression can be passed in the `Filter` property of the `SearchParameters` class. To filter without searching, just pass `"*"` for the `searchText` parameter. To search without filtering, just leave the `Filter` property unset, or do not pass in a `SearchParameters` instance at all.

-1. In Program.cs, in main, uncomment the lines for "3 - Search".

- ```csharp

- // Uncomment next 2 lines in "3 - Search an index"

- Console.WriteLine("{0}", "Searching documents...\n");

- RunQueries(indexClient);

- ```

-1. The solution is now finished. Press F5 to rebuild the app and run the program in its entirety.

- Output includes the same messages as before, with addition of query information and results.

-## Clean up resources

-When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources left running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

-You can find and manage resources in the portal, using the **All resources** or **Resource groups** link in the left-navigation pane.

-If you are using a free service, remember that you are limited to three indexes, indexers, and data sources. You can delete individual items in the portal to stay under the limit.

-## Next steps

-In this C# quickstart, you worked through a series of tasks to create an index, load it with documents, and run queries. At different stages, we took shortcuts to simplify the code for readability and comprehension. If you are comfortable with the basic concepts, we recommend the next article for an exploration of alternative approaches and concepts that will deepen your knowledge.

-The sample code and index are expanded versions of this one. The next sample adds a Rooms collection, uses different classes and actions, and takes a closer look at how processing works.

-> [!div class="nextstepaction"]

-> [How to develop in .NET](search-howto-dotnet-sdk.md)

-Want to optimize and save on your cloud spending?

-> [!div class="nextstepaction"]

-> [Start analyzing costs with Cost Management](../cost-management-billing/costs/quick-acm-cost-analysis.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn)

-> Looking for an earlier version? See [Create a search index using Microsoft.Azure.Search v10](search-get-started-dotnet-v10.md) instead.

-> If your search solution is built on earlier workarounds of flattened datasets in a collection, you should change your index to include complex types as supported in the newest API version. For more information about upgrading API versions, see [Upgrade to the newest REST API version](search-api-migration.md) or [Upgrade to the newest .NET SDK version](search-dotnet-sdk-migration-version-9.md).

-description: Learn how to create and manage search objects in a .NET application using C# and Microsoft.Azure.Search (version 10) of the .NET SDK. Code snippets demonstrate connecting to the service, creating indexes, and queries.

-# How to use Microsoft.Azure.Search in a C# .NET application

-This article explains how to create and manage search objects using C# and the legacy client library, [**Microsoft.Azure.Search**](/dotnet/api/overview/azure/search/client10) (version 10) in the Azure SDK for .NET.

-Version 10 is the last version of the Microsoft.Azure.Search package. Moving forward, new features will be rolled out in [**Azure.Search.Documents**](/dotnet/api/overview/azure/search.documents-readme) from the Azure SDK team.

-> [!NOTE]

-> If you have existing or inflight development projects, you can continue to use version 10. For new projects, or to use new features, you should transition to the [new library](/dotnet/api/overview/azure/search.documents-readme).

-## About version 10

-The SDK consists of a few client libraries that enable you to manage your indexes, data sources, indexers, and synonym maps, as well as upload and manage documents, and execute queries, all without having to deal with the details of HTTP and JSON. These client libraries are all distributed as NuGet packages.

-The main NuGet package is `Microsoft.Azure.Search`, which is a meta-package that includes all the other packages as dependencies. Use this package if you're just getting started or if you know your application will need all the features of Azure Cognitive Search.

-The other NuGet packages in the SDK are:

-

- - `Microsoft.Azure.Search.Data`: Use this package if you're developing a .NET application using Azure Cognitive Search, and you only need to query or update documents in your indexes. If you also need to create or update indexes, synonym maps, or other service-level resources, use the `Microsoft.Azure.Search` package instead.

- - `Microsoft.Azure.Search.Service`: Use this package if you're developing automation in .NET to manage Azure Cognitive Search indexes, synonym maps, indexers, data sources, or other service-level resources. If you only need to query or update documents in your indexes, use the `Microsoft.Azure.Search.Data` package instead. If you need all the functionality of Azure Cognitive Search, use the `Microsoft.Azure.Search` package instead.

- - `Microsoft.Azure.Search.Common`: Common types needed by the Azure Cognitive Search .NET libraries. You do not need to use this package directly in your application. It is only meant to be used as a dependency.

-The various client libraries define classes like `Index`, `Field`, and `Document`, as well as operations like `Indexes.Create` and `Documents.Search` on the `SearchServiceClient` and `SearchIndexClient` classes. These classes are organized into the following namespaces:

-* [Microsoft.Azure.Search](/dotnet/api/microsoft.azure.search)

-* [Microsoft.Azure.Search.Models](/dotnet/api/microsoft.azure.search.models)

-If you would like to provide feedback for a future update of the SDK, see our [feedback page](https://feedback.azure.com/d365community/forum/9325d19e-0225-ec11-b6e6-000d3a4f07b8) or create an issue on [GitHub](https://github.com/azure/azure-sdk-for-net/issues) and mention "Azure Cognitive Search" in the issue title.

-The .NET SDK targets version [`2019-05-06` of the Azure Cognitive Search REST API](https://github.com/Azure/azure-rest-api-specs/tree/master/specification/search/data-plane/Microsoft.Azure.Search.Dat) when indexing Azure Blobs.

-This SDK does not support [Management Operations](/rest/api/searchmanagement/) such as creating and scaling Search services and managing API keys. If you need to manage your Search resources from a .NET application, you can use the [Azure Cognitive Search .NET Management SDK](/dotnet/api/overview/azure/search/management).

-## Upgrade to v10

-If you're already using an older version of the Azure Cognitive Search .NET SDK and you'd like to upgrade to the latest generally available version, [this article](search-dotnet-sdk-migration-version-9.md) explains how.

-## SDK requirements

-1. Visual Studio 2017 or later.

-2. Your own Azure Cognitive Search service. In order to use the SDK, you will need the name of your service and one or more API keys. [Create a service in the portal](search-create-service-portal.md) will help you through these steps.

-3. Download the Azure Cognitive Search .NET SDK [NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Search) by using "Manage NuGet Packages" in Visual Studio. Just search for the package name `Microsoft.Azure.Search` on NuGet.org (or one of the other package names above if you only need a subset of the functionality).

-The Azure Cognitive Search .NET SDK supports applications targeting the .NET Framework 4.5.2 and higher, as well as .NET Core 2.0 and higher.

-## Core scenarios

-There are several things you'll need to do in your search application. In this tutorial, we'll cover these core scenarios:

-* Creating an index

-* Populating the index with documents

-* Searching for documents using full-text search and filters

-The following sample code illustrates each of these scenarios. Feel free to use the code snippets in your own application.

-### Overview

-The sample application we'll be exploring creates a new index named "hotels", populates it with a few documents, then executes some search queries. Here is the main program, showing the overall flow:

-```csharp

-// This sample shows how to delete, create, upload documents and query an index

-static void Main(string[] args)

-{

- IConfigurationBuilder builder = new ConfigurationBuilder().AddJsonFile("appsettings.json");

- IConfigurationRoot configuration = builder.Build();

- SearchServiceClient serviceClient = CreateSearchServiceClient(configuration);

- string indexName = configuration["SearchIndexName"];

- Console.WriteLine("{0}", "Deleting index...\n");

- DeleteIndexIfExists(indexName, serviceClient);

- Console.WriteLine("{0}", "Creating index...\n");

- CreateIndex(indexName, serviceClient);

- ISearchIndexClient indexClient = serviceClient.Indexes.GetClient(indexName);

- Console.WriteLine("{0}", "Uploading documents...\n");

- UploadDocuments(indexClient);

- ISearchIndexClient indexClientForQueries = CreateSearchIndexClient(configuration);

- RunQueries(indexClientForQueries);

- Console.WriteLine("{0}", "Complete. Press any key to end application...\n");

- Console.ReadKey();

-}

-```

-> [!NOTE]

-> You can find the full source code of the sample application used in this walk through on [GitHub](https://github.com/Azure-Samples/search-dotnet-getting-started/tree/master/DotNetHowTo).

->

->

-We'll walk through this step by step. First we need to create a new `SearchServiceClient`. This object allows you to manage indexes. In order to construct one, you need to provide your Azure Cognitive Search service name as well as an admin API key. You can enter this information in the `appsettings.json` file of the [sample application](https://github.com/Azure-Samples/search-dotnet-getting-started/tree/master/DotNetHowTo).

-```csharp

-private static SearchServiceClient CreateSearchServiceClient(IConfigurationRoot configuration)

-{

- string searchServiceName = configuration["SearchServiceName"];

- string adminApiKey = configuration["SearchServiceAdminApiKey"];

- SearchServiceClient serviceClient = new SearchServiceClient(searchServiceName, new SearchCredentials(adminApiKey));

- return serviceClient;

-}

-```

-> [!NOTE]

-> If you provide an incorrect key (for example, a query key where an admin key was required), the `SearchServiceClient` will throw a `CloudException` with the error message "Forbidden" the first time you call an operation method on it, such as `Indexes.Create`. If this happens to you, double-check our API key.

->

->

-The next few lines call methods to create an index named "hotels", deleting it first if it already exists. We will walk through these methods a little later.

-```csharp

-Console.WriteLine("{0}", "Deleting index...\n");

-DeleteIndexIfExists(indexName, serviceClient);

-Console.WriteLine("{0}", "Creating index...\n");

-CreateIndex(indexName, serviceClient);

-```

-Next, the index needs to be populated. To do populate the index, we will need a `SearchIndexClient`. There are two ways to obtain one: by constructing it, or by calling `Indexes.GetClient` on the `SearchServiceClient`. We use the latter for convenience.

-```csharp

-ISearchIndexClient indexClient = serviceClient.Indexes.GetClient(indexName);

-```

-> [!NOTE]

-> In a typical search application, index management and population may be handled by a separate component from search queries. `Indexes.GetClient` is convenient for populating an index because it saves you the trouble of providing additional `SearchCredentials`. It does this by passing the admin key that you used to create the `SearchServiceClient` to the new `SearchIndexClient`. However, in the part of your application that executes queries, it is better to create the `SearchIndexClient` directly so that you can pass in a query key, which only allows you to read data, instead of an admin key. This is consistent with the principle of least privilege and will help to make your application more secure. You can find out more about admin keys and query keys [here](/rest/api/searchservice/#authentication-and-authorization).

->

->

-Now that we have a `SearchIndexClient`, we can populate the index. Index population is done by another method that we will walk through later.

-```csharp

-Console.WriteLine("{0}", "Uploading documents...\n");

-UploadDocuments(indexClient);

-```

-Finally, we execute a few search queries and display the results. This time we use a different `SearchIndexClient`:

-```csharp

-ISearchIndexClient indexClientForQueries = CreateSearchIndexClient(indexName, configuration);

-RunQueries(indexClientForQueries);

-```

-We will take a closer look at the `RunQueries` method later. Here is the code to create the new `SearchIndexClient`:

-```csharp

-private static SearchIndexClient CreateSearchIndexClient(string indexName, IConfigurationRoot configuration)

-{

- string searchServiceName = configuration["SearchServiceName"];

- string queryApiKey = configuration["SearchServiceQueryApiKey"];

- SearchIndexClient indexClient = new SearchIndexClient(searchServiceName, indexName, new SearchCredentials(queryApiKey));

- return indexClient;

-}

-```

-This time we use a query key since we do not need write access to the index. You can enter this information in the `appsettings.json` file of the [sample application](https://github.com/Azure-Samples/search-dotnet-getting-started/tree/master/DotNetHowTo).

-If you run this application with a valid service name and API keys, the output should look like this example:

-(Some console output has been replaced with "..." for illustration purposes.)

-```output

-Deleting index...

-Creating index...

-Uploading documents...

-Waiting for documents to be indexed...

-Search the entire index for the term 'motel' and return only the HotelName field:

-Name: Secret Point Motel

-Name: Twin Dome Motel

-Apply a filter to the index to find hotels with a room cheaper than $100 per night, and return the hotelId and description:

-HotelId: 1

-Description: The hotel is ideally located on the main commercial artery of the city in the heart of New York. A few minutes away is Times Square and the historic centre of the city, as well as other places of interest that make New York one of America's most attractive and cosmopolitan cities.

-HotelId: 2

-Description: The hotel is situated in a nineteenth century plaza, which has been expanded and renovated to the highest architectural standards to create a modern, functional and first-class hotel in which art and unique historical elements coexist with the most modern comforts.

-Search the entire index, order by a specific field (lastRenovationDate) in descending order, take the top two results, and show only hotelName and lastRenovationDate:

-Name: Triple Landscape Hotel

-Last renovated on: 9/20/2015 12:00:00 AM +00:00

-Name: Twin Dome Motel

-Last renovated on: 2/18/1979 12:00:00 AM +00:00

-Search the hotel names for the term 'hotel':

-HotelId: 3

-Name: Triple Landscape Hotel

-...

-Complete. Press any key to end application...

-```

-The full source code of the application is provided at the end of this article.

-Next, we will take a closer look at each of the methods called by `Main`.

-### Creating an index

-After creating a `SearchServiceClient`, `Main` deletes the "hotels" index if it already exists. That deletion is done by the following method:

-```csharp

-private static void DeleteIndexIfExists(string indexName, SearchServiceClient serviceClient)

-{

- if (serviceClient.Indexes.Exists(indexName))

- {

- serviceClient.Indexes.Delete(indexName);

- }

-}

-```

-This method uses the given `SearchServiceClient` to check if the index exists, and if so, delete it.

-> [!NOTE]

-> The example code in this article uses the synchronous methods of the Azure Cognitive Search .NET SDK for simplicity. We recommend that you use the asynchronous methods in your own applications to keep them scalable and responsive. For example, in the method above you could use `ExistsAsync` and `DeleteAsync` instead of `Exists` and `Delete`.

->

->

-Next, `Main` creates a new "hotels" index by calling this method:

-```csharp

-private static void CreateIndex(string indexName, SearchServiceClient serviceClient)

-{

- var definition = new Index()

- {

- Name = indexName,

- Fields = FieldBuilder.BuildForType<Hotel>()

- };

-

- serviceClient.Indexes.Create(definition);

-}

-```

-This method creates a new `Index` object with a list of `Field` objects that defines the schema of the new index. Each field has a name, data type, and several attributes that define its search behavior. The `FieldBuilder` class uses reflection to create a list of `Field` objects for the index by examining the public properties and attributes of the given `Hotel` model class. We'll take a closer look at the `Hotel` class later on.

-> [!NOTE]

-> You can always create the list of `Field` objects directly instead of using `FieldBuilder` if needed. For example, you may not want to use a model class or you may need to use an existing model class that you don't want to modify by adding attributes.

->

->

-In addition to fields, you can also add scoring profiles, suggesters, or CORS options to the Index (these parameters are omitted from the sample for brevity). You can find more information about the Index object and its constituent parts in the [SDK reference](/dotnet/api/microsoft.azure.search.models.index), as well as in the [Azure Cognitive Search REST API reference](/rest/api/searchservice/).

-### Populating the index

-The next step in `Main` populates the newly-created index. This index population is done in the following method:

-(Some code replaced with "..." for illustration purposes. See the full sample solution for the full data population code.)

-```csharp

-private static void UploadDocuments(ISearchIndexClient indexClient)

-{

- var hotels = new Hotel[]

- {

- new Hotel()

- {

- HotelId = "1",

- HotelName = "Secret Point Motel",

- ...

- Address = new Address()

- {

- StreetAddress = "677 5th Ave",

- ...

- },

- Rooms = new Room[]

- {

- new Room()

- {

- Description = "Budget Room, 1 Queen Bed (Cityside)",

- ...

- },

- new Room()

- {

- Description = "Budget Room, 1 King Bed (Mountain View)",

- ...

- },

- new Room()

- {

- Description = "Deluxe Room, 2 Double Beds (City View)",

- ...

- }

- }

- },

- new Hotel()

- {

- HotelId = "2",

- HotelName = "Twin Dome Motel",

- ...

- {

- StreetAddress = "140 University Town Center Dr",

- ...

- },

- Rooms = new Room[]

- {

- new Room()

- {

- Description = "Suite, 2 Double Beds (Mountain View)",

- ...

- },

- new Room()

- {

- Description = "Standard Room, 1 Queen Bed (City View)",

- ...

- },

- new Room()

- {

- Description = "Budget Room, 1 King Bed (Waterfront View)",

- ...

- }

- }

- },

- new Hotel()

- {

- HotelId = "3",

- HotelName = "Triple Landscape Hotel",

- ...

- Address = new Address()

- {

- StreetAddress = "3393 Peachtree Rd",

- ...

- },

- Rooms = new Room[]

- {

- new Room()

- {

- Description = "Standard Room, 2 Queen Beds (Amenities)",

- ...

- },

- new Room ()

- {

- Description = "Standard Room, 2 Double Beds (Waterfront View)",

- ...

- },

- new Room()

- {

- Description = "Deluxe Room, 2 Double Beds (Cityside)",

- ...

- }

- }

- }

- };

- var batch = IndexBatch.Upload(hotels);

- try

- {

- indexClient.Documents.Index(batch);

- }

- catch (IndexBatchException e)

- {

- // Sometimes when your Search service is under load, indexing will fail for some of the documents in

- // the batch. Depending on your application, you can take compensating actions like delaying and

- // retrying. For this simple demo, we just log the failed document keys and continue.

- Console.WriteLine(

- "Failed to index some of the documents: {0}",

- String.Join(", ", e.IndexingResults.Where(r => !r.Succeeded).Select(r => r.Key)));

- }

- Console.WriteLine("Waiting for documents to be indexed...\n");

- Thread.Sleep(2000);

-}

-```

-This method has four parts. The first creates an array of 3 `Hotel` objects each with 3 `Room` objects that will serve as our input data to upload to the index. This data is hard-coded for simplicity. In your own application, your data will likely come from an external data source such as a SQL database.

-The second part creates an `IndexBatch` containing the documents. You specify the operation you want to apply to the batch at the time you create it, in this case by calling `IndexBatch.Upload`. The batch is then uploaded to the Azure Cognitive Search index by the `Documents.Index` method.

-> [!NOTE]

-> In this example, we are just uploading documents. If you wanted to merge changes into existing documents or delete documents, you could create batches by calling `IndexBatch.Merge`, `IndexBatch.MergeOrUpload`, or `IndexBatch.Delete` instead. You can also mix different operations in a single batch by calling `IndexBatch.New`, which takes a collection of `IndexAction` objects, each of which tells Azure Cognitive Search to perform a particular operation on a document. You can create each `IndexAction` with its own operation by calling the corresponding method such as `IndexAction.Merge`, `IndexAction.Upload`, and so on.

->

->

-The third part of this method is a catch block that handles an important error case for indexing. If your Azure Cognitive Search service fails to index some of the documents in the batch, an `IndexBatchException` is thrown by `Documents.Index`. This exception can happen if you are indexing documents while your service is under heavy load. **We strongly recommend explicitly handling this case in your code.** You can delay and then retry indexing the documents that failed, or you can log and continue like the sample does, or you can do something else depending on your application's data consistency requirements.

-> [!NOTE]

-> You can use the [`FindFailedActionsToRetry`](/dotnet/api/microsoft.azure.search.indexbatchexception.findfailedactionstoretry) method to construct a new batch containing only the actions that failed in a previous call to `Index`. There is a discussion of how to properly use it [on StackOverflow](https://stackoverflow.com/questions/40012885/azure-search-net-sdk-how-to-use-findfailedactionstoretry).

->

->

-Finally, the `UploadDocuments` method delays for two seconds. Indexing happens asynchronously in your Azure Cognitive Search service, so the sample application needs to wait a short time to ensure that the documents are available for searching. Delays like this are typically only necessary in demos, tests, and sample applications.

-<a name="how-dotnet-handles-documents"></a>

-#### How the .NET SDK handles documents

-You may be wondering how the Azure Cognitive Search .NET SDK is able to upload instances of a user-defined class like `Hotel` to the index. To help answer that question, let's look at the `Hotel` class:

-```csharp

-using System;

-using Microsoft.Azure.Search;

-using Microsoft.Azure.Search.Models;

-using Microsoft.Spatial;

-using Newtonsoft.Json;

-public partial class Hotel

-{

- [System.ComponentModel.DataAnnotations.Key]

- [IsFilterable]

- public string HotelId { get; set; }

- [IsSearchable, IsSortable]

- public string HotelName { get; set; }

- [IsSearchable]

- [Analyzer(AnalyzerName.AsString.EnLucene)]

- public string Description { get; set; }

- [IsSearchable]

- [Analyzer(AnalyzerName.AsString.FrLucene)]

- [JsonProperty("Description_fr")]

- public string DescriptionFr { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string Category { get; set; }

- [IsSearchable, IsFilterable, IsFacetable]

- public string[] Tags { get; set; }

- [IsFilterable, IsSortable, IsFacetable]

- public bool? ParkingIncluded { get; set; }

- // SmokingAllowed reflects whether any room in the hotel allows smoking.

- // The JsonIgnore attribute indicates that a field should not be created

- // in the index for this property and it will only be used by code in the client.

- [JsonIgnore]

- public bool? SmokingAllowed => (Rooms != null) ? Array.Exists(Rooms, element => element.SmokingAllowed == true) : (bool?)null;

- [IsFilterable, IsSortable, IsFacetable]

- public DateTimeOffset? LastRenovationDate { get; set; }

- [IsFilterable, IsSortable, IsFacetable]

- public double? Rating { get; set; }

- public Address Address { get; set; }

- [IsFilterable, IsSortable]

- public GeographyPoint Location { get; set; }

- public Room[] Rooms { get; set; }

-}

-```

-The first thing to notice is that the name of each public property in the `Hotel` class will map to a field with the same name in the index definition. If you would like each field to start with a lower-case letter ("camel case"), you can tell the SDK to map the property names to camel-case automatically with the `[SerializePropertyNamesAsCamelCase]` attribute on the class. This scenario is common in .NET applications that perform data-binding where the target schema is outside the control of the application developer without having to violate the "Pascal case" naming guidelines in .NET.

-> [!NOTE]

-> The Azure Cognitive Search .NET SDK uses the [NewtonSoft JSON.NET](https://www.newtonsoft.com/json/help/html/Introduction.htm) library to serialize and deserialize your custom model objects to and from JSON. You can customize this serialization if needed. For more information, see [Custom Serialization with JSON.NET](#JsonDotNet).

->

->

-The second thing to notice is each property is decorated with attributes such as `IsFilterable`, `IsSearchable`, `Key`, and `Analyzer`. These attributes map directly to the [corresponding field attributes in an Azure Cognitive Search index](/rest/api/searchservice/create-index). The `FieldBuilder` class uses these properties to construct field definitions for the index.

-The third important thing about the `Hotel` class is the data types of the public properties. The .NET types of these properties map to their equivalent field types in the index definition. For example, the `Category` string property maps to the `category` field, which is of type `Edm.String`. There are similar type mappings between `bool?`, `Edm.Boolean`, `DateTimeOffset?`, and `Edm.DateTimeOffset` and so on. The specific rules for the type mapping are documented with the `Documents.Get` method in the [Azure Cognitive Search .NET SDK reference](/dotnet/api/microsoft.azure.search.documentsoperationsextensions.get). The `FieldBuilder` class takes care of this mapping for you, but it can still be helpful to understand in case you need to troubleshoot any serialization issues.

-Did you happen to notice the `SmokingAllowed` property?

-```csharp

-[JsonIgnore]

-public bool? SmokingAllowed => (Rooms != null) ? Array.Exists(Rooms, element => element.SmokingAllowed == true) : (bool?)null;

-```

-The `JsonIgnore` attribute on this property tells the `FieldBuilder` to not serialize it to the index as a field. This is a great way to create client-side calculated properties you can use as helpers in your application. In this case, the `SmokingAllowed` property reflects whether any `Room` in the `Rooms` collection allows smoking. If all are false, it indicates that the entire hotel does not allow smoking.

-Some properties such as `Address` and `Rooms` are instances of .NET classes. These properties represent more complex data structures and, as a result, require fields with a [complex data type](./search-howto-complex-data-types.md) in the index.

-The `Address` property represents a set of multiple values in the `Address` class, defined below:

-```csharp

-using System;

-using Microsoft.Azure.Search;

-using Microsoft.Azure.Search.Models;

-using Newtonsoft.Json;

-namespace AzureSearch.SDKHowTo

-{

- public partial class Address

- {

- [IsSearchable]

- public string StreetAddress { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string City { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string StateProvince { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string PostalCode { get; set; }

- [IsSearchable, IsFilterable, IsSortable, IsFacetable]

- public string Country { get; set; }

- }

-}

-```

-This class contains the standard values used to describe addresses in the United States or Canada. You can use types like this to group logical fields together in the index.

-The `Rooms` property represents an array of `Room` objects:

-```csharp

-using System;

-using Microsoft.Azure.Search;

-using Microsoft.Azure.Search.Models;

-using Newtonsoft.Json;

-namespace AzureSearch.SDKHowTo

-{

- public partial class Room

- {

- [IsSearchable]

- [Analyzer(AnalyzerName.AsString.EnMicrosoft)]

- public string Description { get; set; }

- [IsSearchable]

- [Analyzer(AnalyzerName.AsString.FrMicrosoft)]

- [JsonProperty("Description_fr")]

- public string DescriptionFr { get; set; }

- [IsSearchable, IsFilterable, IsFacetable]

- public string Type { get; set; }

- [IsFilterable, IsFacetable]

- public double? BaseRate { get; set; }

- [IsSearchable, IsFilterable, IsFacetable]

- public string BedOptions { get; set; }

- [IsFilterable, IsFacetable]

- public int SleepsCount { get; set; }

- [IsFilterable, IsFacetable]

- public bool? SmokingAllowed { get; set; }

- [IsSearchable, IsFilterable, IsFacetable]

- public string[] Tags { get; set; }

- }

-}

-```

-Your data model in .NET and its corresponding index schema should be designed to support the search experience you'd like to give to your end user. Each top level object in .NET, ie document in the index, corresponds to a search result you would present in your user interface. For example, in a hotel search application your end users may want to search by hotel name, features of the hotel, or the characteristics of a particular room. We'll cover some query examples a little later.

-This ability to use your own classes to interact with documents in the index works in both directions; You can also retrieve search results and have the SDK automatically deserialize them to a type of your choice, as we will see in the next section.

-> [!NOTE]

-> The Azure Cognitive Search .NET SDK also supports dynamically-typed documents using the `Document` class, which is a key/value mapping of field names to field values. This is useful in scenarios where you don't know the index schema at design-time, or where it would be inconvenient to bind to specific model classes. All the methods in the SDK that deal with documents have overloads that work with the `Document` class, as well as strongly-typed overloads that take a generic type parameter. Only the latter are used in the sample code in this tutorial. The [`Document` class](/dotnet/api/microsoft.azure.search.models.document) inherits from `Dictionary<string, object>`.

->

->

-**Why you should use nullable data types**

-When designing your own model classes to map to an Azure Cognitive Search index, we recommend declaring properties of value types such as `bool` and `int` to be nullable (for example, `bool?` instead of `bool`). If you use a non-nullable property, you have to **guarantee** that no documents in your index contain a null value for the corresponding field. Neither the SDK nor the Azure Cognitive Search service will help you to enforce this.

-This is not just a hypothetical concern: Imagine a scenario where you add a new field to an existing index that is of type `Edm.Int32`. After updating the index definition, all documents will have a null value for that new field (since all types are nullable in Azure Cognitive Search). If you then use a model class with a non-nullable `int` property for that field, you will get a `JsonSerializationException` like this when trying to retrieve documents:

-```output

-Error converting value {null} to type 'System.Int32'. Path 'IntValue'.

-```

-For this reason, we recommend that you use nullable types in your model classes as a best practice.

-<a name="JsonDotNet"></a>

-#### Custom Serialization with JSON.NET

-The SDK uses JSON.NET for serializing and deserializing documents. You can customize serialization and deserialization if needed by defining your own `JsonConverter` or `IContractResolver`. For more information, see the [JSON.NET documentation](https://www.newtonsoft.com/json/help/html/Introduction.htm). This can be useful when you want to adapt an existing model class from your application for use with Azure Cognitive Search, and other more advanced scenarios. For example, with custom serialization you can:

-* Include or exclude certain properties of your model class from being stored as document fields.

-* Map between property names in your code and field names in your index.

-* Create custom attributes that can be used for mapping properties to document fields.

-You can find examples of implementing custom serialization in the unit tests for the Azure Cognitive Search .NET SDK on GitHub. A good starting point is [this folder](https://github.com/Azure/azure-sdk-for-net/tree/4f6f4e4c90200c1b0621c4cead302a91e89f2aba/sdk/search/Microsoft.Azure.Search/tests/Tests/Models). It contains classes that are used by the custom serialization tests.

-### Searching for documents in the index

-The last step in the sample application is to search for some documents in the index:

-```csharp

-private static void RunQueries(ISearchIndexClient indexClient)

-{

- SearchParameters parameters;

- DocumentSearchResult<Hotel> results;

- Console.WriteLine("Search the entire index for the term 'motel' and return only the HotelName field:\n");

- parameters =

- new SearchParameters()

- {

- Select = new[] { "HotelName" }

- };

- results = indexClient.Documents.Search<Hotel>("motel", parameters);

- WriteDocuments(results);

- Console.Write("Apply a filter to the index to find hotels with a room cheaper than $100 per night, ");

- Console.WriteLine("and return the hotelId and description:\n");

- parameters =

- new SearchParameters()

- {

- Filter = "Rooms/any(r: r/BaseRate lt 100)",

- Select = new[] { "HotelId", "Description" }

- };

- results = indexClient.Documents.Search<Hotel>("*", parameters);

- WriteDocuments(results);

- Console.Write("Search the entire index, order by a specific field (lastRenovationDate) ");

- Console.Write("in descending order, take the top two results, and show only hotelName and ");

- Console.WriteLine("lastRenovationDate:\n");

- parameters =

- new SearchParameters()

- {

- OrderBy = new[] { "LastRenovationDate desc" },

- Select = new[] { "HotelName", "LastRenovationDate" },

- Top = 2

- };

- results = indexClient.Documents.Search<Hotel>("*", parameters);

- WriteDocuments(results);

- Console.WriteLine("Search the entire index for the term 'hotel':\n");

- parameters = new SearchParameters();

- results = indexClient.Documents.Search<Hotel>("hotel", parameters);

- WriteDocuments(results);

-}

-```

-Each time it executes a query, this method first creates a new `SearchParameters` object. This object is used to specify additional options for the query such as sorting, filtering, paging, and faceting. In this method, we're setting the `Filter`, `Select`, `OrderBy`, and `Top` property for different queries. All the `SearchParameters` properties are documented [here](/dotnet/api/microsoft.azure.search.models.searchparameters).

-The next step is to actually execute the search query. Running the search is done using the `Documents.Search` method. For each query, we pass the search text to use as a string (or `"*"` if there is no search text), plus the search parameters created earlier. We also specify `Hotel` as the type parameter for `Documents.Search`, which tells the SDK to deserialize documents in the search results into objects of type `Hotel`.

-> [!NOTE]

-> You can find more information about the search query expression syntax [here](/rest/api/searchservice/Simple-query-syntax-in-Azure-Search).

->

->

-Finally, after each query this method iterates through all the matches in the search results, printing each document to the console:

-```csharp

-private static void WriteDocuments(DocumentSearchResult<Hotel> searchResults)

-{

- foreach (SearchResult<Hotel> result in searchResults.Results)

- {

- Console.WriteLine(result.Document);

- }

- Console.WriteLine();

-}

-```

-Let's take a closer look at each of the queries in turn. Here is the code to execute the first query:

-```csharp

-parameters =

- new SearchParameters()

- {

- Select = new[] { "HotelName" }

- };

-results = indexClient.Documents.Search<Hotel>("motel", parameters);

-WriteDocuments(results);

-```

-In this case, we're searching the entire index for the word "motel" in any searchable field and we only want to retrieve the hotel names, as specified by the `Select` parameter. Here are the results:

-```output

-Name: Secret Point Motel

-Name: Twin Dome Motel

-```

-The next query is a little more interesting. We want to find any hotels that have a room with a nightly rate of less than $100 and return only the hotel ID and description:

-```csharp

-parameters =

- new SearchParameters()

- {

- Filter = "Rooms/any(r: r/BaseRate lt 100)",

- Select = new[] { "HotelId", "Description" }

- };

-results = indexClient.Documents.Search<Hotel>("*", parameters);

-WriteDocuments(results);

-```

-This query uses an OData `$filter` expression, `Rooms/any(r: r/BaseRate lt 100)`, to filter the documents in the index. This uses the [any operator](./search-query-odata-collection-operators.md) to apply the 'BaseRate lt 100' to every item in the Rooms collection. You can find out more about the OData syntax that Azure Cognitive Search supports [here](./query-odata-filter-orderby-syntax.md).

-Here are the results of the query:

-```output

-HotelId: 1

-Description: The hotel is ideally located on the main commercial artery of the city in the heart of New York...

-HotelId: 2

-Description: The hotel is situated in a nineteenth century plaza, which has been expanded and renovated to...

-```

-Next, we want to find the top two hotels that have been most recently renovated, and show the hotel name and last renovation date. Here is the code:

-```csharp

-parameters =

- new SearchParameters()

- {

- OrderBy = new[] { "LastRenovationDate desc" },

- Select = new[] { "HotelName", "LastRenovationDate" },

- Top = 2

- };

-results = indexClient.Documents.Search<Hotel>("*", parameters);

-WriteDocuments(results);

-```

-In this case, we again use OData syntax to specify the `OrderBy` parameter as `lastRenovationDate desc`. We also set `Top` to 2 to ensure we only get the top two documents. As before, we set `Select` to specify which fields should be returned.

-Here are the results:

-```output

-Name: Fancy Stay Last renovated on: 6/27/2010 12:00:00 AM +00:00

-Name: Roach Motel Last renovated on: 4/28/1982 12:00:00 AM +00:00

-```

-Finally, we want to find all hotels names that match the word "hotel":

-```csharp

-parameters = new SearchParameters()

-{

- SearchFields = new[] { "HotelName" }

-};

-results = indexClient.Documents.Search<Hotel>("hotel", parameters);

-WriteDocuments(results);

-```

-And here are the results, which include all fields since we did not specify the `Select` property:

-```output

- HotelId: 3

- Name: Triple Landscape Hotel

- ...

-```

-This step completes the tutorial, but don't stop here. **Next steps provide additional resources for learning more about Azure Cognitive Search.

-## Next steps

-* Browse the references for the [.NET SDK](/dotnet/api/microsoft.azure.search) and [REST API](/rest/api/searchservice/).

-* Review [naming conventions](/rest/api/searchservice/Naming-rules) to learn the rules for naming various objects.

-* Review [supported data types](/rest/api/searchservice/Supported-data-types) in Azure Cognitive Search.

-Microsoft uses best practice procedures and a wiping solution that is [NIST 800-88 compliant](https://csrc.nist.gov/publications/detail/sp/800-88/archive/2006-09-01). For hard drives that canΓÇÖt be wiped, we use a destruction process that destroys it and renders the recovery of information impossible. This destruction process can be to disintegrate, shred, pulverize, or incinerate. We determine the means of disposal according to the asset type. We retain records of the destruction.

- "field": " Microsoft.ServiceBus/namespaces/minimumTlsVersion",

- "equals": " Microsoft.ServiceBus/namespaces"

- "field": " Microsoft.ServiceBus/namespaces/minimumTlsVersion",

-> If the VMs are behind a **Standard** internal load balancer, by default, it wouldn't have access to the Microsoft 365 IPs such as `login.microsoftonline.com`. For outbound access create an Azure NAT gateway. For more information see [Tutorial: Create a NAT gateway - Azure CLI](../virtual-network/nat-gateway/tutorial-create-nat-gateway-cli.md).

-[Replicate Azure VMs to another Azure region](azure-to-azure-how-to-enable-replication.md)

- - name: Checkout Github Action

- - name: Checkout Github Action

- # [Azure [portal](#tab/azure-portal)

-Service registration and discovery are key requirements for maintaining a list of live app instances to call, and routing and load balancing inbound requests. Configuring each client manually takes time and introduces the possibility of human error. Managed Spring Cloud Service Registry (OSS) in Azure Spring Cloud solves this problem. Once configured, a Service Registry server will control service registration and discovery for your applications. The Service Registry server maintains a registry of live app instances, enables client-side load-balancing, and decouples service providers from clients without relying on DNS.

-Before your application can manage service registration and discovery using Spring Cloud Service Registry, you must include the dependency for *spring-cloud-starter-netflix-eureka-client* to your *pom.xml*

- <dependency>

- <groupId>org.springframework.cloud</groupId>

- <artifactId>spring-cloud-starter-netflix-eureka-client</artifactId>

- </dependency>

-Finally, we add an annotation to the top level class of your application

- ```java

- package foo.bar;

- import org.springframework.boot.SpringApplication;

- import org.springframework.boot.autoconfigure.SpringBootApplication;

- import org.springframework.cloud.netflix.eureka.EnableEurekaClient;

- @SpringBootApplication

- @EnableEurekaClient

- public class DemoApplication {

- public static void main(String[] args) {

- SpringApplication.run(DemoApplication.class, args);

- }

- ```

-Note that it can take a few minutes for the changes to propagate from the server to all applications.

-| [Customer-provided keys (encryption)](encryption-customer-provided-keys.md) |  |  |  |  |

-| [Customer-provided keys (encryption)](encryption-customer-provided-keys.md) |  |  |  |  |

-To enable access from a virtual network that is located in another region, register the `AllowGlobalTagsForStorage` feature in the subscription of the virtual network. Subnets in other regions which have storage service endpoints will no longer use a public IP address to communicate with the storage account. All traffic will originate from a private IP address and any IP network rules that permit traffic from those subnets will no longer have an effect.

-> You can tweak your download operation by using optional flags. Here's a few examples.

-In Azure File Sync, the only resource capable of moving is the Storage Sync Service resource. Any subresources are bound to its parent and cannot move to another Storage Sync Service.

-In Azure Storage, the only resource capable of moving is the storage account. An Azure file share, as a subresource, cannot move to a different storage account.

-Individual resources like a Storage Sync Service or storage accounts, cannot move by themselves to a different AAD tenant. Only Azure subscriptions can move AAD tenants. Think about your subscription structure in the new AAD tenant. You can use a dedicated subscription for Azure File Sync.

-Once all related Azure File Sync resources have been sequestered into their own subscription, you are ready to move the entire subscription to the target AAD tenant. The [transfer subscription guide](../../role-based-access-control/transfer-subscription.md) allows you to plan and execute such a transfer.

-When storage accounts are moved to either a new subscription or are moved within a subscription to a new Azure Active Directory (AAD) tenant, sync will stop. Role-based access (RBAC) is used to authorize Azure File Sync to access a storage account and these role assignments are not migrated with the resources.

-The Azure File Sync resource *Storage Sync Service* and the storage accounts that contain file shares that are syncing, have an Azure region they are deployed in. You determine that region when you create a resource. The region of the Storage Sync Service and storage account resources must match. These regions cannot be changed on either resource type after their creation.

-Assigning a different region to a resource is different from a [region fail-over](#region-fail-over), which can be supported, depending on your storage account redundancy setting.

-[Azure storage offers geo-redundancy options](../common/storage-redundancy.md#geo-redundant-storage) for a storage account. These redundancy options can pose problems for storage accounts used with Azure File Sync. The main reason is that replication between geographically distant regions is not performed by Azure File Sync, but by a storage replication technology built-in to the storage subsystem in Azure. It cannot have an understanding of application state and Azure File Sync is an application with files syncing to and from Azure file shares at any given moment. If you opt for any of these geographically disbursed storage redundancy options, you won't lose all of your data in a large-scale disaster. However, you need to [anticipate data loss](../common/storage-disaster-recovery-guidance.md#anticipate-data-loss).

-> Fail-over is never an appropriate substitute to provisioning your resources in the correct Azure region. If your resources are in the "wrong" region, you need to consider stopping sync and setting sync up again to new Azure file shares that are deployed in your desired region.

-A regional fail-over can be started by Microsoft in a catastrophic event that will render data centers in an Azure region incapacitated for an extended period of time. The definition of downtime your business can sustain might be less than the time Microsoft is prepared to let pass before starting a regional fail-over. For a situation like that, [fail-overs can also be initiated by customers](../common/storage-initiate-account-failover.md).

-> In the event of a fail-over, you need to file a support ticket for your impacted Storage Sync Services for sync to work again.

-Check that idmapping is disabled and nothing is re-enabling it, then perform the following:

-Double encryption is not supported for NFS shares yet. Azure provides a layer of encryption for all data in transit between Azure datacenters using MACSec. NFS shares can only be accessed from trusted virtual networks and over VPN tunnels. No additional transport layer encryption is available on NFS shares.

-If the package is not installed, install the package on your distribution.

-Verify that port 2049 is open on your client by running the following command: `telnet <storageaccountnamehere>.file.core.windows.net 2049`. If the port is not open, open it.

-Some kernel versions have a bug which causes directory listings to result in an endless READDIR sequence. Very small directories where all entries can be shipped in one call will not have the problem.

-| [az storage blob list](/cli/azure/storage/account/keys) | Lists the blobs in an Azure Blob storage container. |

-For more information about Azure virtual networks, see [Azure virtual networks overview](../virtual-network/virtual-networks-overview.md).

-> [Compare the API differences between Uniform and Flexible orchestration modes.](../virtual-machine-scale-sets/orchestration-modes-api-comparison.md)

- CUDA_REPO_PKG=cuda-repo-rhel7-10.0.130-1.x86_64.rpm

- wget https://developer.download.nvidia.com/compute/cuda/repos/rhel7/x86_64/${CUDA_REPO_PKG} -O /tmp/${CUDA_REPO_PKG}

- sudo rpm -ivh /tmp/${CUDA_REPO_PKG}

- rm -f /tmp/${CUDA_REPO_PKG}

- CUDA_REPO_PKG=cuda-repo-rhel8-10.2.89-1.x86_64.rpm

- wget https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/${CUDA_REPO_PKG} -O /tmp/${CUDA_REPO_PKG}

- sudo rpm -ivh /tmp/${CUDA_REPO_PKG}

- rm -f /tmp/${CUDA_REPO_PKG}

-**Message**: *Gallery name is invalid. Allowed characters are English alphanumeric characters, with underscores, and periods allowed in the middle, up to 80 characters total. All other special characters, including dashes, are disallowed.*

-**Cause**: The name for the gallery does not meet the naming requirements.

-**Workaround**: Choose a name that meets the following conditions:

-**Message**: *The provided resource name \<galleryName\> has these invalid trailing characters: \<character\>. The name can not end with characters: \<character\>*

-**Cause**: The name for the gallery ends with a period or underscore.

-**Workaround**: Choose a name for the gallery that meets the following conditions:

-**Message**: *The provided location \<region\> is not available for resource type 'Microsoft.Compute/galleries'. List of available regions for the resource type is …*

-**Cause**: The region specified for the gallery is incorrect or requires an access request.

-**Workaround**: Check that the region name is correct. If the region name is correct, submit [an access request](/troubleshoot/azure/general/region-access-request-process) for the region.

-**Message**: *Can not delete resource before nested resources are deleted.*

-**Cause**: You've tried to delete a gallery that contains at least one existing image definition. A gallery must be empty before it can be deleted.

-**Workaround**: Delete all image definitions inside the gallery and then proceed to delete the gallery. If the image definition contains image versions, you must delete the image versions before you delete the image definitions.

-**Message**: *The gallery name \<galleryName\> is not unique within the subscription \<subscriptionID\>. Please pick another gallery name.*

-**Cause**: You have an existing gallery with the same name and have tried to create another gallery with the same name.

-**Workaround**: Choose a different name for the gallery.

-**Message**: *The resource \<galleryName\> already exists in location \<region\_1\> in resource group \<resourceGroup\>. A resource with the same name cannot be created in location \<region\_2\>. Please select a new resource name.*

-**Cause**: You have an existing gallery with the same name and have tried to create another gallery with the same name.

-**Workaround**: Choose a different name for the gallery.

-**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets

-## Deploy a trusted VM

-**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets

-### How does trusted launch compared to Hyper-V Shielded VM?

-Deploy a [trusted launch VM using the portal](trusted-launch-portal.md).

-3. Create a NAT gateway for outbound internet access. For more information see [Tutorial: Create a NAT gateway - Azure CLI](../../../virtual-network/nat-gateway/tutorial-create-nat-gateway-cli.md).

-* [Learn how to configure Pacemaker on Red Hat in Azure](./high-availability-guide-rhel-pacemaker.md)

-[anf-sap-applications-azure]:https://www.netapp.com/us/media/tr-4746.pdf

-3. **[A]** Prepare the OS for running SAP HANA on Azure NetApp with NFS, as described in [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]. Create configuration file */etc/sysctl.d/netapp-hana.conf* for the NetApp configuration settings.

- net.core.rmem_default = 16777216

- net.core.wmem_default = 16777216

- net.core.optmem_max = 16777216

- net.ipv4.tcp_rmem = 65536 16777216 16777216

- net.ipv4.tcp_wmem = 65536 16777216 16777216

-5. **[A]** Adjust the sunrpc settings, as recommended in the [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

-2.**[A]** Prepare the OS for running SAP HANA on Azure NetApp with NFS, as described in [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files](https://www.netapp.com/pdf.html?item=/media/17152-tr4746pdf.pdf). Create configuration file */etc/sysctl.d/netapp-hana.conf* for the NetApp configuration settings.

- net.core.rmem_default = 16777216

- net.core.wmem_default = 16777216

- net.core.optmem_max = 16777216

- net.ipv4.tcp_rmem = 65536 16777216 16777216

- net.ipv4.tcp_wmem = 65536 16777216 16777216

-4.**[A]** Adjust the sunrpc settings, as recommended in the [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files](https://www.netapp.com/pdf.html?item=/media/17152-tr4746pdf.pdf).

-[anf-sap-applications-azure]:https://www.netapp.com/us/media/tr-4746.pdf

-* [NetApp SAP applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

-1. **[A]** Prepare the operating system for running SAP HANA. For more information, see [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]. Create configuration file */etc/sysctl.d/netapp-hana.conf* for the Azure NetApp Files configuration settings.

- net.core.rmem_default = 16777216

- net.core.wmem_default = 16777216

- net.core.optmem_max = 16777216

- net.ipv4.tcp_rmem = 65536 16777216 16777216

- net.ipv4.tcp_wmem = 65536 16777216 16777216

-1. **[A]** Adjust the `sunrpc` settings, as recommended in [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

-[anf-sap-applications-azure]:https://www.netapp.com/us/media/tr-4746.pdf

-* [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]

-3. **[A]** Prepare the OS for running SAP HANA on NetApp Systems with NFS, as described in [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]. Create configuration file */etc/sysctl.d/netapp-hana.conf* for the NetApp configuration settings.

- net.core.rmem_default = 16777216

- net.core.wmem_default = 16777216

- net.core.optmem_max = 16777216

- net.ipv4.tcp_rmem = 65536 16777216 16777216

- net.ipv4.tcp_wmem = 65536 16777216 16777216

-4. **[A]** Adjust the sunrpc settings, as recommended in the [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

-[anf-sap-applications-azure]:https://www.netapp.com/us/media/tr-4746.pdf

-* [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]

-3. **[A]** Prepare the OS for running SAP HANA on Azure NetApp with NFS, as described in [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]. Create configuration file */etc/sysctl.d/netapp-hana.conf* for the NetApp configuration settings.

- net.core.rmem_default = 16777216

- net.core.wmem_default = 16777216

- net.core.optmem_max = 16777216

- net.ipv4.tcp_rmem = 65536 16777216 16777216

- net.ipv4.tcp_wmem = 65536 16777216 16777216

-5. **[A]** Adjust the sunrpc settings, as recommended in the [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

- For more information, see [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

-[anf-sap-applications-azure]:https://www.netapp.com/us/media/tr-4746.pdf

-* [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]

-3. **[A]** Prepare the OS for running SAP HANA on NetApp Systems with NFS, as described in [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure]. Create configuration file */etc/sysctl.d/netapp-hana.conf* for the NetApp configuration settings.

- net.core.rmem_default = 16777216

- net.core.wmem_default = 16777216

- net.core.optmem_max = 16777216

- net.ipv4.tcp_rmem = 65536 16777216 16777216

- net.ipv4.tcp_wmem = 65536 16777216 16777216

-4. **[A]** Adjust the sunrpc settings, as recommended in the [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

- For more information, see [NetApp SAP Applications on Microsoft Azure using Azure NetApp Files][anf-sap-applications-azure].

-|[Tutorial: Create and test a NAT gateway - Azure CLI](../virtual-network/nat-gateway/tutorial-create-nat-gateway-cli.md)|Create and validate a NAT gateway using a virtual machine. |

-> This is a simple deployment of a NAT gateway. For advanced configuration and setup, see [Tutorial: Create a NAT gateway using the Azure portal](../nat-gateway/tutorial-create-nat-gateway-portal.md)

-| VPN Gateway (AZ SKU), Application Gateway v2, NAT Gateway | You can use a public IP from a prefix for your gateway | To associate an IP from a prefix to your gateway: </br> 1. [Create a prefix.](manage-public-ip-address-prefix.md) </br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md) </br> 3. When you deploy the [VPN Gateway](../../vpn-gateway/tutorial-create-gateway-portal.md), [Application Gateway](../../application-gateway/quick-create-portal.md#create-an-application-gateway), or [NAT Gateway](../nat-gateway/tutorial-create-nat-gateway-portal.md), be sure to select the IP you previously gave from the prefix.|

-* To create and validate a NAT gateway, see [Tutorial: Create a NAT gateway using the Azure portal](tutorial-create-nat-gateway-portal.md)

-For steps on how to test the NAT gateway, see [Tutorial: Create a NAT gateway - Azure portal](tutorial-create-nat-gateway-portal.md#test-nat-gateway).

-1. Validate that your [NAT gateway public IP address is being used](./tutorial-create-nat-gateway-portal.md#test-nat-gateway).

-1. [Testing that the NAT gateway public IP](./tutorial-create-nat-gateway-portal.md#test-nat-gateway) is used for outbound traffic. If a different IP is being used, it could be because of a custom UDR, follow the remaining steps on how to check for and remove custom UDRs.

-| [Azure portal](./nat-gateway/tutorial-create-nat-gateway-portal.md) | Creates a virtual network, subnet, public IP, NAT gateway, and a virtual machine to test the NAT gateway resource. |

-| [Azure PowerShell](./nat-gateway/tutorial-create-nat-gateway-powershell.md) | Includes the use of [New-AzNatGateway](/powershell/module/az.network/new-aznatgateway) to create a NAT gateway resource. Creates a virtual network, subnet, public IP, NAT gateway, and a virtual machine to test the NAT gateway resource. |

-| [Azure CLI](./nat-gateway/tutorial-create-nat-gateway-cli.md) | Includes the use of [az network nat gateway create](/cli/azure/network/nat#az-network-nat-gateway-create) to create a NAT gateway resource. Creates a virtual network, subnet, public IP, NAT gateway, and a virtual machine to test the NAT gateway resource. |

-**Time Grain** - Refers to the frequency at which you want see the aggregation of. In the current command, you will see a selected aggregated unit per 5 mins. You can select ΓÇô 5M/15M/30M/1H/6H/12H and 1D.

-| **BitsInPerSecond** | Bits ingressing Azure per second.|

-| **BitsOutPerSecond** | Bits egressing Azure per second. |

-| **Packets per second** | Packet count of ExpressRoute Gateway.|