added more links, fixed formatting

HeidiSteen · HeidiSteen · commit 8288756d9591 · 2021-11-18T21:37:27.000-08:00
diff --git a/articles/search/search-sku-manage-costs.md b/articles/search/search-sku-manage-costs.md
@@ -19,6 +19,8 @@ As a first step, estimate your baseline costs by using the Azure pricing calcula
 
 Azure provides built-in cost management that cuts across service boundaries to provide inclusive cost monitoring and the ability to set budgets and define alerts. The costs of running a search service will vary depending on capacity and which features you use. After you create your search service, optimize capacity so that you pay only for what you need. 
 
+<a name="billable-events"></a>
+
 ## Understand the billing model
 
 Azure Cognitive Search runs on Azure infrastructure that accrues costs when you deploy new resources. It's important to understand that there could be other additional infrastructure costs that might accrue.
@@ -27,50 +29,37 @@ Azure Cognitive Search runs on Azure infrastructure that accrues costs when you
 
 When you create or use Search resources, you're charged for the following meters:
 
-+ You're charged an hourly rate based on the [pricing tier](search\search-sku-tier.md) of your search service, prorated to the hour. 
++ You're charged an hourly rate based on the [pricing tier](search-sku-tier.md) of your search service, prorated to the hour.
 
-+ The charge is applied to a *search unit* (SU) allocated to the service. Search units are the product of replicas and partitions (R x P = SU), which allows you to scale using flexible combinations of replicas and partitions, varying capacity depending on whether you need more query or indexing power.
++ The charge is applied per the number of search units (SU) allocated to the service. Search units are [units of capacity](search-capacity-planning.md) and are the product of replicas and partitions (R x P = SU) allocated to your service.
 
-Billing is based on capacity and the costs of running premium features, such as [AI enrichment](cognitive-search-concept-intro.md), [Semantic search](semantic-search-overview.md), and [Private endpoints](service-create-private-endpoint.md).
+Billing is based on capacity (SUs) and the costs of running premium features, such as [AI enrichment](cognitive-search-concept-intro.md), [Semantic search](semantic-search-overview.md), and [Private endpoints](service-create-private-endpoint.md). Meters associated with premium features are listed in the following table.
 
 | Meter | Unit |
 |-------|------|
-| Indexer usage | 1 unit for every 1000 API calls |
-| Image extraction (AI enrichment) <sup>1</sup> | Per 1000 images. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing). |
-| Custom Entity extraction (AI enrichment) <sup>2</sup> | Per 1000 text records. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing) |
-| Custom Entity Lookup skill (AI enrichment) <sup>2</sup> | Per 1000 text records. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing) |
-| Built-in skills  (AI enrichment) <sup>2</sup> | Number of transactions, billed at the same rate as if you had performed the task by calling Cognitive Services directly. You can process 20 documents per indexer per day for free. Larger or more frequent workloads require a multi-resource Cognitive Services key. | 
-| Semantic Search <sup>2</sup> | Number of queries, billed at a progressive rate. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing). |
-| Private Endpoints <sup>2</sup> | Billed as long as the endpoint exists, and billed for bandwidth. |
+| Indexer usage | Per 1000 API calls |
+| Image extraction (AI enrichment) <sup>1, 2</sup> | Per 1000 images. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing). |
+| Custom Entity extraction (AI enrichment) <sup>1</sup> | Per 1000 text records. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing) |
+| Custom Entity Lookup skill (AI enrichment) <sup>1</sup> | Per 1000 text records. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing) |
+| Built-in skills  (AI enrichment) <sup>1</sup> | Number of transactions, billed at the same rate as if you had performed the task by calling Cognitive Services directly. You can process 20 documents per indexer per day for free. Larger or more frequent workloads require a multi-resource Cognitive Services key. |
+| Semantic Search <sup>1</sup> | Number of queries of "queryType=semantic", billed at a progressive rate. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing). |
+| Private Endpoints <sup>1</sup> | Billed as long as the endpoint exists, and billed for bandwidth. |
 
-<sup>1</sup> In an [indexer configuration](/rest/api/searchservice/create-indexer#indexer-parameters), **imageAction** is the parameter that triggers image extraction. If **imageAction** is set to "none" (the default), you won't be charged for image extraction. See the [pricing page](https://azure.microsoft.com/pricing/details/search/) page for image extraction charges.
+<sup1</sup> Applies only if you use or enable the feature.
 
-<sup>2</sup> Applies only if you enable the feature.
+<sup>2</sup> In an [indexer configuration](/rest/api/searchservice/create-indexer#indexer-parameters), "imageAction" is the parameter that triggers image extraction. If "imageAction" is set to "none" (the default), you won't be charged for image extraction. 
 
-There is no meter on the number of queries, query responses, or documents ingested, although [service limits](search\search-limits-quotas-capacity.md) do apply at each tier.
+There is no meter on the number of queries, query responses, or documents ingested, although [service limits](search-limits-quotas-capacity.md) do apply at each tier.
 
 Data traffic might also incur networking costs. See the [Bandwidth pricing](https://azure.microsoft.com/pricing/details/bandwidth/).
 
-Several premium features ([Knowledge store](knowledge-store-concept-intro.md), [Debug Sessions](cognitive-search-debug-session.md), [Enrichment cache (preview)](cognitive-search-incremental-indexing-conceptual.md)) have a dependency on Azure Storage. The meters for Azure Storage apply in this case, and the associated storage costs of using those features will be included in the Azure Storage bill.
+Several premium features ([Knowledge store](knowledge-store-concept-intro.md), [Debug Sessions](cognitive-search-debug-session.md), [Enrichment cache (preview)](cognitive-search-incremental-indexing-conceptual.md)) have a dependency on Azure Storage. The meters for Azure Storage apply in this case, and the associated storage costs of using these features will be included in the Azure Storage bill.
 
 [Customer-managed keys](search-security-manage-encryption-keys.md) provide double encryption of sensitive content. This feature requires a billable [Azure Key Vault](https://azure.microsoft.com/pricing/details/key-vault/)).
 
-Skillsets can include [billable built-in skills](cognitive-search-predefined-skills.md), non-billable built-in utility skills, and custom skills. 
-
-+ Non-billable utility skills include Conditional, Shaper, Text Merge, Text Split. There is no billing impact when using them, no Cognitive Services key requirement, and no 20 document limit. 
-+ A custom skill is functionality you provide. The cost of using a custom skill depends entirely on whether custom code is calling other metered services.  There is no Cognitive Services key requirement and no 20 document limit on custom skills.
-
-<!-- 
-
+Skillsets can include [billable built-in skills](cognitive-search-predefined-skills.md), non-billable built-in utility skills, and custom skills. Non-billable utility skills include Conditional, Shaper, Text Merge, Text Split. There is no billing impact when using them, no Cognitive Services key requirement, and no 20 document limit. 
 
-| Operation | Billing impact |
-|-----------|----------------|
-| Document cracking, text extraction | Free |
-| Document cracking, image extraction | Billed according to the number of images extracted from your documents. |
-| [Built-in skills](cognitive-search-predefined-skills.md) based on Cognitive Services | Billed at the same rate as if you had performed the task by using Cognitive Services directly. You can process 20 documents per indexer per day for free. Larger or more frequent workloads require a key. |
-| [Built-in skills](cognitive-search-predefined-skills.md) that do not add enrichments | None. Non-billable utility skills include Conditional, Shaper, Text Merge, Text Split. There is no billing impact, no Cognitive Services key requirement, and no 20 document limit. |
-| Custom skills | |
-| [Custom Entity Lookup](cognitive-search-skill-custom-entity-lookup.md) | Metered by Azure Cognitive Search. See the [pricing page](https://azure.microsoft.com/pricing/details/search/#pricing) for details. | -->
+A custom skill is functionality you provide. The cost of using a custom skill depends entirely on whether custom code is calling other metered services.  There is no Cognitive Services key requirement and no 20 document limit on custom skills.
 
 ## Monitor costs
 
@@ -82,13 +71,13 @@ Follow these guidelines to minimize costs of an Azure Cognitive Search solution.
 
 1. If possible, create all resources in the same region, or in as few regions as possible, to minimize or eliminate bandwidth charges.
 
-1. Scale up for resource-intensive operations like indexing, and then readjust downwards for regular query workloads. If there are predictable patterns to your workloads, you might be able to synchronize scale up to coincide with the expected volume (you would need to write code to automate this).
+1. [Scale up](search-capacity-planning.md) for resource-intensive operations like indexing, and then readjust downwards for regular query workloads. If there are predictable patterns to your workloads, you might be able to synchronize scale up to coincide with the expected volume (you would need to write code to automate this).
 
    When estimating the cost of a search solution, keep in mind that pricing and capacity aren't linear (doubling capacity more than doubles the cost on the same tier). Also, at some point, switching up to a higher tier can give you better and faster performance at roughly the same price point. For more information and an example, see [Upgrade to a Standard S2 tier](search-performance-tips.md#tip-upgrade-to-a-standard-s2-tier).
 
-1. Consider Azure Web App for your front-end application so that requests and responses stay within the data center boundary.
+1. Consider [Azure Web App](../app-service/overview.md) for your front-end application so that requests and responses stay within the data center boundary.
 
-1. If you're using AI enrichment, there is an extra charge for blob storage, but the cumulative cost goes down if you enable incremental enrichment.
+1. If you're using [AI enrichment](cognitive-search-concept-intro.md), there is an extra charge for blob storage, but the cumulative cost goes down if you enable [enrichment caching](cognitive-search-incremental-indexing-conceptual.md).
 
 ## Create budgets
 
