Clarify managed identity support for storage

Author: xuehongg

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

@@ -7,7 +7,7 @@ ms.suite: integration
 ms.reviewer: estfan, azla
 ms.collection: ce-skilling-ai-copilot
 ms.topic: how-to
-ms.date: 09/27/2024
+ms.date: 10/26/2024
 # Customer intent: As a developer, I want to create my first example Standard logic app workflow that runs in single-tenant Azure Logic Apps using the Azure portal.
 ---
 
@@ -458,7 +458,7 @@ By default, your Standard logic app authenticates access to your Azure Storage a
 
    1. On the logic app menu, under **Settings**, select **Configuration**.
 
-   1. On the **Workflow runtime settings** tab, for **Runtime Scale Monitoring**, select **On**.
+   1. On the **Workflow runtime settings** tab, for **Runtime Scale Monitoring**, select **On**. If your logic app uses the App Service Environment (ASE) v3 hosting option, this step is not needed because ASE does not support **Runtime Scale Monitoring**.
 
    1. On the **Configuration** toolbar, select **Save**.
 

articles/logic-apps/single-tenant-overview-compare.md

@@ -5,7 +5,7 @@ services: azure-logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
-ms.date: 09/12/2024
+ms.date: 10/26/2024
 ---
 
 # Differences between Standard single-tenant logic apps versus Consumption multitenant logic apps
@@ -319,8 +319,6 @@ For the **Standard** logic app workflow, these capabilities have changed, or the
 
 * **Azure API Management**: You currently can't import a **Standard** logic app resource into Azure API Management. However, you can import a **Consumption** logic app resource.
 
-* **Authentication to backend storage**: Single-tenant Azure Logic Apps relies only on storage access keys to connect with the backend Azure Storage account. Alternative authentication methods, such as Microsoft Entra ID (Enterprise ID) and managed identity, currently aren't supported. So, when you deploy an Azure storage account alongside a **Standard** logic app, make sure that you enable storage access keys.
-
 <a name="firewall-permissions"></a>
 
 ## Strict network and firewall traffic permissions