Skip to content

Commit 2640a9b

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-screenshot
2 parents e0854b0 + dbedc84 commit 2640a9b

File tree

121 files changed

+317
-235
lines changed

Some content is hidden

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

121 files changed

+317
-235
lines changed

articles/automation/overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Automation overview
33
description: This article tells what Azure Automation is and how to use it to automate the lifecycle of infrastructure and applications.
44
services: automation
55
keywords: azure automation, DSC, powershell, state configuration, change tracking, DSC, inventory, runbooks, python, graphical
6-
ms.date: 03/17/2025
6+
ms.date: 03/21/2025
77
ms.topic: overview
88
ms.custom: linux-related-content
99
---
@@ -16,7 +16,7 @@ Automation is needed in three broad areas of cloud operations:
1616
* Response - Create event-based automation to diagnose and resolve issues.
1717
* Orchestrate - Orchestrate and integrate your automation with other Azure or third party services and products.
1818

19-
Azure Automation delivers a cloud-based automation, operating system updates, and configuration service that supports consistent management across your Azure and non-Azure environments. It includes process automation, configuration management, shared capabilities, and heterogeneous features.
19+
Azure Automation delivers a cloud-based automation service that supports consistent management across your Azure and non-Azure environments. It includes process automation, configuration management, shared capabilities, and heterogeneous features.
2020

2121
:::image type="content" source="./media/overview/automation-overview.png" alt-text="Diagram shows the Automation capabilities." lightbox="./media/overview/automation-overview.png":::
2222

articles/connectors/connectors-azure-application-insights.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 01/10/2024
8+
ms.date: 03/21/2025
99
# Customer intent: As a developer, I want to get telemetry from an Application Insights resource to use with my workflow in Azure Logic Apps.
1010
---
1111

articles/connectors/connectors-azure-monitor-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 02/08/2024
8+
ms.date: 03/21/2025
99
# Customer intent: As a developer, I want to get log data from my Log Analytics workspace or telemetry from my Application Insights resource to use with my workflow in Azure Logic Apps.
1010
---
1111

articles/healthcare-apis/includes/fhir-bulk-delete-operation.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,3 +127,16 @@ Here's a list of error messages that might occur if the bulk delete operation fa
127127
> [!NOTE]
128128
> If you cancel and then restart a bulk delete job, the deletion process resumes from where it was stopped.
129129
130+
## Preview capabilities for the bulk delete operation
131+
### `$bulk-delete` with `_include` and `_revinclude`
132+
Note: When using FHIR service-supported search parameters with `$bulk-delete`, the `$bulk-delete` operation now supports using `_include` and `_revinclude` in the search criteria for conditional and bulk delete. Please note that this does not affect current behavior of singular deletes, which does not support extra parameters. Additionally, when using bulk delete with FHIR search parameters, consider using the same query in a FHIR search first, so that you can verify the data that you want to delete.
133+
134+
Some examples of using `$bulk-delete` with `_include` and `_revinclude`:
135+
136+
The following example using `_revinclude` will bulk delete all Patient resources that were last updated before 12/18/2021, as well as all resources that reference to those patients:
137+
138+
`DELETE [base]/Patient/$bulk-delete?_lastUpdated=lt2021-12-18&_revinclude=*:*`
139+
140+
The following example using `_include` will bulk delete all DiagnosticReport resources that were last updated before 12/18/2021, as well as all ServiceRequest resources that are referenced by those DiagnosticReport resources (via DiagnosticReport.basedOn relationship), and all Encounter resources that are referenced by those ServiceRequest resources (via ServiceRequest.encounters relationship):
141+
142+
`DELETE [base]/DiagnosticReport/$bulk-delete?_lastUpdated=lt2021-12-12&_include=DiagnosticReport:based-on:ServiceRequest&_include:iterate=ServiceRequest:encounter`

articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,26 @@
11
---
22
title: Create and deploy workflows with Azure Arc-enabled Logic Apps
3-
description: Create and deploy single-tenant based logic app workflows that run anywhere that Kubernetes can run.
3+
description: Create and deploy Standard logic app workflows that run anywhere that Kubernetes can run.
44
services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 08/01/2024
8+
ms.date: 03/22/2025
99
ms.custom: devx-track-azurecli
10-
#Customer intent: As a developer, I want to learn how to create and deploy automated Logic Apps workflows that can run anywhere that Kubernetes can run.
10+
#Customer intent: As a developer, I want to learn how to create and deploy automated Azure Logic Apps workflows that can run anywhere that Kubernetes can run.
1111
---
1212

1313
# Create and deploy single-tenant based logic app workflows with Azure Arc-enabled Logic Apps (Preview)
1414

1515
> [!NOTE]
16-
> This capability is in preview and is subject to the
16+
>
17+
> Standard workflows can now deploy and run in partially connected environments hosted on your own infrastructure.
18+
> For more information, see the following documentation:
19+
>
20+
> - [Set up your own infrastructure for Standard logic app workflows using hybrid deployment](/azure/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements)
21+
> - [Create Standard logic app workflows for hybrid deployment on your own infrastructure](/azure/logic-apps/create-standard-workflows-hybrid-deployment?tabs=azure-portal)
22+
>
23+
> The following capability is in preview and is subject to the
1724
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
1825
1926
With Azure Arc-enabled Logic Apps, you can create and deploy single-tenant based logic app workflows to a Kubernetes infrastructure that you operate and manage. Your logic apps run in a *custom location* that is mapped to an Azure Arc-enabled Kubernetes cluster where you installed and enabled the Azure App Service platform extensions bundle.

articles/logic-apps/azure-arc-enabled-logic-apps-overview.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,21 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, kewear, rohithah, archidda, azla
77
ms.topic: overview
8-
ms.date: 02/19/2025
8+
ms.date: 03/22/2025
99
#Customer intent: As a developer, I want to learn about automated Azure Arc-enabled logic app workflows that can run anywhere that Kubernetes can run.
1010
---
1111

1212
# What is Azure Arc-enabled Logic Apps? (Preview)
1313

1414
> [!NOTE]
15-
> This capability is in preview and is subject to the
15+
>
16+
> Standard workflows can now deploy and run in partially connected environments hosted on your own infrastructure.
17+
> For more information, see the following documentation:
18+
>
19+
> - [Set up your own infrastructure for Standard logic app workflows using hybrid deployment](/azure/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements)
20+
> - [Create Standard logic app workflows for hybrid deployment on your own infrastructure](/azure/logic-apps/create-standard-workflows-hybrid-deployment?tabs=azure-portal)
21+
>
22+
> The following capability is in preview and is subject to the
1623
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
1724
1825
With Azure Arc-enabled Logic Apps, you can develop and run single-tenant based logic apps anywhere that Kubernetes can run. For example, you can run your logic app workflows on Azure, Azure Kubernetes Service, on premises, and even other cloud providers. This offering provides a centralized single-pane-of-glass management platform through Azure Arc and the Azure portal for the following capabilities:

articles/logic-apps/logic-apps-create-api-app.md

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
2-
title: Create web APIs & REST APIs for Azure Logic Apps
3-
description: Create web APIs & REST APIs to call your APIs, services, or systems for system integrations in Azure Logic Apps
2+
title: Patterns for web APIs and REST APIs
3+
description: Patterns for web APIs and REST APIs so you can call your APIs, services, or systems from workflows in Azure Logic Apps.
44
services: logic-apps
55
ms.suite: integration
6-
ms.reviewer: azla
6+
ms.reviewer: estfan, azla
77
ms.topic: conceptual
8-
ms.date: 10/23/2023
8+
ms.date: 03/21/2024
99
---
1010

11-
# Create custom APIs you can call from Azure Logic Apps
11+
# Patterns for custom web APIs and REST APIs you can call from Azure Logic Apps
1212

1313
[!INCLUDE [logic-apps-sku-consumption](~/reusable-content/ce-skilling/azure/includes/logic-apps-sku-consumption.md)]
1414

@@ -369,14 +369,6 @@ Power Automate, and Microsoft Power Apps, you must add security,
369369
register your APIs as Azure Logic Apps connectors, and nominate your connectors for the
370370
[Microsoft Azure Certified program](https://azure.microsoft.com/marketplace/programs/certified/logic-apps/).
371371

372-
## Get support
373-
374-
* For specific help with custom APIs,
375-
376-
377-
* For questions, visit the
378-
[Microsoft Q&A question page for Azure Logic Apps](/answers/topics/azure-logic-apps.html).
379-
380372
## Next steps
381373

382374
* [Handle errors and exceptions](../logic-apps/logic-apps-exception-handling.md)

articles/logic-apps/logic-apps-enterprise-integration-edifact-contrl-acknowledgment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: praveensri
77
ms.author: psrivas
88
ms.reviewer: estfan, divswa, azla
99
ms.topic: conceptual
10-
ms.date: 08/15/2023
10+
ms.date: 03/22/2025
1111
---
1212

1313
# CONTRL acknowledgments and error codes for EDIFACT messages in Azure Logic Apps

0 commit comments

Comments
 (0)