You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@@ -294,7 +294,7 @@ curl --request POST http://localhost:7071/api/MyHttpTrigger --data "{'name':'Azu
294
294
295
295
The following considerations apply when calling HTTP endpoints locally:
296
296
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).
298
298
299
299
+ 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.
Copy file name to clipboardExpand all lines: articles/cyclecloud/overview.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,8 +31,9 @@ CycleCloud integrates with Azure services such as [Azure Monitor](/azure/azure-m
31
31
### CycleCloud Capabilities
32
32
33
33
::: moniker range="=cyclecloud-7"
34
-
|||
35
-
| --- | --- |
34
+
35
+
|Capability|Image|
36
+
|---|---|
36
37
|[**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 ||
37
38
|[**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 ||
38
39
|[**Autoscale Resources**](./concepts/scheduling.md)<br>Automatically adjust cluster size and components based upon job load, availability, and time requirements ||
@@ -44,8 +45,9 @@ CycleCloud integrates with Azure services such as [Azure Monitor](/azure/azure-m
44
45
::: moniker-end
45
46
46
47
::: moniker range=">=cyclecloud-8"
47
-
|||
48
-
| --- | --- |
48
+
49
+
|Capability|Image|
50
+
|---|---|
49
51
|[**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 ||
50
52
|[**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 ||
51
53
|[**Autoscale Resources**](./concepts/scheduling.md)<br>Automatically adjust cluster size and components based upon job load, availability, and time requirements ||
Copy file name to clipboardExpand all lines: articles/data-factory/frequently-asked-questions.yml
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -225,10 +225,6 @@ sections:
225
225
### How do I gracefully handle null values in an activity output?
226
226
227
227
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.
232
228
233
229
- question: |
234
230
Mapping data flows
@@ -238,6 +234,10 @@ sections:
238
234
When Microsoft provides help or troubleshooting with data flows, please provide the ADF pipeline support files.
239
235
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**.
240
236
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
+
241
241
### How do I access data by using the other 90 dataset types in Data Factory?
242
242
243
243
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.
Copy file name to clipboardExpand all lines: articles/event-grid/mqtt-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
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.
# 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
16
16
17
17
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.
18
18
@@ -23,6 +23,7 @@ This article guides you through the steps to configure an Azure Front Door Premi
23
23
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
24
24
- 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).
25
25
- 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.
26
27
27
28
## Create an origin group and add the API Management instance as an origin
28
29
@@ -83,6 +84,8 @@ This article guides you through the steps to configure an Azure Front Door Premi
83
84
84
85
- 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)
85
86
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
+
86
89
## Create an origin group and add the API Management instance as an origin
87
90
88
91
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
182
185
183
186
- 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)
184
187
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
+
185
190
## Create an origin group and add the API Management instance as an origin
186
191
187
192
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
260
265
261
266
## Next steps
262
267
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).
-`changedBy`: Who initiated a change in your resource, like an app ID or authorized person's email address.
24
24
-`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.
26
26
27
27
## Prerequisites
28
28
@@ -64,8 +64,14 @@ When a resource is created, updated, or deleted, a new change resource (`Microso
64
64
```
65
65
66
66
[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
+
67
72
> [!NOTE]
68
73
> 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.
0 commit comments