Merge pull request #53076 from JeffKoMS/se-bug-fixes-01092026

Se bug fixes 01092026 - minor changes across three modules

Author: prmerger-automator[bot]

learn-pr/wwl-azure/azure-event-hubs/includes/3-event-hubs-capture.md

@@ -28,7 +28,7 @@ https://mystorageaccount.blob.core.windows.net/mycontainer/mynamespace/myeventhu
 
 ## Scaling to throughput units
 
-Event Hubs traffic is controlled by throughput units. A single throughput unit allows 1 MB per second or 1,000 events per second of ingress and twice that amount of egress. Standard Event Hubs can be configured with 1-20 throughput units, and you can purchase more with a quota increase support request. Usage beyond your purchased throughput units is throttled. Event Hubs Capture copies data directly from the internal Event Hubs storage, bypassing throughput unit egress quotas and saving your egress for other processing readers, such as Stream Analytics or Spark.
+Event Hubs traffic is controlled by throughput units (TUs). Each TU provides up to 1 MB per second of ingress (or roughly 1,000 1‑KB events per second) and up to 2 MB per second of egress (or 4,096 events per second). Standard Event Hubs can be configured with 1-40 throughput units per namespace; you can enable auto-inflate to scale up to a configured maximum or request a higher quota. Usage beyond your purchased TUs is throttled. Event Hubs Capture copies data directly from internal Event Hubs storage, bypassing TU egress and preserving egress for other processing readers, such as Stream Analytics or Spark.
 
 Once configured, Event Hubs Capture runs automatically when you send your first event, and continues running. To make it easier for your downstream processing to know that the process is working, Event Hubs writes empty files when there's no data. This process provides a predictable cadence and marker that can feed your batch processors.
 

learn-pr/wwl-azure/configure-web-app-settings/includes/5-enable-diagnostic-logging.md

@@ -12,7 +12,7 @@ The following table shows the types of logging, the platforms supported, and whe
 
 ## Enable application logging (Windows)
 
-1. To enable application logging for Windows apps in the Azure portal, navigate to your app and select **App Service logs**.
+1. To enable application logging for Windows apps in the Azure portal, navigate to your app and select **Monitoring** > **App Service logs**.
 
 1. Select **On** for either **Application Logging (Filesystem)** or **Application Logging (Blob)**, or both. The **Filesystem** option is for temporary debugging purposes, and turns itself off in 12 hours. The **Blob** option is for long-term logging, and needs a blob storage container to write logs to.
 
@@ -57,25 +57,42 @@ In your application code, you use the usual logging facilities to send log messa
     System.Diagnostics.Trace.TraceError("If you're seeing this, something bad happened");
     ```
 
-    By default, ASP.NET Core uses the `Microsoft.Extensions.Logging.AzureAppServices` logging provider.
+    ASP.NET Core includes the Azure App Service logging provider. Enable it when configuring logging, for example:
 
-* Python applications can use the [OpenCensus package](/azure/azure-monitor/app/opencensus-python) to send logs to the application diagnostics log.
+    ```csharp
+    builder.Logging.AddAzureWebAppDiagnostics();
+    ```
+
+* Python applications should use [OpenTelemetry with Azure Monitor](/azure/azure-monitor/app/opentelemetry-enable) to send logs to the application diagnostics log.
+
+## Send logs to Azure Monitor
+
+You can forward platform and application logs to Azure Monitor destinations via Diagnostic Settings.
+
+* In the Azure portal, open your app and select **Monitoring** > **Diagnostic settings**, then add a diagnostic setting to send logs to a Log Analytics workspace, Storage account, or Event Hubs.
+* Common categories include **AppServiceHTTPLogs** (web server logs) and **AppServiceConsoleLogs** (stdout/stderr). For details, see [Supported resource logs for Microsoft.Web](/azure/app-service/monitor-app-service-reference#supported-resource-logs-for-microsoftweb).
 
 ## Stream logs
 
-Before you stream logs in real time, enable the log type that you want. Any information written to files ending in .txt, .log, or .htm that are stored in the `/LogFiles` directory (`d:/home/logfiles`) is streamed by App Service.
+Before you stream logs in real time, enable the log type that you want. Any information written to files ending in .txt, .log, or .htm that are stored in the `/home/LogFiles` directory (Windows: `D:\home\LogFiles`) is streamed by App Service.
 
 > [!NOTE]
 > Some types of logging buffer write to the log file, which can result in out of order events in the stream. For example, an application log entry that occurs when a user visits a page may be displayed in the stream before the corresponding HTTP log entry for the page request.
 
 * Azure portal - To stream logs in the Azure portal, navigate to your app and select **Log stream**.
 
-* Azure CLI - To stream logs live in Cloud Shell, use the following command:
+* Azure CLI - To stream logs live in Cloud Shell, use the following command (note: Cloud Shell may not work for some Linux-based plans; use the local CLI if needed):
 
     ```bash
     az webapp log tail --name appname --resource-group myResourceGroup
     ```
 
+    To filter specific log types, such as HTTP or application logs, use the `--provider` parameter, for example:
+
+    ```bash
+    az webapp log tail --name appname --resource-group myResourceGroup --provider http
+    ```
+
 * Local console - To stream logs in the local console, install Azure CLI and sign in to your account. Once signed in, follow the instructions shown for Azure CLI.
 
 ## Access log files
@@ -85,7 +102,10 @@ If you configure the Azure Storage blobs option for a log type, you need a clien
 For logs stored in the App Service file system, the easiest way is to download the ZIP file in the browser at:
 
 * Linux/container apps: `https://<app-name>.scm.azurewebsites.net/api/logs/docker/zip`
-* Windows apps: `https://<app-name>.scm.azurewebsites.net/api/dump`
+* Windows apps: `https://<app-name>.scm.azurewebsites.net/api/logs/zip`
+
+> [!NOTE]
+> The `api/dump` endpoint downloads a full diagnostic dump, not just logs. Use `api/logs/zip` to download only log files.
 
 For Linux/container apps, the ZIP file contains console output logs for both the docker host and the docker container. For a scaled-out app, the ZIP file contains one set of logs for each instance. In the App Service file system, these log files are the contents of the */home/LogFiles* directory.
 

learn-pr/wwl-azure/implement-azure-container-apps/includes/6-container-apps-revisions-secrets.md

@@ -15,7 +15,7 @@ az containerapp update \
   --image <IMAGE_NAME>
 ```
 
-You can list all revisions associated with your container app with the `az containerapp revision list` command. 
+You can list all revisions associated with your container app with the `az containerapp revision list` command.
 
 ```bash
 az containerapp revision list \
@@ -43,7 +43,7 @@ An updated or deleted secret doesn't automatically affect existing revisions in
 Before you delete a secret, deploy a new revision that no longer references the old secret. Then deactivate all revisions that reference the secret.
 
 > [!NOTE]
-> Container Apps doesn't support Azure Key Vault integration. Instead, enable managed identity in the container app and use the Key Vault SDK in your app to access secrets.
+> Container Apps supports native Azure Key Vault integration. Enable managed identity in the container app, grant the identity the **Key Vault Secrets User** role, and define secrets as Key Vault references using the secret's URI. Container Apps automatically retrieves and refreshes the secret value.
 
 ### Defining secrets