Skip to content

Commit 207dfa5

Browse files
committed
Add banners to remaining ISE docs
1 parent 660cb85 commit 207dfa5

File tree

2 files changed

+36
-2
lines changed

2 files changed

+36
-2
lines changed

articles/logic-apps/customer-managed-keys-integration-service-environment.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,28 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: mijos, rarayudu, azla
77
ms.topic: how-to
8-
ms.date: 08/20/2022
8+
ms.date: 11/04/2022
99
---
1010

1111
# Set up customer-managed keys to encrypt data at rest for integration service environments (ISEs) in Azure Logic Apps
1212

13+
> [!IMPORTANT]
14+
>
15+
> On August 31, 2024, the ISE resource will retire, due to its dependency on Azure Cloud Services (classic),
16+
> which retires at the same time. Before the retirement date, export any logic apps from your ISE to Standard
17+
> logic apps so that you can avoid service disruption. Standard logic app workflows run in single-tenant Azure
18+
> Logic Apps and provide the same capabilities plus more.
19+
>
20+
> Starting November 1, 2022, you can no longer create new ISE resources. However, ISE resources existing
21+
> before this date are supported through August 31, 2024. For more information, see the following resources:
22+
>
23+
> - [ISE Retirement - what you need to know](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/ise-retirement-what-you-need-to-know/ba-p/3645220)
24+
> - [Single-tenant versus multi-tenant and integration service environment for Azure Logic Apps](single-tenant-overview-compare.md)
25+
> - [Azure Logic Apps pricing](https://azure.microsoft.com/pricing/details/logic-apps/)
26+
> - [Export ISE workflows to a Standard logic app](export-from-ise-to-standard-logic-app.md)
27+
> - [Integration Services Environment will be retired on 31 August 2024 - transition to Logic Apps Standard](https://azure.microsoft.com/updates/integration-services-environment-will-be-retired-on-31-august-2024-transition-to-logic-apps-standard/)
28+
> - [Cloud Services (classic) deployment model is retiring on 31 August 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/)
29+
1330
Azure Logic Apps relies on Azure Storage to store and automatically [encrypt data at rest](../storage/common/storage-service-encryption.md). This encryption protects your data and helps you meet your organizational security and compliance commitments. By default, Azure Storage uses Microsoft-managed keys to encrypt your data. For more information about how Azure Storage encryption works, see [Azure Storage encryption for data at rest](../storage/common/storage-service-encryption.md) and [Azure Data Encryption-at-Rest](../security/fundamentals/encryption-atrest.md).
1431

1532
When you create an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md) for hosting your logic apps, and you want more control over the encryption keys used by Azure Storage, you can set up, use, and manage your own key by using [Azure Key Vault](../key-vault/general/overview.md). This capability is known as "Bring Your Own Key" (BYOK), and your key is called a "customer-managed key". With this capability, Azure Storage automatically enables [double encryption or *infrastructure encryption* using platform-managed keys](../security/fundamentals/double-encryption.md) for your key. To learn more, see [Doubly encrypt data with infrastructure encryption](../storage/common/storage-service-encryption.md#doubly-encrypt-data-with-infrastructure-encryption).

articles/logic-apps/ise-manage-integration-service-environment.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,28 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 08/20/2022
8+
ms.date: 11/04/2022
99
---
1010

1111
# Manage your integration service environment (ISE) in Azure Logic Apps
1212

13+
> [!IMPORTANT]
14+
>
15+
> On August 31, 2024, the ISE resource will retire, due to its dependency on Azure Cloud Services (classic),
16+
> which retires at the same time. Before the retirement date, export any logic apps from your ISE to Standard
17+
> logic apps so that you can avoid service disruption. Standard logic app workflows run in single-tenant Azure
18+
> Logic Apps and provide the same capabilities plus more.
19+
>
20+
> Starting November 1, 2022, you can no longer create new ISE resources. However, ISE resources existing
21+
> before this date are supported through August 31, 2024. For more information, see the following resources:
22+
>
23+
> - [ISE Retirement - what you need to know](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/ise-retirement-what-you-need-to-know/ba-p/3645220)
24+
> - [Single-tenant versus multi-tenant and integration service environment for Azure Logic Apps](single-tenant-overview-compare.md)
25+
> - [Azure Logic Apps pricing](https://azure.microsoft.com/pricing/details/logic-apps/)
26+
> - [Export ISE workflows to a Standard logic app](export-from-ise-to-standard-logic-app.md)
27+
> - [Integration Services Environment will be retired on 31 August 2024 - transition to Logic Apps Standard](https://azure.microsoft.com/updates/integration-services-environment-will-be-retired-on-31-august-2024-transition-to-logic-apps-standard/)
28+
> - [Cloud Services (classic) deployment model is retiring on 31 August 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/)
29+
1330
This article shows how to perform management tasks for your [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), for example:
1431

1532
* Manage the resources such as multi-tenant based logic apps, connections, integration accounts, and connectors in your ISE.

0 commit comments

Comments
 (0)