Merge pull request #220766 from adrianhall/main

Removed DevOps Toolkit references

Author: prmerger-automator[bot]

articles/api-management/devops-api-development-templates.md

@@ -22,12 +22,11 @@ Each part of the API DevOps pipeline is discussed below.
 
 ## API definition
 
-An API developer writes an API definition by providing a specification, settings (such as logging, diagnostics, and backend settings), and policies to be applied to the API. The API definition provides the information required to provision the API on an Azure API Management service. The specification  may be based on a standards-based API specification (such as [WSDL][1], [OpenAPI][2], or [GraphQL][3]), or it may be defined using the Azure Resource Manager (ARM) APIs (for example, an ARM template describing the API and operations). The API definition will change over time and should be considered "source code". Ensure that the API definition is stored under source code control and has appropriate review before adoption.  
+An API developer writes an API definition by providing a specification, settings (such as logging, diagnostics, and backend settings), and policies to be applied to the API. The API definition provides the information required to provision the API on an Azure API Management service. The specification may be based on a standards-based API specification (such as [WSDL][1], [OpenAPI][2], or [GraphQL][3]), or it may be defined using the Azure Resource Manager (ARM) APIs (for example, an ARM template describing the API and operations). The API definition will change over time and should be considered "source code". Ensure that the API definition is stored under source code control and has appropriate review before adoption.  
 
 There are several tools to assist producing the API definition:
 
-* The [Azure API Management DevOps Resource Toolkit][4] includes two tools that provide an Azure Resource Manager (ARM) template.  The _extractor_ creates an ARM template by extracting an API definition from an API Management service. The _creator_ produces the ARM template from a YAML specification.  The DevOps Resource Toolkit supports SOAP, REST, and GraphQL APIs.
-* The [Azure APIOps Toolkit][5] provides a workflow built on top of a [git][21] source code control system (such as [GitHub][22] or [Azure Repos][23]).  It uses an _extractor_ similar to the DevOps Resource Toolkit to produce an API definition that is then applied to a target API Management service.  APIOps supports REST and GraphQL APIs at this time.
+* The [Azure APIOps Toolkit][5] provides a workflow built on top of a [git][21] source code control system (such as [GitHub][22] or [Azure Repos][23]).  It uses an _extractor_ to produce an API definition that is then applied to a target API Management service by a _publisher_.  APIOps supports REST and GraphQL APIs at this time.
 * The [dotnet-apim][6] tool converts a well-formed YAML definition into an ARM template for later deployment.  The tool is focused on REST APIs.
 * [Terraform][7] is an alternative to Azure Resource Manager to configure resources in Azure.  You can create a Terraform configuration (together with policies) to implement the API in the same way that an ARM template is created.
 
@@ -53,9 +52,9 @@ Once the automated tools have been run, the API definition is reviewed by the hu
 
 The API definition will be published to an API Management service through a release pipeline.  The tools used to publish the API definition depend on the tool used to produce the API definition:
 
-* If using the [Azure API Management DevOps Resource Toolkit][4] or [dotnet-apim][6], the API definition is represented as an ARM template.  Tasks are available for [Azure Pipelines][17] and [GitHub Actions][18] to deploy an ARM template.
-* If using the [Azure APIOps Toolkit][5], the toolkit includes a publisher that writes the API definition to the service.
-* If using [Terraform][7], CLI tools will deploy the API definition on your service.  There are tasks available for [Azure Pipelines][19] and [GitHub Actions][20]
+* If using the [Azure APIOps Toolkit][5], the toolkit includes a publisher that writes the API definition to the target service.
+* If using [dotnet-apim][6], the API definition is represented as an ARM template.  Tasks are available for [Azure Pipelines][17] and [GitHub Actions][18] to deploy an ARM template.
+* If using [Terraform][7], CLI tools will deploy the API definition on your service.  There are tasks available for [Azure Pipelines][19] and [GitHub Actions][20].
 
 > **Can I use other source code control and CI/CD systems?**
 >
@@ -74,6 +73,7 @@ We've seen the greatest success in customer deployments, and recommend the follo
 * Set up either [GitHub][22] or [Azure Repos][23] for your source code control system.  This choice will determine your choice of pipeline runner as well.  GitHub can use [Azure Pipelines][17] or [GitHub Actions][18], whereas Azure Repos must use Azure Pipelines.
 * Set up an Azure API Management service for each API developer so that they can develop API definitions along with the API service.  Use the consumption or developer SKU when creating the service.
 * Use [policy fragments][24] to reduce the new policy that developers need to write for each API.
+* Use [named values][29] and [backends][30] to ensure that policies are generic and can apply to any API Management instance.
 * Use the [Azure APIOps Toolkit][5] to extract a working API definition from the developer service.
 * Set up an API approval process that runs on each pull request.  The API approval process should include breaking change detection, linting, and automated API testing. 
 * Use the [Azure APIOps Toolkit][5] publisher to publish the API to your production API Management service.
@@ -117,3 +117,5 @@ Review [Automated API deployments with APIOps][28] in the Azure Architecture Cen
 [26]: https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md
 [27]: https://github.com/Azure/azure-api-style-guide
 [28]: /azure/architecture/example-scenario/devops/automated-api-deployments-apiops
+[29]: /azure/api-management/api-management-howto-properties
+[30]: /azure/api-management/backends