Last 20 commits touching this section.
Document Azure Disk Encryption retirement for Batch (#321141) * Document Azure Disk Encryption retirement for Batch Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 31d11ad6-b48b-4533-8562-e7002b1619b3 * Update articles/batch/security-best-practices.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Update articles/batch/batch-pool-update-properties.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Update articles/batch/disk-encryption.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Update articles/batch/disk-encryption.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Update articles/batch/disk-encryption.md Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Standardize Batch ADE retirement wording Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 31d11ad6-b48b-4533-8562-e7002b1619b3 --------- Co-authored-by: Xin Xin <xxin@microsoft.com> Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> Copilot-Session: 31d11ad6-b48b-4533-8562-e7002b1619b3
Clarify Batch node count metric aggregation Document sampling, missing and duplicate samples, and recommended aggregation choices for Batch node and core count metrics. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 772b771c-32fa-4f54-8439-271d924d0d42
Update BlobFuse documentation for FUSE reference Removed a hyperlink from the FUSE reference page in the BlobFuse documentation.
Refine VM image recommendations in documentation Removed redundant bullet point about Linux images for Batch container workloads.
Improve HPC Evaluate-stage entry guidance (#320626) * docs: improve HPC evaluate-stage guidance * Apply suggestion from @learn-build-service-prod-09[bot] Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> * Apply suggestion from @learn-build-service-prod-09[bot] Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> * docs: add HPC decision and production readiness gates * Update articles/cyclecloud/overview-ccws.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * Update articles/high-performance-computing/performance-benchmarking/platform-selection-best-practices-for-hpc-ai-models.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * Fix HPC article ownership and broken link * Update author information in overview.md * Change author in HPC benchmarking overview Updated author information from 'howard.andy' to 'padmalathas'. --------- Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com>
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main) (#320467) * Note that Newtonsoft serialization attributes stop working after migration (#128734) Follow-up to the `AllowSynchronousIO` clarification in #128726 and the *Migrate to asynchronous HTTP stream I/O* section that was added alongside it. That async guidance is correct as written: replacing `ReadToEnd` with `ReadToEndAsync` keeps the same serializer, so a migrated app keeps behaving identically. This PR covers a step of the migration that isn't behavior-preserving. ## Problem The in-process model used *Newtonsoft.Json*. The isolated worker model uses *System.Text.Json* by default. Types that a migrated app binds to usually still carry *Newtonsoft.Json* attributes (`[JsonProperty("customer_name")]` being the common one), and *System.Text.Json* doesn't recognize them. It binds the affected property to its default value and reports nothing: HTTP 200, property `null`, no exception and no log entry. The *JSON serialization* section of this guide covers the serializer switch itself and links to *Customizing JSON serialization* for options and for moving back to JSON.NET. It says nothing about the attributes already sitting on the reader's types. `JsonProperty` and `JsonPropertyName` currently appear nowhere in this guide, its includes, or `dotnet-isolated-process-guide.md`, so a reader whose property silently stops binding has nothing to search for. Measured on `Microsoft.Azure.Functions.Worker` 2.52.0, `Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore` 2.1.1, Core Tools 4.13.0, host 4.1051.300.26316: a DTO carrying `[JsonProperty("customer_name")]` binds to `null` on every input path tested while the app stays on *System.Text.Json*, with no diagnostic on any of them. ## Change One file, one added paragraph, nothing removed: note that *Newtonsoft.Json* serialization attributes carried over from the in-process model are ignored by *System.Text.Json* without an error. The paragraph gives the two ways out: replace them with their *System.Text.Json* equivalents, or configure *Newtonsoft.Json* for the layer that handles the payload. ## Notes for review The edited file is an include, `includes/functions-dotnet-migrate-isolated-other-code-changes.md`. It renders inside `articles/azure-functions/migrate-dotnet-to-isolated-model.md`, which is also the file changed by my open PR #128730. The two touch different files and don't conflict, but they land on the same rendered page, so you may want to look at them together. "Configure *Newtonsoft.Json* for the layer that handles the payload" is deliberately unspecific about which layer, because that depends on whether the app uses ASP.NET Core integration. There's a companion change for `articles/azure-functions/dotnet-isolated-process-guide.md` that makes that distinction precise; it's a different file with a different owner, so I'm submitting it separately. Either change stands on its own. * Include Fluent Bit ConfigMap for log collection (#128767) Added Fluent Bit configuration examples for log collection using Azure Files in AKS. and added support limitation. * Document listSecrets access granted by Container Apps built-in roles (#128755) * Document listSecrets access in Container Apps built-in roles Several Container Apps built-in roles define permissions with wildcard patterns that match the listSecrets action, so they grant read access to secret values in plain text even when the role name or description suggests narrower access. - manage-secrets.md: add a 'Permissions for managing secrets' section listing the built-in roles that grant listSecrets, plus a custom role example that omits it. - jobs.md: correct the Permissions section to name the Jobs Contributor and Jobs Operator roles, call out that both grant listSecrets, and fix the custom role action list (executions/read, stop/action, managedEnvironments/read). - security.md: add secrets management best practices covering role review and custom roles. Roles verified against live ARM role definitions and articles/role-based-access-control/built-in-roles/containers.md. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Correct claim that a custom role without listSecrets blocks secret access The job start API accepts a template override that replaces the container image, command, and environment variables for the execution. An identity holding only Microsoft.App/jobs/start/action can therefore run an arbitrary container with the job's secrets injected and read the values from inside it. Omitting listSecrets from a custom role does not prevent this, so the previous guidance was misleading. - jobs.md: replace the vague 'you get access to all the secrets' note with an IMPORTANT callout explaining the override mechanism, and stop presenting the custom role action list as a way to run jobs without secret access. - manage-secrets.md: change the custom role example to a monitor-only role that omits start/action, and add a WARNING covering the start/action escalation path. Verified against the job start REST contract documented in jobs.md and the --image/--command/--env-vars parameters of 'az containerapp job start'. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Clarify Container Apps job permissions and secret access Refine the role guidance after review: - explain that job start can reference retained secrets rather than implying all secrets are injected automatically - qualify managed identity access by container identity availability - link directly to the Jobs - Start REST API - replace Contributor requirements with jobs/start/action - add individual execution read and stop operations to custom roles - correct wildcard and ConnectedEnvironments role descriptions - normalize the permissions table and scope the jobs-specific warning Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Address Container Apps permissions review findings Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Clarify Container Apps secret access guidance Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Update articles/container-apps/jobs.md * Update articles/container-apps/jobs.md Co-authored-by: Craig Shoemaker <craigshoemaker@gmail.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Craig Shoemaker <craigshoemaker@gmail.com> * Add FAQ about multiple X-Azure-Ref values (#128749) * Add FAQ about multiple X-Azure-Ref values - question: Why do I see multiple X-Azure-Ref values in my backend application logs when requests pass through Azure Front Door? answer: The X-Azure-Ref value displayed in the client response and Azure Front Door access logs represents the primary request correlation identifier generated by Azure Front Door. Additional X-Azure-Ref values observed only in backend application logs are expected and are internal correlation identifiers generated during request processing within the Azure Front Door platform. These internal identifiers are used by the service for request tracking and diagnostics and don't indicate multiple client requests. * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * docs: remove duplicate 'the' in NSG diagnostics comments (#128783) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * Clarify Prometheus counter visibility (#128772) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 09f5c5be-413a-4b74-b070-c848484e0d73 * docs: fix 'enviroment' typo in Data Factory access strategies (#128774) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'for' in Azure NetApp Files clone FAQ (#128775) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'to' in private link relocation guide (#128776) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in Logic Apps Reassert docs (#128777) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in storage task runs alt-text (#128781) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in WebJobs deploy alt-text (#128780) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'to' in Container Apps volume mount error (#128778) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'to' in Functions identity-based connections (#128779) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in SignalR Front Door alt-text (#128784) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in Site Recovery reprotect guide (#128785) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in Batch upgrade policy note (#128782) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in Planetary Computer ingestion overview (#128786) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> * docs: remove duplicate 'the' in IoT Edge downstream device guide (#128787) Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> --------- Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com> Co-authored-by: Fabian <info@fzankl.de> Co-authored-by: jacobbaek <dubaek@gmail.com> Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com> Co-authored-by: Tiago Alves Macambira <tmacam@burocrata.org> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Craig Shoemaker <craigshoemaker@gmail.com> Co-authored-by: Jagan Peddabavi <157447885+Jpeddabavi@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: mrchatam <chatam@proton.me> Co-authored-by: mrchatam <mrchatam@users.noreply.github.com> Co-authored-by: Kelly Shields <kellyshields@microsoft.com> Copilot-Session: 09f5c5be-413a-4b74-b070-c848484e0d73
Fix Azure Batch landing page and review follow-ups (#320147) * Fix Batch landing page and review follow-ups Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: f1d8f64f-fb6c-4367-a09d-52c035567fd0 * docs: add financial risk simulation guidance * docs: split financial simulation guidance into a series --------- Co-authored-by: Xin Xin <xxin@microsoft.com> Co-authored-by: Padmalathas <107439713+Padmalathas@users.noreply.github.com> Copilot-Session: f1d8f64f-fb6c-4367-a09d-52c035567fd0
Document Azure Monitor for Batch pool nodes (#320084) * Document Azure Monitor for Batch pool nodes Add an end-to-end AMA and DCR guide, update monitoring navigation, and remove retired Batch Insights and OMS agent guidance. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5fe900a5-3d2b-4382-add1-988a2a4f2535 * Update dates for Batch monitoring docs Set ms.date to the current date for every documentation article changed by the Batch pool monitoring update. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5fe900a5-3d2b-4382-add1-988a2a4f2535 * Update articles/batch/monitor-batch-pool-nodes.md Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> * Update articles/batch/monitor-batch-pool-nodes.md Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> * Apply suggestion from @learn-build-service-prod-07[bot] Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> --------- Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> Co-authored-by: Padmalatha Somashiandan <107439713+Padmalathas@users.noreply.github.com> Copilot-Session: 5fe900a5-3d2b-4382-add1-988a2a4f2535
Merge pull request #319078 from Hectoruu/US-601710-broken-links-dat-54 2026_08 - Fix monthly broken links
Merge pull request #319094 from patrickconcannon/pconcannon/batch-image-verification-status Clarify that Batch image verification status can change over time
Address documentation review feedback - Split image verification guidance into shorter paragraphs - Use the preferred contraction in the best-practices guidance Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 153552d3-5f99-4c92-b2e7-a056e5c58775
Apply Learn style suggestions and update ms.date Address Learn Authoring Assistant feedback: use 'might' instead of 'may' for possibility per the Microsoft Writing Style Guide (3 occurrences), and tighten 'has stopped working' to 'stopped working'. Also bump ms.date on both articles to reflect the content update. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add how-to for disabling hyper-threading on Azure Batch pool nodes (#318966) * Add how-to for disabling hyper-threading on Batch pool nodes Document how customers disable hyper-threading (SMT) on Azure Batch pool nodes by setting the pool tag platformsettings.host_environment.disablehyperthreading=true. The Batch service no longer requires the Microsoft.Compute/PlatformSettingsOverride subscription feature; applying the pool tag is now sufficient. Adds a new how-to article (create-pool-disable-hyperthreading.md) with VM size support guidance, impact on vCPU count/quota, Bicep/ARM/REST examples, and Linux/Windows verification steps, and links it from the batch TOC. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3634da46-a388-40bd-8b89-04ce48c56f7d * Update articles/batch/create-pool-disable-hyperthreading.md Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> * Update articles/batch/create-pool-disable-hyperthreading.md Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> * Rename create-pool-disable-hyperthreading.md to how-to-disable-hyper-threading-using-pool-tag.md * Update hyperlink for disabling hyper-threading --------- Co-authored-by: Xin Xin <xxin@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Padmalatha Somashiandan <107439713+Padmalathas@users.noreply.github.com> Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> Copilot-Session: 3634da46-a388-40bd-8b89-04ce48c56f7d
Merge pull request #318918 from xinlaoda/update-batch-ffmpeg-sample-location Update ffmpeg tutorial: new sample location + local input-file generation