Remove more references to ISE

Author: ecfan

articles/azure-monitor/autoscale/autoscale-overview.md

@@ -130,7 +130,6 @@ Autoscale supports the following services.
 | Azure Spring Apps                                 | [Set up autoscale for applications](../../spring-apps/enterprise/how-to-setup-autoscale.md)                                                      |
 | Azure Media Services                              | [Autoscaling in Media Services](/azure/media-services/latest/release-notes#autoscaling)                                                          |
 | Azure Service Bus                                 | [Automatically update messaging units of an Azure Service Bus namespace](../../service-bus-messaging/automate-update-messaging-units.md)         |
-| Azure Logic Apps - Integration service environment (ISE) | [Add ISE capacity](../../logic-apps/ise-manage-integration-service-environment.md#add-ise-capacity)                                       |
 
 ## Next steps
 

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

@@ -188,10 +188,6 @@ In Azure Logic Apps, an [action](../logic-apps/logic-apps-overview.md#logic-app-
 
 For all the operations and other technical information, such as properties, limits, and so on, review the [Event Hubs connector's reference page](/connectors/eventhubs/).
 
-> [!NOTE]
-> For logic apps hosted in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
-> the connector's ISE version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
-
 ## Next steps
 
 * [Managed connectors for Azure Logic Apps](managed.md)

articles/connectors/introduction.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
-ms.date: 01/10/2024
+ms.date: 09/06/2024
 ms.custom: engagement-fy23
 # Customer intent: As a developer, I want to learn how connectors help me access data, events, and resources in other apps, services, systems, and platforms from my workflow in Azure Logic Apps.
 ---
@@ -136,46 +136,6 @@ In Standard workflows for single-tenant Azure Logic Apps, you can create nativel
 
 * [Create service provider-based custom built-in connectors for Standard workflows](../logic-apps/create-custom-built-in-connector-standard.md)
 
-## ISE and connectors
-
-> [!IMPORTANT]
->
-> On August 31, 2024, the ISE resource retires, due to its dependency on Azure Cloud Services (classic), 
-> which retires at the same time. Before the retirement date, export any logic apps from your ISE to Standard 
-> logic apps to avoid service disruption. Standard logic app workflows run in single-tenant Azure Logic Apps 
-> and provide the same capabilities plus more. For example, Standard workflows support using private endpoints 
-> for inbound traffic so that your workflows can communicate privately and securely with virtual networks. 
-> Standard workflows also support virtual network integration for outbound traffic. For more information, 
-> review [Secure traffic between virtual networks and single-tenant Azure Logic Apps using private endpoints](/azure/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint).
-
-If you use a dedicated [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md) where workflows can directly access to resources in an Azure virtual network, you can build, deploy, and run your workflows on dedicated resources.
-
-Custom connectors created within an ISE don't work with the on-premises data gateway. However, these connectors can directly access on-premises data sources that are connected to an Azure virtual network hosting the ISE. So, logic app workflows in an ISE most likely don't need the data gateway when communicating with those resources. If you have custom connectors that you created outside an ISE that require the on-premises data gateway, workflows in an ISE can use those connectors.
-
-In the workflow designer, when you browse the built-in connectors or managed connectors that you want to use for workflows in an ISE, the **CORE** label appears on built-in connectors, while the **ISE** label appears on managed connectors that are designed to work with an ISE.
-
-:::row:::
-    :::column:::
-        ![Example CORE connector](./media/apis-list/example-core-connector.png)
-        <br><br>**CORE**
-        <br><br>Built-in connectors with this label run in the same ISE as your workflows.
-    :::column-end:::
-    :::column:::
-        ![Example ISE connector](./media/apis-list/example-ise-connector.png)
-        <br><br>**ISE**
-        <br><br>Managed connectors with this label run in the same ISE as your workflows.
-        <br><br>If you have an on-premises system that's connected to an Azure virtual network, an ISE lets your workflows directly access that system without using the [on-premises data gateway](../logic-apps/logic-apps-gateway-connection.md). Instead, you can either use that system's **ISE** connector if available, an HTTP action, or a [custom connector](#custom-connectors-and-apis).
-        <br><br>For on-premises systems that don't have **ISE** connectors, use the on-premises data gateway. To find available ISE connectors, review [ISE connectors](#ise-and-connectors).
-    :::column-end:::
-    :::column:::
-        ![Example non-ISE connector](./media/apis-list/example-multitenant-connector.png)
-        <br><br>No label
-        <br><br>All other connectors without a label, which you can continue to use, run in the global, multitenant Logic Apps service.
-    :::column-end:::
-    :::column:::
-    :::column-end:::
-:::row-end:::
-
 ## Known issues
 
 The following table includes known issues for connectors in Azure Logic Apps:

articles/connectors/managed.md

@@ -256,127 +256,6 @@ For more information, review the following documentation:
     :::column-end:::
 :::row-end:::
 
-## ISE connectors
-
-In an integration service environment (ISE), these managed connectors also have [ISE versions](introduction.md#ise-and-connectors), which have different capabilities than their multitenant versions:
-
-> [!NOTE]
->
-> Workflows that run in an ISE and their connectors, regardless where those connectors run, follow a fixed pricing plan versus the Consumption pricing plan. For more information, review [Azure Logic Apps pricing model](../logic-apps/logic-apps-pricing.md) and [Azure Logic Apps pricing details](https://azure.microsoft.com/pricing/details/logic-apps/).
-
-:::row:::
-    :::column:::
-        [![AS2 ISE icon][as2-icon]][as2-doc]
-        <br><br>[**AS2** ISE][as2-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Automation ISE icon][azure-automation-icon]][azure-automation-doc]
-        <br><br>[**Azure Automation** ISE][azure-automation-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Blob Storage ISE icon][azure-blob-storage-icon]][azure-blob-storage-doc]
-        <br><br>[**Azure Blob Storage** ISE][azure-blob-storage-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Cosmos DB ISE icon][azure-cosmos-db-icon]][azure-cosmos-db-doc]
-        <br><br>[**Azure Cosmos DB** ISE][azure-cosmos-db-doc]
-    :::column-end:::
-:::row-end:::
-:::row:::
-    :::column:::
-        [![Azure Event Hubs ISE icon][azure-event-hubs-icon]][azure-event-hubs-doc]
-        <br><br>[**Azure Event Hubs** ISE][azure-event-hubs-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Event Grid ISE icon][azure-event-grid-icon]][azure-event-grid-doc]
-        <br><br>[**Azure Event Grid** ISE][azure-event-grid-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Files ISE icon][azure-file-storage-icon]][azure-file-storage-doc]
-        <br><br>[**Azure Files** ISE][azure-file-storage-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Key Vault ISE icon][azure-key-vault-icon]][azure-key-vault-doc]
-        <br><br>[**Azure Key Vault** ISE][azure-key-vault-doc]
-    :::column-end:::
-:::row-end:::
-:::row:::
-    :::column:::
-        [![Azure Monitor Logs ISE icon][azure-monitor-logs-icon]][azure-monitor-logs-doc]
-        <br><br>[**Azure Monitor Logs** ISE][azure-monitor-logs-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Service Bus ISE icon][azure-service-bus-icon]][azure-service-bus-doc]
-        <br><br>[**Azure Service Bus** ISE][azure-service-bus-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Synapse Analytics ISE icon][azure-sql-data-warehouse-icon]][azure-sql-data-warehouse-doc]
-        <br><br>[**Azure Synapse Analytics** ISE][azure-sql-data-warehouse-doc]
-    :::column-end:::
-    :::column:::
-        [![Azure Table Storage ISE icon][azure-table-storage-icon]][azure-table-storage-doc]
-        <br><br>[**Azure Table Storage** ISE][azure-table-storage-doc]
-    :::column-end:::
-:::row-end:::
-:::row:::
-    :::column:::
-        [![Azure Queues ISE icon][azure-queues-icon]][azure-queues-doc]
-        <br><br>[**Azure Queues** ISE][azure-queues-doc]
-    :::column-end:::
-    :::column:::
-        [![EDIFACT ISE icon][edifact-icon]][edifact-doc]
-        <br><br>[**EDIFACT** ISE][edifact-doc]
-    :::column-end:::
-    :::column:::
-        [![File System ISE icon][file-system-icon]][file-system-doc]
-        <br><br>[**File System** ISE][file-system-doc]
-    :::column-end:::
-    :::column:::
-        [![FTP ISE icon][ftp-icon]][ftp-doc]
-        <br><br>[**FTP** ISE][ftp-doc]
-    :::column-end:::
-:::row-end:::
-:::row:::
-    :::column:::
-        [![IBM 3270 ISE icon][ibm-3270-icon]][ibm-3270-doc]
-        <br><br>[**IBM 3270** ISE][ibm-3270-doc]
-    :::column-end:::
-    :::column:::
-        [![IBM DB2 ISE icon][ibm-db2-icon]][ibm-db2-doc]
-        <br><br>[**IBM DB2** ISE][ibm-db2-doc]
-    :::column-end:::
-    :::column:::
-        [![IBM MQ ISE icon][ibm-mq-icon]][ibm-mq-doc]
-        <br><br>[**IBM MQ** ISE][ibm-mq-doc]
-    :::column-end:::
-    :::column:::
-        [![SAP ISE icon][sap-icon]][sap-connector-doc]
-        <br><br>[**SAP** ISE][sap-connector-doc]
-    :::column-end:::
-:::row-end:::
-:::row:::
-    :::column:::
-        [![SFTP-SSH ISE icon][sftp-ssh-icon]][sftp-ssh-doc]
-        <br><br>[**SFTP-SSH** ISE][sftp-ssh-doc]
-    :::column-end:::
-    :::column:::
-        [![SMTP ISE icon][smtp-icon]][smtp-doc]
-        <br><br>[**SMTP** ISE][smtp-doc]
-    :::column-end:::
-    :::column:::
-        [![SQL Server ISE icon][sql-server-icon]][sql-server-doc]
-        <br><br>[**SQL Server** ISE][sql-server-doc]
-    :::column-end:::
-    :::column:::
-        [![X12 ISE icon][x12-icon]][x12-doc]
-        <br><br>[**X12** ISE][x12-doc]
-    :::column-end:::
-:::row-end:::
-
-For more information, see these topics:
-
-* [Access to Azure virtual network resources from Azure Logic Apps](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md)
-* [Azure Logic Apps pricing model](../logic-apps/logic-apps-pricing.md)
 
 ## Next steps
 

articles/logic-apps/.openpublishing.redirection.logic-apps.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md",
+            "redirect_url": "/azure/logic-apps/single-tenant-overview-compare",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/logic-apps/connect-virtual-network-vnet-set-up-single-ip-address.md",
             "redirect_url": "/azure/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint",