Skip to content

Commit 232ebc0

Browse files
authored
Merge branch 'MicrosoftDocs:main' into vabachu/update-dtv2-host-json
2 parents d9760bd + d8c0f88 commit 232ebc0

File tree

236 files changed

+1077
-1054
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

236 files changed

+1077
-1054
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6509,6 +6509,11 @@
65096509
"source_path": "articles/cloud-services/schema-csdef-workerrole.md",
65106510
"redirect_url": "/previous-versions/azure/cloud-services/schema-csdef-workerrole",
65116511
"redirect_document_id": false
6512+
},
6513+
{
6514+
"source_path": "articles/reliability/migrate-sql-managed-instance.md",
6515+
"redirect_url": "/azure/azure-sql/managed-instance/instance-zone-redundancy-configure",
6516+
"redirect_document_id": false
65126517
}
65136518
]
65146519
}

articles/api-management/api-management-policy-expressions.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -243,22 +243,13 @@ The `context` variable is implicitly available in every policy [expression](api-
243243
|`bool VerifyNoRevocation(input: this System.Security.Cryptography.X509Certificates.X509Certificate2)`|Performs an X.509 chain validation without checking certificate revocation status.<br /><br />`input` - certificate object<br /><br />Returns `true` if the validation succeeds; `false` if the validation fails.|
244244

245245

246-
## Related content
247-
248-
For more information working with policies, see:
249-
250-
* [Policies in API Management](api-management-howto-policies.md)
251-
* [Tutorial: Transform and protect APIs](transform-api.md)
252-
* [Policy reference](./api-management-policies.md) for a full list of policy statements and their settings
253-
* [Policy snippets repo](https://github.com/Azure/api-management-policy-snippets)
254-
* [Azure API Management policy toolkit](https://github.com/Azure/azure-api-management-policy-toolkit/)
255-
* [Author policies using Microsoft Copilot in Azure](/azure/copilot/author-api-management-policies?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json)
246+
[!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]
256247

257248
For more information:
258249

259250
- See how to supply context information to your backend service. Use the [Set query string parameter](set-query-parameter-policy.md) and [Set HTTP header](set-header-policy.md) policies to supply this information.
260251
- See how to use the [Validate JWT](validate-jwt-policy.md) policy to pre-authorize access to operations based on token claims.
261-
- See how to use an [API Inspector](./api-management-howto-api-inspector.md) trace to detect how policies are evaluated and the results of those evaluations.
252+
- See how to use [API tracing](./api-management-howto-api-inspector.md) to detect how policies are evaluated and the results of those evaluations.
262253
- See how to use expressions with the [Get from cache](cache-lookup-policy.md) and [Store to cache](cache-store-policy.md) policies to configure API Management response caching. Set a duration that matches the response caching of the backend service as specified by the backed service's `Cache-Control` directive.
263254
- See how to perform content filtering. Remove data elements from the response received from the backend using the [Control flow](choose-policy.md) and [Set body](set-body-policy.md) policies.
264255
- To download the policy statements, see the [api-management-samples/policies](https://github.com/Azure/api-management-samples/tree/master/policies) GitHub repo.

articles/api-management/policy-fragments.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -110,12 +110,4 @@ After creating a policy fragment, you can view and update the properties of a po
110110
1. Review **Policy document references** for policy definitions that include the fragment. Before a fragment can be deleted, you must remove the fragment references from all policy definitions.
111111
1. After all references are removed, select **Delete**.
112112

113-
## Related content
114-
115-
For more information about working with policies, see:
116-
117-
+ [Tutorial: Transform and protect APIs](transform-api.md)
118-
+ [Set or edit policies](set-edit-policies.md)
119-
+ [Policy reference](./api-management-policies.md) for a full list of policy statements
120-
+ [Policy snippets repo](https://github.com/Azure/api-management-policy-snippets)
121-
+ [Author policies using Microsoft Copilot in Azure](/azure/copilot/author-api-management-policies?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json)
113+
[!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]

articles/api-management/set-edit-policies.md

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -229,13 +229,4 @@ To modify the policy evaluation order using the policy editor:
229229

230230
[!INCLUDE [api-management-policies-azure-copilot](../../includes/api-management-policies-azure-copilot.md)]
231231

232-
## Related content
233-
234-
For more information about working with policies, see:
235-
236-
* [Tutorial: Transform and protect APIs](transform-api.md)
237-
* [Set or edit policies](set-edit-policies.md)
238-
* [Policy reference](./api-management-policies.md)
239-
* [Policy snippets repo](https://github.com/Azure/api-management-policy-snippets)
240-
* [Azure API Management policy toolkit](https://github.com/Azure/azure-api-management-policy-toolkit/)
241-
* [Author policies using Microsoft Copilot in Azure](/azure/copilot/author-api-management-policies?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json)
232+
[!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]

articles/application-gateway/toc.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,6 @@
5959
href: redirect-overview.md
6060
- name: Rewrite HTTP headers and URL
6161
href: rewrite-http-headers-url.md
62-
6362
- name: TCP/TLS proxy
6463
href: tcp-tls-proxy-overview.md
6564
- name: Support for working remotely
@@ -96,6 +95,8 @@
9695
href: ssl-certificate-management.md
9796
- name: Security baseline
9897
href: /security/benchmark/azure/baselines/application-gateway-security-baseline?toc=/azure/application-gateway/toc.json
98+
- name: Network security blog
99+
href: https://techcommunity.microsoft.com/category/azure-network-security/blog/azurenetworksecurityblog
99100
- name: Deploy
100101
items:
101102
- name: Host multiple sites
@@ -368,6 +369,8 @@
368369
href: /azure/templates/microsoft.network/applicationgateways
369370
- name: Resources
370371
items:
372+
- name: Networking blog
373+
href: https://techcommunity.microsoft.com/category/azure/blog/azurenetworkingblog
371374
- name: Author templates
372375
displayName: ARM
373376
href: ../azure-resource-manager/templates/syntax.md

articles/automation/change-tracking/overview-monitoring-agent.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Automation Change Tracking and Inventory overview using Azure Monit
33
description: This article describes the Change Tracking and Inventory feature using Azure monitoring agent, which helps you identify software and Microsoft service changes in your environment.
44
services: automation
55
ms.subservice: change-inventory-management
6-
ms.date: 03/07/2025
6+
ms.date: 03/12/2025
77
ms.topic: overview
88
ms.service: azure-automation
99
---
@@ -28,7 +28,7 @@ Azure Change Tracking & Inventory service enhances the auditing and governance f
2828
1. **Change Tracking**
2929

3030
a. Monitors changes, including modifications to files, registry keys, software installations, and Windows services or Linux daemons.</br>
31-
b. Provides detailed logs of what and when the changes were made, who made them, enabling you to quickly detect configuration drifts or unauthorized changes. </br>
31+
b. Provides detailed logs of what and when the changes were made, enabling you to quickly detect configuration drifts or unauthorized changes. </br>
3232
Change Tracking metadata will get ingested into the ConfigurationChange table in the connected LA workspace. [Learn more](/azure/azure-monitor/reference/tables/configurationchange)
3333

3434
1. **Inventory**

articles/azure-app-configuration/enable-dynamic-configuration-aspnet-core.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ A *sentinel key* is a key that you update after you complete the change of all o
4343
// Load configuration from Azure App Configuration
4444
builder.Configuration.AddAzureAppConfiguration(options =>
4545
{
46-
options.Connect(new Uri(endpoint), new DefaultAzureCredential());
46+
options.Connect(new Uri(endpoint), new DefaultAzureCredential())
4747
// Load all keys that start with `TestApp:` and have no label
4848
.Select("TestApp:*", LabelFilter.Null)
4949
// Configure to reload configuration if the registered sentinel key is modified

articles/azure-cache-for-redis/cache-how-to-encryption.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ In the **Basic, Standard, and Premium** tiers, the OS disk is encrypted by defau
8787

8888
1. Select your chosen user assigned managed identity, and then choose the key input method to use.
8989

90-
1. If using the **Select Azure key vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
90+
1. If using the **Select Azure Key Vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
9191

9292
> [!NOTE]
9393
> For instructions on how to set up an Azure Key Vault instance, see the [Azure Key Vault quickstart guide](/azure/key-vault/secrets/quick-create-portal). You can also select the _Create a key vault_ link beneath the Key Vault selection to create a new Key Vault instance. Remember that both purge protection and soft delete must be enabled in your Key Vault instance.
@@ -113,7 +113,7 @@ In the **Basic, Standard, and Premium** tiers, the OS disk is encrypted by defau
113113

114114
1. Select your chosen user assigned managed identity, and then choose which key input method to use.
115115

116-
1. If using the **Select Azure key vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
116+
1. If using the **Select Azure Key Vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
117117

118118
> [!NOTE]
119119
> For instructions on how to set up an Azure Key Vault instance, see the [Azure Key Vault quickstart guide](/azure/key-vault/secrets/quick-create-portal). You can also select the _Create a key vault_ link beneath the Key Vault selection to create a new Key Vault instance.

articles/azure-cache-for-redis/managed-redis/managed-redis-how-to-encryption.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ In the **Flash Optimized** tier, keys and values are also partially stored on-di
7373

7474
1. Select your chosen user assigned managed identity, and then choose the key input method to use.
7575

76-
1. If using the **Select Azure key vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
76+
1. If using the **Select Azure Key Vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
7777

7878
> [!NOTE]
7979
> For instructions on how to set up an Azure Key Vault instance, see the [Azure Key Vault quickstart guide](/azure/key-vault/secrets/quick-create-portal). You can also select the _Create a key vault_ link beneath the Key Vault selection to create a new Key Vault instance. Remember that both purge protection and soft delete must be enabled in your Key Vault instance.
@@ -99,7 +99,7 @@ In the **Flash Optimized** tier, keys and values are also partially stored on-di
9999

100100
1. Select your chosen user assigned managed identity, and then choose which key input method to use.
101101

102-
1. If using the **Select Azure key vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
102+
1. If using the **Select Azure Key Vault and key** input method, choose the Key Vault instance that holds your customer managed key. This instance must be in the same region as your cache.
103103

104104
> [!NOTE]
105105
> For instructions on how to set up an Azure Key Vault instance, see the [Azure Key Vault quickstart guide](/azure/key-vault/secrets/quick-create-portal). You can also select the _Create a key vault_ link beneath the Key Vault selection to create a new Key Vault instance.

articles/azure-maps/how-to-secure-sas-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ The following example scenario uses two Azure Resource Manager (ARM) template de
4141
1. Create a user-assigned managed identity.
4242
1. Assign Azure role-based access control (RBAC) **Azure Maps Data Reader** role to the user-assigned managed identity.
4343
1. Create an Azure Maps account with a [Cross Origin Resource Sharing (CORS) configuration](azure-maps-authentication.md#cross-origin-resource-sharing-cors), and attach the user-assigned managed identity.
44-
1. Create and save a SAS token in the Azure key vault.
44+
1. Create and save a SAS token in the Azure Key Vault.
4545
1. Retrieve the SAS token secret from the key vault.
4646
1. Create an Azure Maps REST API request that uses the SAS token.
4747

0 commit comments

Comments
 (0)