Skip to content

Commit 0b0c836

Browse files
committed
Fix links for renamed quickstart file and terminology for Azure Logic Apps
1 parent 3e6390e commit 0b0c836

File tree

14 files changed

+41
-35
lines changed

14 files changed

+41
-35
lines changed

articles/applied-ai-services/metrics-advisor/tutorials/enable-anomaly-notification.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Required. Give each H2 a heading that sets expectations for the content that fol
5555
Follow the H2 headings with a sentence about how the section contributes to the whole.
5656
-->
5757

58-
## Send notifications with Logic Apps, Teams, and SMTP
58+
## Send notifications with Azure Logic Apps, Teams, and SMTP
5959

6060
#### [Logic Apps](#tab/logic)
6161

@@ -73,18 +73,18 @@ Select the **Hooks** tab in your Metrics Advisor workspace, and select the **Cre
7373
There's one extra parameter of **Endpoint** that needs to be filled out, this could be done after completing Step 3 below.
7474

7575

76-
**Step 2.** Create a Logic Apps resource
76+
**Step 2.** Create a Consumption logic app resource
7777

78-
In the [Azure portal](https://portal.azure.com), create an empty Logic App by following the instructions in [Create your logic app](../../../logic-apps/quickstart-create-first-logic-app-workflow.md). When you see the **Logic Apps Designer**, return to this tutorial.
78+
In the [Azure portal](https://portal.azure.com), create a Consumption logic app resource with a blank workflow by following the instructions in [Create an example Consumption logic app workflow](../../../logic-apps/quickstart-create-example-consumption-workflow.md). When you see the workflow designer opens, return to this tutorial.
7979

8080

8181
**Step 3.** Add a trigger of **When an HTTP request is received**
8282

83-
- Azure Logic Apps uses various actions to trigger workflows that are defined. For this use case, it uses the trigger of **When an HTTP request is received**.
83+
- Azure Logic Apps uses various actions to trigger workflows that are defined. For this use case, it uses the trigger named **When an HTTP request is received**.
8484

8585
- In the dialog for **When an HTTP request is received**, select **Use sample payload to generate schema**.
8686

87-
![Screenshot that shows the When an HTTP request dialog box and the Use sample payload to generate schema option selected. ](../media/tutorial/logic-apps-generate-schema.png)
87+
![Screenshot that shows the When an HTTP request dialog box and the Use sample payload to generate schema option selected.](../media/tutorial/logic-apps-generate-schema.png)
8888

8989
Copy the following sample JSON into the textbox and select **Done**.
9090

articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,13 +48,13 @@ For Azure Functions, you develop orchestrations by writing code and using the [D
4848

4949
You can mix and match services when you build an orchestration, such as calling functions from logic app workflows and calling logic app workflows from functions. Choose how to build each orchestration based on the services' capabilities or your personal preference. The following table lists some key differences between these services:
5050

51-
| | Durable Functions | Logic Apps |
51+
| | Durable Functions | Azure Logic Apps |
5252
| --- | --- | --- |
5353
| **Development** | Code-first (imperative) | Designer-first (declarative) |
5454
| **Connectivity** | [About a dozen built-in binding types](functions-triggers-bindings.md#supported-bindings), write code for custom bindings | [Large collection of connectors](/connectors/connector-reference/connector-reference-logicapps-connectors), [Enterprise Integration Pack for B2B scenarios](../logic-apps/logic-apps-enterprise-integration-overview.md), [build custom connectors](/connectors/custom-connectors/) |
5555
| **Actions** | Each activity is an Azure function; write code for activity functions |[Large collection of ready-made actions](/connectors/connector-reference/connector-reference-logicapps-connectors)|
56-
| **Monitoring** | [Azure Application Insights](../azure-monitor/app/app-insights-overview.md) | [Azure portal](../logic-apps/quickstart-create-first-logic-app-workflow.md), [Azure Monitor Logs](../logic-apps/monitor-workflows-collect-diagnostic-data.md), [Microsoft Defender for Cloud](../logic-apps/healthy-unhealthy-resource.md) |
57-
| **Management** | [REST API](durable/durable-functions-http-api.md), [Visual Studio](/visualstudio/azure/vs-azure-tools-resources-managing-with-cloud-explorer) | [Azure portal](../logic-apps/quickstart-create-first-logic-app-workflow.md), [REST API](/rest/api/logic/), [PowerShell](/powershell/module/az.logicapp), [Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md) |
56+
| **Monitoring** | [Azure Application Insights](../azure-monitor/app/app-insights-overview.md) | [Azure portal](../logic-apps/quickstart-create-example-consumption-workflow.md), [Azure Monitor Logs](../logic-apps/monitor-workflows-collect-diagnostic-data.md), [Microsoft Defender for Cloud](../logic-apps/healthy-unhealthy-resource.md) |
57+
| **Management** | [REST API](durable/durable-functions-http-api.md), [Visual Studio](/visualstudio/azure/vs-azure-tools-resources-managing-with-cloud-explorer) | [Azure portal](../logic-apps/quickstart-create-example-consumption-workflow.md), [REST API](/rest/api/logic/), [PowerShell](/powershell/module/az.logicapp), [Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md) |
5858
| **Execution context** | Can run [locally](./functions-kubernetes-keda.md) or in the cloud | Runs in Azure, locally, or on premises. For more information, see [What is Azure Logic Apps](../logic-apps/logic-apps-overview.md#resource-environment-differences). |
5959

6060
<a name="function"></a>
@@ -120,5 +120,5 @@ You can get more information on integration services by using the following link
120120
Get started by creating your first flow, logic app workflow, or function app. Select any of the following links:
121121

122122
* [Get started with Power Automate](/power-automate/getting-started)
123-
* [Create your first logic app workflow](../logic-apps/quickstart-create-first-logic-app-workflow.md)
123+
* [Create an example Consumption logic app workflow](../logic-apps/quickstart-create-example-consumption-workflow.md)
124124
* [Create your first Azure function](./functions-get-started.md)

articles/azure-monitor/alerts/itsm-convert-servicenow-to-webhook.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ If you're syncing work items between ServiceNow and an Azure Log Analytics works
2020

2121
## Pull data from your ServiceNow instance into a Log Analytics workspace
2222

23-
1. [Create a logic app](../../logic-apps/quickstart-create-first-logic-app-workflow.md) in the Azure portal.
23+
1. In the Azure portal, [create a Consumption logic app workflow](../../logic-apps/quickstart-create-example-consumption-workflow.md).
2424
1. Create an HTTP GET request that uses the [ServiceNow **Table** API](https://developer.servicenow.com/dev.do#!/reference/api/sandiego/rest/c_TableAPI) to retrieve data from the ServiceNow instance. [See an example](https://docs.servicenow.com/bundle/sandiego-application-development/page/integrate/inbound-rest/concept/use-REST-API-Explorer.html#t_GetStartedRetrieveExisting) of how to use the Table call to retrieve incidents.
2525
1. To see a list of tables in your ServiceNow instance, in ServiceNow, go to **System definitions**, then **Tables**. Example table names include: `change_request`, `em_alert`, `incident`, `em_event`.
2626

articles/communication-services/quickstarts/chat/logic-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ You can create automated workflows that send chat messages by using the Azure Co
2222

2323
- An active Azure Communication Services resource, or [create a Communication Services resource](../create-communication-resource.md).
2424

25-
- An active Azure Logic Apps resource, or [create a blank logic app with the trigger that you want to use](../../../logic-apps/quickstart-create-first-logic-app-workflow.md). Currently, the Communication Services Chat connector provides only actions, so your logic app requires a trigger, at minimum.
25+
- An active Azure Logic Apps resource, or [create a logic app workflow with the trigger that you want to use](../../../logic-apps/quickstart-create-example-consumption-workflow.md). Currently, the Communication Services Chat connector provides only actions, so your logic app requires a trigger, at minimum.
2626

2727
## Create user
2828

@@ -96,7 +96,7 @@ To verify that you sent a message correctly:
9696

9797
## Test your logic app
9898

99-
To manually start your workflow, on the designer toolbar, select **Run**. The workflow creates a user, issues an access token for that user, and then removes the token and deletes the user. For more information, review [How to run your workflow](../../../logic-apps/quickstart-create-first-logic-app-workflow.md#run-workflow).
99+
To manually start your workflow, on the designer toolbar, select **Run**. The workflow creates a user, issues an access token for that user, and then removes the token and deletes the user. For more information, review [How to run your workflow](../../../logic-apps/quickstart-create-example-consumption-workflow.md#run-workflow).
100100

101101
Now, select **List chat thread messages**. In the action outputs, check for the message that was sent.
102102

@@ -106,7 +106,7 @@ Now, select **List chat thread messages**. In the action outputs, check for the
106106

107107
To remove a Communication Services subscription, delete the Communication Services resource or resource group. Deleting the resource group also deletes any other resources in that group. For more information, review [How to clean up Communication Services resources](../create-communication-resource.md#clean-up-resources).
108108

109-
To clean up your logic app workflow and related resources, review [how to clean up Logic Apps resources](../../../logic-apps/quickstart-create-first-logic-app-workflow.md#clean-up-resources).
109+
To clean up your logic app workflow and related resources, review [how to clean up Azure Logic Apps resources](../../../logic-apps/quickstart-create-example-consumption-workflow.md#clean-up-resources).
110110

111111
## Next steps
112112

articles/communication-services/quickstarts/email/logic-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ This quickstart will show how to send emails using the Azure Communication Servi
2424

2525
- An active Azure Communication Services resource, or [create a Communication Services resource](../create-communication-resource.md).
2626

27-
- An active Logic Apps resource (logic app), or [create a blank logic app but with the trigger that you want to use](../../../logic-apps/quickstart-create-first-logic-app-workflow.md). Currently, the Azure Communication Services Email connector provides only actions, so your logic app requires a trigger, at minimum.
27+
- An active Azure Logic Apps resource (logic app), or [create a Consumption logic app workflow with the trigger that you want to use](../../../logic-apps/quickstart-create-example-consumption-workflow.md). Currently, the Azure Communication Services Email connector provides only actions, so your logic app workflow requires a trigger, at minimum.
2828

2929
- An Azure Communication Services Email resource with a [configured domain](../email/create-email-communication-resource.md) or [custom domain](../email/add-custom-verified-domains.md).
3030

@@ -60,15 +60,15 @@ Add a new step in your workflow by using the Azure Communication Services Email
6060

6161
## Test your logic app
6262

63-
To manually start your workflow, on the designer toolbar, select **Run**. The workflow should create a user, issue an access token for that user, then remove it and delete the user. For more information, review [how to run your workflow](../../../logic-apps/quickstart-create-first-logic-app-workflow.md#run-workflow). You can check the outputs of these actions after the workflow runs successfully.
63+
To manually start your workflow, on the designer toolbar, select **Run**. The workflow should create a user, issue an access token for that user, then remove it and delete the user. For more information, review [how to run your workflow](../../../logic-apps/quickstart-create-example-consumption-workflow.md#run-workflow). You can check the outputs of these actions after the workflow runs successfully.
6464

6565
You should have an email in the address specified. Additionally, you can use the Get email message status action to check the status of emails send through the Send email action. To learn more actions, check the [Azure Communication Services Email connector](/connectors/acsemail/) documentation.
6666

6767
## Clean up resources
6868

6969
To remove a Communication Services subscription, delete the Communication Services resource or resource group. Deleting the resource group also deletes any other resources in that group. For more information, review [how to clean up Communication Services resources](../create-communication-resource.md#clean-up-resources).
7070

71-
To clean up your logic app workflow and related resources, review [how to clean up Logic Apps resources](../../../logic-apps/quickstart-create-first-logic-app-workflow.md#clean-up-resources).
71+
To clean up your logic app workflow and related resources, review [how to clean up Logic Apps resources](../../../logic-apps/quickstart-create-example-consumption-workflow.md#clean-up-resources).
7272

7373
## Next steps
7474

articles/communication-services/quickstarts/identity/access-tokens.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Learn more about [authentication concepts](../../concepts/authentication.md), ca
5959
To clean up and remove a Communication Services subscription, delete the resource or resource group. Deleting a resource group also deletes any other resources that are associated with it. For more information, see the "Clean up resources" section of [Create and manage Communication Services resources](../create-communication-resource.md#clean-up-resources).
6060

6161
::: zone pivot="platform-nocode"
62-
To clean up your logic app workflow and related resources, review [how to clean up Logic Apps resources](../../../logic-apps/quickstart-create-first-logic-app-workflow.md#clean-up-resources).
62+
To clean up your logic app workflow and related resources, review [how to clean up Azure Logic Apps resources](../../../logic-apps/quickstart-create-example-consumption-workflow.md#clean-up-resources).
6363
::: zone-end
6464

6565
::: zone pivot="platform-azportal,programming-language-java,programming-language-python,programming-language-javascript,programming-language-csharp,platform-azcli"

articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-no-code.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.author: sanchezjuan
1818

1919
- An active Azure Communication Services resource, or [create a Communication Services resource](../../../create-communication-resource.md).
2020

21-
- An active Logic Apps resource (logic app), or [create a blank logic app but with the trigger that you want to use](../../../../../logic-apps/quickstart-create-first-logic-app-workflow.md). Currently, the Azure Communication Services Identity connector provides only actions, so your logic app requires a trigger, at minimum.
21+
- An active Azure Logic Apps resource (logic app), or [create a Consumption logic app workflow with the trigger that you want to use](../../../../../logic-apps/quickstart-create-example-consumption-workflow.md). Currently, the Azure Communication Services Identity connector provides only actions, so your logic app requires a trigger, at minimum.
2222

2323
## Create user
2424

@@ -88,4 +88,4 @@ After you have a Communication Services identity, you can use the Issue a user a
8888

8989
## Test your logic app
9090

91-
To manually start your workflow, on the designer toolbar, select **Run**. The workflow should create a user, issue an access token for that user, then remove it and delete the user. For more information, review [how to run your workflow](../../../../../logic-apps/quickstart-create-first-logic-app-workflow.md#run-workflow). You can check the outputs of these actions after the workflow runs successfully.
91+
To manually start your workflow, on the designer toolbar, select **Run**. The workflow should create a user, issue an access token for that user, then remove it and delete the user. For more information, review [how to run your workflow](../../../../../logic-apps/quickstart-create-example-consumption-workflow.md#run-workflow). You can check the outputs of these actions after the workflow runs successfully.

articles/communication-services/quickstarts/sms/logic-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Although this quickstart focuses on using the connector to respond to a trigger,
2929

3030
- An active Azure Communication Services resource, or [create a Communication Services resource](../create-communication-resource.md).
3131

32-
- An active Logic Apps resource (logic app), or [create a blank logic app but with the trigger that you want to use](../../../logic-apps/quickstart-create-first-logic-app-workflow.md). Currently, the Azure Communication Services SMS connector provides only actions, so your logic app requires a trigger, at minimum.
32+
- An active Azure Logic Apps resource (logic app), or [create a Consumption logic app workflow with the trigger that you want to use](../../../logic-apps/quickstart-create-example-consumption-workflow.md). Currently, the Azure Communication Services SMS connector provides only actions, so your logic app workflow requires a trigger, at minimum.
3333

3434
This quickstart uses the **When a new email arrives** trigger, which is available with the [Office 365 Outlook connector](/connectors/office365/).
3535

@@ -99,13 +99,13 @@ Next, run your logic app workflow for testing.
9999

100100
## Test your logic app
101101

102-
To manually start your workflow, on the designer toolbar, select **Run**. Or, you can wait for the trigger to fire. In both cases, the workflow should send an SMS message to your specified destination phone number. For more information, review [how to run your workflow](../../../logic-apps/quickstart-create-first-logic-app-workflow.md#run-workflow).
102+
To manually start your workflow, on the designer toolbar, select **Run**. Or, you can wait for the trigger to fire. In both cases, the workflow should send an SMS message to your specified destination phone number. For more information, review [how to run your workflow](../../../logic-apps/quickstart-create-example-consumption-workflow.md#run-workflow).
103103

104104
## Clean up resources
105105

106106
To remove a Communication Services subscription, delete the Communication Services resource or resource group. Deleting the resource group also deletes any other resources in that group. For more information, review [how to clean up Communication Services resources](../create-communication-resource.md#clean-up-resources).
107107

108-
To clean up your logic app workflow and related resources, review [how to clean up Logic Apps resources](../../../logic-apps/quickstart-create-first-logic-app-workflow.md#clean-up-resources).
108+
To clean up your logic app workflow and related resources, review [how to clean up Azure Logic Apps resources](../../../logic-apps/quickstart-create-example-consumption-workflow.md#clean-up-resources).
109109

110110
## Next steps
111111

articles/connectors/connect-common-data-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,9 +49,9 @@ For technical information based on the connector's Swagger description, such as
4949

5050
* Basic knowledge about how to create either Consumption or Standard logic app workflows and the logic app from where you want to access the rows in your Dataverse database. To start your logic app with a Common Data Service trigger, you need a blank workflow. For more information, review the following resources:
5151

52-
* [Create your first Consumption logic app workflow](../logic-apps/quickstart-create-first-logic-app-workflow.md)
52+
* [Create an example Consumption logic app workflow](../logic-apps/quickstart-create-example-consumption-workflow.md)
5353

54-
* [Create a Standard logic app workflow](../logic-apps/create-single-tenant-workflows-azure-portal.md)
54+
* [Create an example Standard logic app workflow](../logic-apps/create-single-tenant-workflows-azure-portal.md)
5555

5656
## Add a Dataverse trigger
5757

articles/connectors/connectors-create-api-azure-event-hubs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ For all the operations and other technical information, such as properties, limi
3131

3232
* The logic app workflow where you want to access your event hub
3333

34-
To start a workflow with an Event Hubs trigger, you need an empty workflow. If you're new to [Azure Logic Apps](../logic-apps/logic-apps-overview.md), try this [quickstart to create an example logic app workflow](../logic-apps/quickstart-create-first-logic-app-workflow.md).
34+
To start a workflow with an Event Hubs trigger, you need an empty workflow. If you're new to [Azure Logic Apps](../logic-apps/logic-apps-overview.md), try this [quickstart to create an example Consumption logic app workflow](../logic-apps/quickstart-create-example-consumption-workflow.md).
3535

3636
<a name="permissions-connection-string"></a>
3737

0 commit comments

Comments
 (0)