Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into newNetwork

Author: roygara

articles/api-management/send-one-way-request-policy.md

@@ -89,6 +89,6 @@ This example uses the `send-one-way-request` policy to send a message to a Slack
 
 ## Related policies
 
-* [Intergration and external communication](api-management-policies.md#integration-and-external-communication)
+* [Integration and external communication](api-management-policies.md#integration-and-external-communication)
 
 [!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]

articles/app-service/index.yml

@@ -9,7 +9,7 @@ metadata:
   ms.topic: landing-page
   ms.author: msangapu
   ms.service: azure-app-service
-  ms.date: 01/22/2025
+  ms.date: 06/10/2025
   ms.custom: UpdateFrequency3
 
 landingContent:
@@ -74,12 +74,20 @@ landingContent:
           - text: Invoke OpenAPI web app from Azure AI Agent
             url: invoke-openapi-web-app-from-azure-ai-agent-service.md
 
-  - title: Troubleshoot with Azure SRE Agent (AI)
+  - title: Secure and deploy  
     linkLists:
+      - linkListType: concept
+        links:
+          - text: Security in Azure App Service
+            url: overview-security.md        
       - linkListType: tutorial
         links:
-          - text: Fix application issues with SRE Agent
-            url: tutorial-sre-agent.md
+          - text: Secure with custom domain and certificate
+            url: tutorial-secure-domain-certificate.md
+          - text: Continuous deployment
+            url: deploy-continuous-deployment.md
+          - text: Upload content with FTP
+            url: deploy-ftp.md
 
   - title: Build a CRUD app
     linkLists:
@@ -102,18 +110,9 @@ landingContent:
           - text: REST API
             url: /rest/api/appservice/
 
-  - title: Secure and deploy  
+  - title: Troubleshoot with Azure SRE Agent (AI)
     linkLists:
-      - linkListType: concept
-        links:
-          - text: Security in Azure App Service
-            url: overview-security.md        
       - linkListType: tutorial
         links:
-          - text: Secure with custom domain and certificate
-            url: tutorial-secure-domain-certificate.md
-          - text: Continuous deployment
-            url: deploy-continuous-deployment.md
-          - text: Upload content with FTP
-            url: deploy-ftp.md
-
+          - text: Fix application issues with SRE Agent
+            url: tutorial-sre-agent.md

articles/automation/automation-child-runbooks.md

@@ -42,16 +42,18 @@ The parameters of a child runbook called inline can be of any data type, includi
 Currently, PowerShell 5.1 is supported and only certain runbook types can call each other:
 
 * A [PowerShell runbook](automation-runbook-types.md#powershell-runbooks) and a [graphical runbook](automation-runbook-types.md#graphical-runbooks) can call each other inline, because both are PowerShell based.
-* A [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks) and a graphical PowerShell Workflow runbook can call each other inline, because both are PowerShell Workflow based.
+* A [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks) can call another PowerShell Workflow runbook inline.
 * The PowerShell types and the PowerShell Workflow types can't call each other inline. They must use `Start-AzAutomationRunbook`.
 
 > [!IMPORTANT]
-> Executing child scripts using `.\child-runbook.ps1` is not supported in PowerShell 7.1 and PowerShell 7.2 
+  > * Executing child scripts using `.\child-runbook.ps1` is not supported in PowerShell 7.1 and PowerShell 7.2 
   **Workaround**: Use `Start-AutomationRunbook` ([internal cmdlet](/azure/automation/shared-resources/modules#internal-cmdlets)) or `Start-AzAutomationRunbook` (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) to start another runbook from parent runbook.
+  > * Executing child scripts using Graphical PowerShell Workflow runbooks is not supported.
+  **Workaround**: Use Start-AzAutomationRunbook (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) from within the parent runbook (via an InlineScript block) to start another runbook.
 
-The publish order of runbooks matters only for PowerShell Workflow and graphical PowerShell Workflow runbooks.
+The publish order of runbooks matters only for PowerShell Workflow runbooks.
 
-When your runbook calls a graphical or PowerShell Workflow child runbook by using inline execution, it uses the name of the runbook. The name must start with `.\\` to specify that the script is in the local directory.
+When your runbook calls a PowerShell Workflow child runbook by using inline execution, it uses the name of the runbook. The name must start with `.\\` to specify that the script is in the local directory.
 
 ### Example
 

articles/automation/troubleshoot/runbooks.md

@@ -11,6 +11,41 @@ ms.custom: has-adal-ref, devx-track-azurepowershell
 
  This article describes runbook issues that might occur and how to resolve them. For general information, see [Runbook execution in Azure Automation](../automation-runbook-execution.md).
 
+## Graphical PowerShell Workflow runbooks with child runbooks fail to execute
+
+### Issue
+Graphical PowerShell Workflow runbooks with child runbooks fail to execute as expected.
+
+### Cause
+To improve the security posture of Graphical PowerShell Workflow runbooks, the service no longer executes Graphical PowerShell Workflow runbooks with child scripts.
+
+### Resolution
+
+Workaround is to use Start-AzAutomationRunbook (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) from within the parent runbook to start child runbook. For example, use the InlineScript block:
+
+```
+
+$job = Start-AzAutomationRunbook `
+
+    -AutomationAccountName "MyAccount" `
+
+    -ResourceGroupName "MyRG" `
+
+    -Name "ReusableTaskRunbook" `
+
+    -Parameters @{ TaskId = '1234' }
+
+ 
+
+#Optional: Wait for job completion
+
+do {
+
+    Start-Sleep -Seconds 5
+
+    $jobStatus = Get-AzAutomationJob -Id $job.Id -AutomationAccountName "MyAccount" -ResourceGroupName "MyRG"} while ($jobStatus.Status -ne "Completed")
+
+```
 
 ## It is no longer possible to use cmdlets from imported non-default modules in graphical PowerShell runbooks
 

articles/azure-functions/flex-consumption-plan.md

@@ -147,6 +147,7 @@ Keep these other considerations in mind when using Flex Consumption plan:
 + **Triggers**: While all triggers are fully supported in a Flex Consumption plan, the Blob storage trigger only supports the [Event Grid source](./functions-event-grid-blob-trigger.md). Non-C# function apps must use version `[4.0.0, 5.0.0)` of the [extension bundle](./extension-bundles.md), or a later version. 
 + **Regions**: Not all regions are currently supported. To learn more, see [View currently supported regions](flex-consumption-how-to.md#view-currently-supported-regions).
 + **Deployments**: Deployment slots aren't currently supported.
++ **Proxies**: Functions Proxies aren't supported. Consider integrating your function apps with Azure API Management.
 + **Scale**: The lowest maximum scale is currently `40`. The highest currently supported value is `1000`. 
 + **Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#managed-dependencies-feature) aren't supported by Flex Consumption. You must instead [upload modules with app content](functions-reference-powershell.md#including-modules-in-app-content).
 + **Diagnostic settings**: Diagnostic settings aren't currently supported.

articles/azure-functions/functions-app-settings.md

@@ -203,7 +203,14 @@ A comma-delimited list of beta features to enable. Beta features enabled by thes
 |---|------------|
 |AzureWebJobsFeatureFlags|`feature1,feature2,EnableProxies`|
 
-Add `EnableProxies` to this list to re-enable proxies on version 4.x of the Functions runtime while you plan your migration to Azure API Management. For more information, see [Re-enable proxies in Functions v4.x](./legacy-proxies.md#re-enable-proxies-in-functions-v4x). 
+If your app currently has this setting, add new flags to the end of the comma-delineated list. 
+
+Currently-supported feature flags:
+
+|Flag value | Description |
+| ----- | ----- |
+| `EnableProxies` | Re-enables proxies on version 4.x of the Functions runtime while you plan your migration to Azure API Management. For more information, see [Re-enable proxies in Functions v4.x](./legacy-proxies.md#re-enable-proxies-in-functions-v4x). |
+| `EnableAzureMonitorTimeIsoFormat` | Enables the `ISO 8601` time format in Azure Monitor logs for Linux apps running on a Dedicated (App Service) plan. |
 
 ## AzureWebJobsKubernetesSecretName 
 

articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md

@@ -148,13 +148,6 @@ You need to assign a public switched telephone network (PSTN) number to your Res
 
 1. Also, if you plan to make outbound PSTN calls using your Resource Accounts assigned phone number, now is a good time to assign a [Microsoft Teams Calling Plan](/microsoftteams/calling-plans-for-office-365).
 
-### CCaaS Developer: Configure Call Automation to use preproduction environment 
-
-Use the following code snippet in C# to set use of preproduction environment for Teams Phone extensibility. The Next-PMA preprod environment has the latest code base and bug fixes. 
-
-```csharp
-CallAutomationClient callAutomationClient = new CallAutomationClient(new Uri("https://nextpma.plat.skype.com:6448"), acsConnectionString); 
-```
 
 ### CCaaS Developer: Get Resource Account Information
 

articles/communication-services/samples/includes/call-automation-azure-openai-csharp.md

@@ -25,6 +25,9 @@ This server-side application helps create a virtual assistant that can handle ph
 - Azure Dev Tunnels. For details, see  [Enable dev tunnel](/azure/developer/dev-tunnels/get-started)
 - An Azure OpenAI Resource and Deployed Model. See [instructions](/azure/ai-services/openai/how-to/create-resource?pivots=web-portal).
 
+> [!NOTE]
+> Bidirectional Streaming in Azure Communication Services is generally available, but the Azure OpenAI real-time API has its own release schedule. For up-to-date info on the API’s availability, check out the [official docs](/azure/ai-services/openai/concepts/models?tabs=global-standard%2Cstandard-chat-completions#audio-models).
+
 ## Set up instructions
 
 Before running this sample, you need to set up the resources with the following configuration updates:

articles/communication-services/samples/includes/call-automation-azure-openai-js.md

@@ -27,6 +27,9 @@ This server-side application helps create a virtual assistant that can handle ph
 - Azure Dev Tunnels. For details, see  [Enable dev tunnel](/azure/developer/dev-tunnels/get-started)
 - An Azure OpenAI Resource and Deployed Model. See [instructions](/azure/ai-services/openai/how-to/create-resource?pivots=web-portal).
 
+> [!NOTE]
+> Bidirectional Streaming in Azure Communication Services is generally available, but the Azure OpenAI real-time API has its own release schedule. For up-to-date info on the API’s availability, check out the [official docs](/azure/ai-services/openai/concepts/models?tabs=global-standard%2Cstandard-chat-completions#audio-models).
+
 
 ## Before running the sample for the first time
 

articles/confidential-computing/create-confidential-vm-from-compute-gallery.md

@@ -30,7 +30,7 @@ The resulting image version can be used only to create confidential VMs.
 This image version can be replicated within the source region **but cannot be replicated to a different region** or across subscriptions currently.
 
 > [!NOTE]
-> If you want to create an image from a Windows confidential VM that has confidential compute disk encryption enabled with a platform-managed key or a customer-managed key, you can only create a specialized image. This limitation exists because the generalization tool (**sysprep**), might not be able to generalized the encrypted image source. This limitation applies to the OS disk, which is implicitly created along with the Windows confidential VM, and the snapshot created from this OS disk.
+> If you want to create an image from a Windows confidential VM that has confidential compute disk encryption enabled with a platform-managed key or a customer-managed key, you can create a specialized or generalized image.
 
 ### Create a Confidential VM type image using Confidential VM capture