Skip to content

Commit 6847e46

Browse files
authored
Merge pull request #295814 from MicrosoftDocs/main
3/5/2025 PM Publish
2 parents d956d6e + 7138d5e commit 6847e46

File tree

132 files changed

+687
-645
lines changed

Some content is hidden

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

132 files changed

+687
-645
lines changed

articles/azure-functions/functions-develop-local.md

Lines changed: 65 additions & 26 deletions
Large diffs are not rendered by default.

articles/azure-functions/functions-run-local.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Develop Azure Functions locally using Core Tools
33
description: Learn how to code and test Azure Functions from the command prompt or terminal on your local computer before you deploy them to run them on Azure Functions.
44
ms.assetid: 242736be-ec66-4114-924b-31795fd18884
55
ms.topic: conceptual
6-
ms.date: 11/14/2023
6+
ms.date: 02/23/2025
77
ms.custom: devx-track-csharp, 80e4ff38-5174-43, devx-track-extended-java, devx-track-js, devx-track-python, devx-track-ts
88
zone_pivot_groups: programming-languages-set-functions
99
---
@@ -294,7 +294,7 @@ curl --request POST http://localhost:7071/api/MyHttpTrigger --data "{'name':'Azu
294294

295295
The following considerations apply when calling HTTP endpoints locally:
296296

297-
+ You can make GET requests from a browser passing data in the query string. For all other HTTP methods, you must use a HTTP testing tool that also keeps your data secure. For more information, see [HTTP test tools](functions-develop-local.md#http-test-tools).
297+
+ You can make GET requests from a browser passing data in the query string. For all other HTTP methods, you must use an HTTP testing tool that also keeps your data secure. For more information, see [HTTP test tools](functions-develop-local.md#http-test-tools).
298298

299299
+ Make sure to use the same server name and port that the Functions host is listening on. You see an endpoint like this in the output generated when starting the Function host. You can call this URL using any HTTP method supported by the trigger.
300300

articles/azure-vmware/faq.yml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ metadata:
44
description: "Get answers to common questions about Azure VMware Solution."
55
ms.topic: faq
66
ms.service: azure-vmware
7-
ms.date: 1/24/2025
7+
ms.date: 3/5/2025
88
title: Common questions about Azure VMware Solution
99
summary: This article answers commonly asked questions about Azure VMware Solution.
1010

@@ -274,6 +274,11 @@ sections:
274274
- question: Why does a vSphere Storage vMotion from Azure NetApp Files (ANF) to another datastore take an extended period of time?
275275
answer: This is due to the use of the Data Mover agent in the ESXi kernel. The Data Mover agent requires that all the blocks in the VMDK (Virtual Machine Disk) file be read and transferred to the ESXi host regardless of content. This results in the entire size of the VMDK to be transferred from the external array through the ESXi host to the destination datastore. The entire disk must be read in order to create a complete replica at the destination. The destination format and consumed space depends upon the destination datastore capabilities, protocol and format. Since all blocks must be read from the source datastore, the time to complete this operation may be longer than expected.
276276

277+
- question: What Fault tolerance setting should I maintain in a standard Azure VMware Solution deployment to remain compliant with Microsoft's SLA?
278+
answer: Per Microsoft's [SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) when the cluster has between 3 and 5 hosts, the number of failures to tolerate = 1; and when the cluster has between 6 and 16 hosts, the number of failures to tolerate = 2. Please note storage policies are not automatically upgraded based on cluster size.
279+
280+
- question: What Fault tolerance setting should I maintain in a stretched Azure VMware Solution deployment to remain compliant with Microsoft's SLA?
281+
answer: Per Microsoft's [SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) A minimum of 6 nodes are deployed in the cluster (3 in each availability zone), and you must have a minimum virtual machine storage policy of (i) primary level of failures to tolerate of "Dual-Site Mirroring" and (ii) a secondary level of failures to tolerate of 1 is used by the workload virtual machines
277282

278283
- name: Hosts, clusters, and private clouds
279284
questions:

articles/cyclecloud/overview.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,9 @@ CycleCloud integrates with Azure services such as [Azure Monitor](/azure/azure-m
3131
### CycleCloud Capabilities
3232

3333
::: moniker range="=cyclecloud-7"
34-
| | |
35-
| --- | --- |
34+
35+
|Capability|Image|
36+
|---|---|
3637
| [**Scheduler Agnostic**](./concepts/scheduling.md)<br>Use standard HPC schedulers such as Slurm, PBS Pro, LSF, Grid Engine, and HTCondor, or extend CycleCloud autoscaling plugins to work with your own scheduler | ![Schedulers sample](./images/version-7/overview-schedulers-tn.png) |
3738
| [**Manage Compute Resources**](./how-to/start-cluster.md)<br>Manage virtual machines and scale sets to provide a flexible set of compute resources that can meet your dynamic workload requirements | ![Compute resources sample](./images/overview-nodes-tn.png) |
3839
| [**Autoscale Resources**](./concepts/scheduling.md)<br>Automatically adjust cluster size and components based upon job load, availability, and time requirements | ![Autoscale sample](./images/overview-scaling-tn.png) |
@@ -44,8 +45,9 @@ CycleCloud integrates with Azure services such as [Azure Monitor](/azure/azure-m
4445
::: moniker-end
4546

4647
::: moniker range=">=cyclecloud-8"
47-
| | |
48-
| --- | --- |
48+
49+
|Capability|Image|
50+
|---|---|
4951
| [**Scheduler Agnostic**](./concepts/scheduling.md)<br>Use standard HPC schedulers such as Slurm, PBS Pro, LSF, Grid Engine, and HTCondor, or extend CycleCloud autoscaling plugins to work with your own scheduler | ![Schedulers sample](./images/version-8/overview-schedulers-tn.png) |
5052
| [**Manage Compute Resources**](./how-to/start-cluster.md)<br>Manage virtual machines and scale sets to provide a flexible set of compute resources that can meet your dynamic workload requirements | ![Compute resources sample](./images/overview-nodes-tn.png) |
5153
| [**Autoscale Resources**](./concepts/scheduling.md)<br>Automatically adjust cluster size and components based upon job load, availability, and time requirements | ![Autoscale sample](./images/overview-scaling-tn.png) |

articles/cyclecloud/release-notes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The current release is 8.7.1.
1414

1515
CycleCloud 8.7 is the seventh GA release of the CycleCloud 8.x platform and continues to add expanded scheduler support and security improvements.
1616

17-
| | |
17+
| Note | Image |
1818
| --- | --- |
1919
|[**CycleCloud can use Managed Identity for more secure access to Azure Storage**](./how-to/managed-identities.md)<br/> CycleCloud now supports replacing Shared Access Key access to Azure Storage with Identity-based access for both the CycleCloud orchestrator and CycleCloud Locker access for cluster nodes. | |
2020
| [**OpenPBS is supported by azpbs agent**](~/articles/cyclecloud/openpbs.md)<br/> Introducing `azpbs` a configuration-based agent for managing heterogeneous OpenPBS cluster including on-prem/cloud hybrid. `azpbs` is a more general and precise matching framework for job and VM resources. | ![Open PBS Logo](./images/release-notes/openpbs-logo.png) |

articles/data-factory/frequently-asked-questions.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -225,10 +225,6 @@ sections:
225225
### How do I gracefully handle null values in an activity output?
226226
227227
You can use the `@coalesce` construct in the expressions to handle null values gracefully.
228-
229-
### How many pipeline activities can be executed simultaneously?
230-
231-
A maximum of 50 concurrent pipeline activities is allowed. The 51st pipeline activity will be queued until a free slot is opened up. A maximum of 800 concurrent external activities will be allowed, after which they will be queued in the same way.
232228
233229
- question: |
234230
Mapping data flows
@@ -238,6 +234,10 @@ sections:
238234
When Microsoft provides help or troubleshooting with data flows, please provide the ADF pipeline support files.
239235
This Zip file contains the code-behind script from your data flow graph. From the ADF UI, select **...** next to pipeline, and then select **Download support files**.
240236
237+
### How many concurrent mapping data flow pipeline activities can be executed simultaneously?
238+
239+
A maximum of 50 concurrent mapping data flow pipeline activities is allowed.
240+
241241
### How do I access data by using the other 90 dataset types in Data Factory?
242242
243243
The mapping data flow feature currently allows Azure SQL Database, Azure Synapse Analytics, delimited text files from Azure Blob storage or Azure Data Lake Storage Gen2, and Parquet files from Blob storage or Data Lake Storage Gen2 natively for source and sink.

articles/event-grid/mqtt-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
title: 'Overview of MQTT broker in Azure Event Grid'
3-
description: Message Queuing Telemetry Transport (MQTT) broker feature in Azure Event Grid enables MQTT clients to communicate with each other and with Azure services.
2+
title: MQTT (PubSub) broker'
3+
description: Message Queuing Telemetry Transport (MQTT) PubSub broker feature in Azure Event Grid enables MQTT clients to communicate with each other and with Azure services.
44
ms.topic: concept-article
5-
ms.date: 02/12/2025
5+
ms.date: 03/05/2025
66
author: george-guirguis
77
ms.author: geguirgu
88
ms.subservice: mqtt

articles/extended-zones/TOC.yml

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,10 @@
2929
href: create-storage-account.md
3030
- name: Request quota increase
3131
href: request-quota-increase.md
32+
- name: Security
33+
items:
34+
- name: Azure Network Security Blog
35+
href: https://techcommunity.microsoft.com/category/azure-network-security/blog/azurenetworksecurityblog
3236
- name: Reference
3337
items:
3438
- name: Azure CLI
@@ -39,7 +43,13 @@
3943
items:
4044
- name: Microsoft Q&A
4145
href: /answers/tags/133/azure
46+
- name: Azure Networking Blog
47+
href: https://techcommunity.microsoft.com/category/azure/blog/azurenetworkingblog
4248
- name: Azure support
43-
href: https://azure.microsoft.com/support/
49+
href: https://azure.microsoft.com/support
50+
- name: Pricing
51+
href: https://azure.microsoft.com/pricing
4452
- name: Service updates
4553
href: https://azure.microsoft.com/updates
54+
- name: SLA
55+
href: https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services

articles/frontdoor/standard-premium/how-to-enable-private-link-apim.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'Connect Azure Front Door Premium to an Azure API Management origin with Private Link (Preview)'
2+
title: 'Connect Azure Front Door Premium to an Azure API Management origin with Private Link'
33
titleSuffix: Azure Private Link
44
description: Learn how to connect your Azure Front Door Premium to an Azure API Management privately.
55
services: frontdoor
@@ -12,7 +12,7 @@ zone_pivot_groups: front-door-dev-exp-portal-ps-cli
1212
ms.custom: ai-usage
1313
---
1414

15-
# Connect Azure Front Door Premium to an Azure API Management with Private Link (Preview)
15+
# Connect Azure Front Door Premium to an Azure API Management with Private Link
1616

1717
This article guides you through the steps to configure an Azure Front Door Premium to connect privately to your Azure API Management origin using Azure Private Link.
1818

@@ -23,6 +23,7 @@ This article guides you through the steps to configure an Azure Front Door Premi
2323
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
2424
- Have a functioning Azure Front Door Premium profile and an endpoint. For more information on how to create an Azure Front Door profile, see [Create a Front Door](../create-front-door-portal.md).
2525
- Have a functioning Azure API Management instance. For more information on how to create an API Management instance, see [Create a new Azure API Management instance](../../api-management/get-started-create-service-instance.md)
26+
- Private endpoint support for Azure API Management Standard v2 tier is currently in limited preview. If you want to enable an Azure API Management Standard v2 tier instance as a private link enabled origin for Azure Front Door Premium, you must first sign up for the preview via this [this form](https://aka.ms/privateendpointpreview). This step isn't needed if you're using an API Management instance with Developer, Basic, Standard or Premium tier.
2627

2728
## Create an origin group and add the API Management instance as an origin
2829

@@ -83,6 +84,8 @@ This article guides you through the steps to configure an Azure Front Door Premi
8384

8485
- Have a functioning Azure Front Door Premium profile and an endpoint. For more information on how to create an Azure Front Door profile, see [Create a Front Door - PowerShell](../create-front-door-powershell.md)
8586

87+
- Private endpoint support for Azure API Management Standard v2 tier is currently in limited preview. If you want to enable an Azure API Management Standard v2 tier instance as a private link enabled origin for Azure Front Door Premium, you must first sign up for the preview via this [this form](https://aka.ms/privateendpointpreview). This step isn't needed if you're using an API Management instance with Developer, Basic, Standard or Premium tier.
88+
8689
## Create an origin group and add the API Management instance as an origin
8790

8891
1. Use [New-AzFrontDoorCdnOriginGroupHealthProbeSettingObject](/powershell/module/az.cdn/new-azfrontdoorcdnorigingrouphealthprobesettingobject) to create an in-memory object for storing the health probe settings.
@@ -182,6 +185,8 @@ Your Azure Front Door profile is now fully functional after completing the final
182185

183186
- A functioning Azure API Management instance. See [Create a new Azure API Management instance by using the Azure CLI](../../api-management/get-started-create-service-instance-cli.md)
184187

188+
- Private endpoint support for Azure API Management Standard v2 tier is currently in limited preview. If you want to enable an Azure API Management Standard v2 tier instance as a private link enabled origin for Azure Front Door Premium, you must first sign up for the preview via this [this form](https://aka.ms/privateendpointpreview). This step isn't needed if you're using an API Management instance with Developer, Basic, Standard or Premium tier.
189+
185190
## Create an origin group and add the API Management instance as an origin
186191

187192
1. Run [az afd origin-group create](/cli/azure/afd/origin-group#az-afd-origin-group-create) to create an origin group.
@@ -260,4 +265,4 @@ Your Azure Front Door profile is now fully functional after completing the final
260265

261266
## Next steps
262267

263-
Learn about [Private Link service with storage account](../../storage/common/storage-private-endpoints.md).
268+
Learn about [Private Link service with storage account](../../storage/common/storage-private-endpoints.md).

articles/governance/resource-graph/changes/get-resource-changes.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In this article, you learn:
2222
- Change analysis uses _Change Actor_ functionality:
2323
- `changedBy`: Who initiated a change in your resource, like an app ID or authorized person's email address.
2424
- `clientType`: Which client made the change, like _Azure portal_.
25-
- `operation`: Which [operation](../../../role-based-access-control/resource-provider-operations.md) was called, like `Microsoft.Compute/virtualmachines/write`.
25+
- `operation`: Which [operation](../../../role-based-access-control/resource-provider-operations.md) was called, like `Microsoft.Compute/virtualmachines/write`. The `operation` field in the resource changes data represents the [Azure role-based access control permissions](../../../role-based-access-control/resource-provider-operations.md) used to initiate the change.
2626

2727
## Prerequisites
2828

@@ -64,8 +64,14 @@ When a resource is created, updated, or deleted, a new change resource (`Microso
6464
```
6565

6666
[See the full reference guide for change resource properties.](/rest/api/resources/changes)
67+
68+
The `operation` field in the resource changes data represents the [Azure role-based access control permissions](../../../role-based-access-control/resource-provider-operations.md) used to initiate the change. This field does not always describe the actual operation performed but rather the permission (authorization action) that was used. For example, `Microsoft.Compute/virtualmachines/write` corresponds to the permission for the operation `PUT/providers/Microsoft.Compute/virtualmachines`.
69+
70+
For understanding the type of change that was captured in the resource (i.e. Create, Delete, Update), we recommend that you use the `changeType` field rather than the `operation` field, which instead represents the [Azure role-based access control permissions](../../../role-based-access-control/resource-provider-operations.md) used to initiate the change.
71+
6772
> [!NOTE]
6873
> Snapshots are not currently supported for deleted resources.
74+
> For records with `changeType`: Delete, the `changesCount` is shown as 0 because the resource itself gets deleted, and there are no properties remaining.
6975
7076
## Run a query
7177

0 commit comments

Comments
 (0)