[{"author":"jlian","date":"2026-09-24T16:41:13+00:00","message":"docs(iot-edge): add large-fleet identity operation checklist","sha":"8dbc1403181ac6a89a40e25d734a584df8dd7c5f","url":"https://github.com/MicrosoftDocs/azure-docs/commit/8dbc1403181ac6a89a40e25d734a584df8dd7c5f"},{"author":"jlian","date":"2026-09-16T19:50:32+00:00","message":"docs: document client-secret authentication for metrics collector","sha":"dd1f661207a1deac57ebedacf609c7dbaf1346eb","url":"https://github.com/MicrosoftDocs/azure-docs/commit/dd1f661207a1deac57ebedacf609c7dbaf1346eb"},{"author":"jlian","date":"2026-09-15T23:36:14+00:00","message":"Update IoT Edge monitoring for Metrics Collector 2.0 (#320482)\n\n* Draft IoT Edge metrics Logs Ingestion migration guidance\n\n* Normalize draft list formatting and final newline\n\n* Use bundled HTTP diagnostic client in migration example\n\n* Clarify alert target and device dimension migration contract\n\n* Write customer guidance for Metrics Collector 2.0\n\n* Scope resource association guidance to the documented configuration\n\n* Minimize Metrics Collector documentation diff\n\n* Address Metrics Collector documentation review\n\n* Clarify metrics collector upgrade link\n\n* Apply remaining authoring suggestions\n\n* Address metrics collector review feedback\n\n* Retry documentation validation\n\n* Clarify routed metrics sample migration\n\n* Remove legacy monitoring sample references\n\n* Add tutorial client secret setup\n\n* Clarify managed and workload identity options\n\n* Document stateful log alert resolution timing\n\n* Focus metrics guidance on customer configuration\n\n* Align workbook source defaults\n\n* Align workbook guidance with current controls\n\n* Use direct workbook monitoring guidance\n\n* Clarify workload identity validation boundary\n\n* Address workload guidance style checks\n\n* Clarify collector federation and token-file permissions\n\n* Keep workload federation guidance concise\n\n* Apply workload federation style guidance\n\n* Document configurable metrics table in IoT Edge workbooks\n\n* Clarify workbook table selection in observability guide\n\n* Document invalid metrics table fallback\n\n* Fix Alerts UI formatting\n\n* Fix numbered-list table indentation","sha":"42f9355db82c06f623dd4f103830527774b747dc","url":"https://github.com/MicrosoftDocs/azure-docs/commit/42f9355db82c06f623dd4f103830527774b747dc"},{"author":"learn-build-service-prod","date":"2026-09-14T16:52:15+00:00","message":"Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main) (#320467)\n\n* Note that Newtonsoft serialization attributes stop working after migration (#128734)\n\nFollow-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.\n\n## Problem\n\nThe 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.\n\nThe *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.\n\nMeasured 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.\n\n## Change\n\nOne 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.\n\n## Notes for review\n\nThe 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.\n\n\"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.\n\n* Include Fluent Bit ConfigMap for log collection (#128767)\n\nAdded Fluent Bit configuration examples for log collection using Azure Files in AKS. and added support limitation.\n\n* Document listSecrets access granted by Container Apps built-in roles (#128755)\n\n* Document listSecrets access in Container Apps built-in roles\n\nSeveral Container Apps built-in roles define permissions with wildcard\npatterns that match the listSecrets action, so they grant read access to\nsecret values in plain text even when the role name or description\nsuggests narrower access.\n\n- manage-secrets.md: add a 'Permissions for managing secrets' section\n listing the built-in roles that grant listSecrets, plus a custom role\n example that omits it.\n- jobs.md: correct the Permissions section to name the Jobs Contributor\n and Jobs Operator roles, call out that both grant listSecrets, and fix\n the custom role action list (executions/read, stop/action,\n managedEnvironments/read).\n- security.md: add secrets management best practices covering role\n review and custom roles.\n\nRoles verified against live ARM role definitions and\narticles/role-based-access-control/built-in-roles/containers.md.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Correct claim that a custom role without listSecrets blocks secret access\n\nThe job start API accepts a template override that replaces the container\nimage, command, and environment variables for the execution. An identity\nholding only Microsoft.App/jobs/start/action can therefore run an\narbitrary container with the job's secrets injected and read the values\nfrom inside it. Omitting listSecrets from a custom role does not prevent\nthis, so the previous guidance was misleading.\n\n- jobs.md: replace the vague 'you get access to all the secrets' note\n with an IMPORTANT callout explaining the override mechanism, and stop\n presenting the custom role action list as a way to run jobs without\n secret access.\n- manage-secrets.md: change the custom role example to a monitor-only\n role that omits start/action, and add a WARNING covering the\n start/action escalation path.\n\nVerified against the job start REST contract documented in jobs.md and\nthe --image/--command/--env-vars parameters of 'az containerapp job start'.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Clarify Container Apps job permissions and secret access\n\nRefine the role guidance after review:\n- explain that job start can reference retained secrets rather than\n implying all secrets are injected automatically\n- qualify managed identity access by container identity availability\n- link directly to the Jobs - Start REST API\n- replace Contributor requirements with jobs/start/action\n- add individual execution read and stop operations to custom roles\n- correct wildcard and ConnectedEnvironments role descriptions\n- normalize the permissions table and scope the jobs-specific warning\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Address Container Apps permissions review findings\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Clarify Container Apps secret access guidance\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Update articles/container-apps/jobs.md\n\n* Update articles/container-apps/jobs.md\n\nCo-authored-by: Craig Shoemaker \n\n---------\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\nCo-authored-by: Craig Shoemaker \n\n* Add FAQ about multiple X-Azure-Ref values (#128749)\n\n* Add FAQ about multiple X-Azure-Ref values\n\n - question: Why do I see multiple X-Azure-Ref values in my backend application logs when requests pass through Azure Front Door?\n 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.\n\n* Potential fix for pull request finding\n\nCo-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>\n\n---------\n\nCo-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>\n\n* docs: remove duplicate 'the' in NSG diagnostics comments (#128783)\n\nCo-authored-by: mrchatam \n\n* Clarify Prometheus counter visibility (#128772)\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>\n\nCopilot-Session: 09f5c5be-413a-4b74-b070-c848484e0d73\n\n* docs: fix 'enviroment' typo in Data Factory access strategies (#128774)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'for' in Azure NetApp Files clone FAQ (#128775)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'to' in private link relocation guide (#128776)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in Logic Apps Reassert docs (#128777)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in storage task runs alt-text (#128781)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in WebJobs deploy alt-text (#128780)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'to' in Container Apps volume mount error (#128778)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'to' in Functions identity-based connections (#128779)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in SignalR Front Door alt-text (#128784)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in Site Recovery reprotect guide (#128785)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in Batch upgrade policy note (#128782)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in Planetary Computer ingestion overview (#128786)\n\nCo-authored-by: mrchatam \n\n* docs: remove duplicate 'the' in IoT Edge downstream device guide (#128787)\n\nCo-authored-by: mrchatam \n\n---------\n\nCo-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>\nCo-authored-by: Fabian \nCo-authored-by: jacobbaek \nCo-authored-by: Learn Build Service GitHub App \nCo-authored-by: Tiago Alves Macambira \nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\nCo-authored-by: Craig Shoemaker \nCo-authored-by: Jagan Peddabavi <157447885+Jpeddabavi@users.noreply.github.com>\nCo-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>\nCo-authored-by: mrchatam \nCo-authored-by: mrchatam \nCo-authored-by: Kelly Shields \nCopilot-Session: 09f5c5be-413a-4b74-b070-c848484e0d73","sha":"e51d1a135b2f3c560082e5a227af03d5edb54f3c","url":"https://github.com/MicrosoftDocs/azure-docs/commit/e51d1a135b2f3c560082e5a227af03d5edb54f3c"},{"author":"gordonwang0","date":"2026-09-11T20:42:23+00:00","message":"Update articles/iot-edge/configure-device.md\n\nCo-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com>","sha":"8e39d2a9ec11f1589dbe40f9c894b1961e06c0f1","url":"https://github.com/MicrosoftDocs/azure-docs/commit/8e39d2a9ec11f1589dbe40f9c894b1961e06c0f1"},{"author":"gordonwang0","date":"2026-09-11T20:41:28+00:00","message":"Update articles/iot-edge/configure-device.md\n\nCo-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com>","sha":"630be83d0ed3df3550992d47999b23404945b223","url":"https://github.com/MicrosoftDocs/azure-docs/commit/630be83d0ed3df3550992d47999b23404945b223"},{"author":"gordonwang0","date":"2026-09-11T20:41:05+00:00","message":"Update articles/iot-edge/configure-device.md\n\nCo-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com>","sha":"c7e3bebeb801d7393ad4fa6bc404d5331bd183c9","url":"https://github.com/MicrosoftDocs/azure-docs/commit/c7e3bebeb801d7393ad4fa6bc404d5331bd183c9"},{"author":"gordonwang0","date":"2026-09-11T20:00:13+00:00","message":"Update documentation on elevated Docker permissions\n\nClarified the purpose of the allow_elevated_docker_permissions setting and its impact on Docker capabilities for IoT Edge modules.","sha":"84e0aa29c5db9438438450df0b4ac503bd806820","url":"https://github.com/MicrosoftDocs/azure-docs/commit/84e0aa29c5db9438438450df0b4ac503bd806820"},{"author":"vadim-kovalyov","date":"2026-09-04T00:06:46+00:00","message":"docs(iot-edge): address review feedback\n\nKeep bind source policy in operator-facing documentation and apply Learn active-voice guidance.\\n\\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>","sha":"b9110bb448b3caaf57eabda532737998b82150f2","url":"https://github.com/MicrosoftDocs/azure-docs/commit/b9110bb448b3caaf57eabda532737998b82150f2"},{"author":"vadim-kovalyov","date":"2026-09-03T23:48:52+00:00","message":"docs(iot-edge): document bind source limits\n\nDocument the device allowlist introduced in IoT Edge 1.6.3 and explain how it affects module and persistent-storage bind mounts.\\n\\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>","sha":"b30e88be53404798416900bacd583429f7aee469","url":"https://github.com/MicrosoftDocs/azure-docs/commit/b30e88be53404798416900bacd583429f7aee469"},{"author":"sethmanheim","date":"2026-07-31T19:49:11+00:00","message":"Move IoT certificate management content under IoT Hub (#317138)\n\n* Move IoT certificate management content under IoT Hub\n\n* Resolve errors\n\n* More fixes\n\n* Fixes\n\n* Fixes\n\n* Add redirects\n\n* Update articles/iot/iot-hub-certificate-management-concepts.md\n\nCo-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>\n\n* Update articles/iot-hub/iot-mqtt-connect-to-iot-hub.md\n\nCo-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>\n\n* Update articles/iot/tutorial-x509-test-certs.md\n\nCo-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>\n\n* Update articles/iot/tutorial-x509-test-certs.md\n\nCo-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>\n\n* Apply suggestions from code review\n\nCo-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>\n\n* Fix TOC\n\n* Fix TOC again\n\n* Suggestions from CDA\n\n* Fix\n\n* Apply suggestions from code review\n\nCo-authored-by: learn-build-service-prod-06[bot] <274430002+learn-build-service-prod-06[bot]@users.noreply.github.com>\n\n* Align TOC with main\n\n* Revert last\n\n* Revert last\n\n* Try again to sync with main TOC\n\n* Add back\n\n* Update articles/iot/TOC.yml\n\nCo-authored-by: Dominic Betts <1454644+dominicbetts@users.noreply.github.com>\n\n* Incorp Dom comments\n\n* Fixes\n\n* Warnings\n\n* Add note\n\n* Update\n\n* Accept weird random change\n\n---------\n\nCo-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com>\nCo-authored-by: learn-build-service-prod-06[bot] <274430002+learn-build-service-prod-06[bot]@users.noreply.github.com>\nCo-authored-by: Dominic Betts <1454644+dominicbetts@users.noreply.github.com>","sha":"37a800a6a92a03eda29ee3328e83e3ffdf4b4130","url":"https://github.com/MicrosoftDocs/azure-docs/commit/37a800a6a92a03eda29ee3328e83e3ffdf4b4130"},{"author":"prmerger-automator","date":"2026-07-21T19:05:15+00:00","message":"Merge pull request #318361 from Hectoruu/US-592880-broken-links-dat-155\n\n2026_07 - Fix monthly broken links","sha":"a841113b6dd126752232cf1f4d3a170fb8f6dd0c","url":"https://github.com/MicrosoftDocs/azure-docs/commit/a841113b6dd126752232cf1f4d3a170fb8f6dd0c"},{"author":"prmerger-automator","date":"2026-07-17T20:30:34+00:00","message":"Merge pull request #318303 from jlian/patch-400210\n\nUpdate release date for IoT Edge 1.6 LTS","sha":"712be1a2bed5b6992af6293197c2342ed94cbf23","url":"https://github.com/MicrosoftDocs/azure-docs/commit/712be1a2bed5b6992af6293197c2342ed94cbf23"},{"author":"jlian","date":"2026-07-17T20:08:46+00:00","message":"Resolve 1.6 LTS release date and drop DO NOT MERGE gate\n\n1.6.0 LTS GA'd 2026-07-16. Remove the pre-GA hold comment and bump ms.date.\nRelease date (July 2026) matches support.md. Verified the tag/1.6.0 release\nlinks resolve.","sha":"18fe35a9828b1a75ea7039d5003609e3521c2db5","url":"https://github.com/MicrosoftDocs/azure-docs/commit/18fe35a9828b1a75ea7039d5003609e3521c2db5"},{"author":"Hectoruu","date":"2026-07-17T18:40:50+00:00","message":"Update GlobalSign demo account link","sha":"f512b0fab714d7cf331aa2cb38e82a6a9546706c","url":"https://github.com/MicrosoftDocs/azure-docs/commit/f512b0fab714d7cf331aa2cb38e82a6a9546706c"},{"author":"jlian","date":"2026-07-16T23:42:03+00:00","message":"Resolve IoT Edge 1.6 LTS GA placeholders in support.md\n\nIoT Edge 1.6.0 GA'd 2026-07-16. Fill the GA-gated placeholders that\nmirror the version-history.md fix (#318303):\n- Release date: July 2026 (matches version-history.md)\n- Tested Microsoft.Azure.Devices.Client SDK: 1.43.x (from the 1.6.0\n source, pinned to 1.43.2-edgeLts)\n- Remove the DO NOT MERGE gating comment now that placeholders resolve","sha":"813527bea30abf3780207556a1847c6e2372fca1","url":"https://github.com/MicrosoftDocs/azure-docs/commit/813527bea30abf3780207556a1847c6e2372fca1"},{"author":"jlian","date":"2026-07-16T22:33:57+00:00","message":"Update release date for IoT Edge 1.6 LTS","sha":"5367d209ebbcc35e7645d6e1d689907eabe2af94","url":"https://github.com/MicrosoftDocs/azure-docs/commit/5367d209ebbcc35e7645d6e1d689907eabe2af94"},{"author":"jlian","date":"2026-07-16T19:19:50+00:00","message":"iot-edge: prep docs for IoT Edge 1.6 LTS (#316938)\n\n* iot-edge: update .NET LTS references for IoT Edge 1.6 LTS\n\nIoT Edge 1.6 LTS aligns with .NET 10 (per version-history.md and\nAzure/iotedge main). Update the two remaining 1.5/.NET 8-era code\nsamples so docs reflect the upcoming runtime:\n\n- how-to-access-dtpm.md: VS target framework guidance -> .NET 10.0\n- tutorial-develop-for-linux.md: filtermodule.csproj sample ->\n net10.0 and Microsoft.Extensions.Hosting 10.0.0\n\nRefresh ms.date on touched files.\n\n* iot-edge: remove Debian 11 (Bullseye) from supported platforms for 1.6 LTS\n\nIoT Edge 1.6 LTS drops Debian 11 support (Azure/iotedge#7511).\nRemove Debian 11 / Bullseye references from the public docs:\n\n- support.md: drop Debian 11 from both Tier 1 (ARM32v7) and Tier 2\n (AMD64/ARM64) tables; generalize the cross-tier note now that\n Debian 11 was the only example.\n- includes/iot-edge-install-linux.md: drop the Debian 11 install\n block; update the Raspberry Pi OS Stretch retirement tip to point\n at Bookworm (Debian 12) instead of Bullseye.\n- module-development.md: ARM32 container support note now references\n Debian 12 instead of Debian 11.\n- Refresh ms.date on touched files.\n\n* iot-edge: roll 'latest supported release' references from 1.5 LTS to 1.6 LTS\n\nIoT Edge 1.6 LTS is the new supported release. Update docs that\nrepresent the *current/latest* runtime:\n\nVersion badges and supported-release callouts:\n- includes/iot-edge-version-all-supported.md: applies-to + IMPORTANT\n note now lead with 1.6 LTS; 1.5 LTS noted as supported until\n November 10, 2026.\n- how-to-update-iot-edge.md: applies-to badges include 1.6 + 1.5;\n IMPORTANT note updated; example version numbers updated\n (patch 1.6.1->1.6.2, major/minor 1.5->1.6, tag examples 1.6 /\n 1.6.1, rolling/specific tag prose, iotedge version sample 1.6.0).\n- version-history.md: 'Documented versions' updated so 1.6 (LTS) is\n current and 1.5 (LTS) is the previous supported version.\n Historical version-history table rows and 'LTS release cadence'\n bullets intentionally untouched.\n\nSystem runtime image tags (rolling :1.5 -> :1.6, pinned 1.5.0/1.5.1\n-> 1.6.0/1.6.1) across all how-to / tutorial / module composition /\nproduction / deploy / proxy / nested IoT Edge / downstream IoT Edge\n/ stream analytics / custom vision / troubleshoot files:\n\n- configure-device.md, debug-module-vs-code.md,\n how-to-access-host-storage-from-module.md,\n how-to-configure-proxy-support.md,\n how-to-connect-downstream-iot-edge-device.md,\n how-to-deploy-at-scale.md, how-to-deploy-cli-at-scale.md,\n how-to-deploy-modules-cli.md, how-to-visual-studio-develop-module.md,\n module-composition.md, production-checklist.md,\n troubleshoot.md, troubleshoot-common-errors.md,\n tutorial-deploy-custom-vision.md, tutorial-deploy-stream-analytics.md,\n tutorial-develop-for-linux.md, tutorial-develop-for-linux-on-windows.md,\n tutorial-nested-iot-edge.md,\n tutorial-nested-iot-edge-for-linux-on-windows.md\n\nProse 'latest stable runtime version' / 'set image value to version\n1.5' / 'change the image version to the latest version 1.5' /\n'IoT Edge version 1.5 is preinstalled' / DEFAULT_RT_IMAGE=1.5\nmentions also updated to 1.6.\n\nIntentionally NOT touched:\n- support.md release table and SDK matrix (need verified 1.6 GA date\n and SDK version pin from product before adding rows)\n- iot-edge-for-linux-on-windows-support.md and\n iot-edge-for-linux-on-windows-updates.md (no EFLOW 1.6 GA yet)\n- version-history.md historical rows and Microsoft.Extensions.Hosting /\n package version pins that need product confirmation.\n\nRefresh ms.date on all touched files.\n\n* fix: address self-review findings (iteration 1)\n\n* fix: address self-review findings (iteration 2)\n\n* style: align SDK version table columns in support.md\n\n* Apply suggestions from code review\n\nCo-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com>\n\n* Apply suggestions from code review\n\nCo-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com>\n\n* iot-edge: bump ms.date to 07/16/2026 for 1.6 LTS GA\n\n---------\n\nCo-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com>\nCo-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com>","sha":"b3e13ab8afb4924fe99d2078d50082386b1f2d47","url":"https://github.com/MicrosoftDocs/azure-docs/commit/b3e13ab8afb4924fe99d2078d50082386b1f2d47"},{"author":"jlian","date":"2026-06-16T22:10:44+00:00","message":"Document IoT Edge identity-operation quota cause: device scope cache refresh\n\nAdd a troubleshooting entry for IoT Hub identity-operation quota exhaustion\non large fleets, caused by the per-edgeHub hourly device scope cache refresh\n(GetDevicesAndModulesInScope), with the DeviceScopeCacheRefreshRateSecs\nmitigation and downstream-device caveat. Document DeviceScopeCacheRefreshRateSecs\nand DeviceScopeCacheRefreshDelaySecs as edgeHub environment variables. Fix a\nminor typo in the adjacent identity-calls section.","sha":"59e50bfaeb89b754897b0de2b9844dee0818ac1f","url":"https://github.com/MicrosoftDocs/azure-docs/commit/59e50bfaeb89b754897b0de2b9844dee0818ac1f"},{"author":"jlian","date":"2026-05-13T18:29:14+00:00","message":"Clarify connected-client reporting in nested topologies\n\n- iot-edge-limits-and-restrictions.md: reword the \"plus one connection for itself\" passage to spell out that the extra connection is the child edgeHub's own connection (/$edgeHub) and that connections are per module + downstream client + child edgeHub, not per arbitrary identity. Tightens the 202-connections example for the same reason.\n\n- module-edgeagent-edgehub.md: add a new 'Which connections appear in clients' section that documents what edgeHub's clients reported property contains and excludes (modules including $edgeAgent, downstream IoT Edge children as /$edgeHub and /$edgeAgent, leaf devices as , local $edgeHub omitted), plus the disconnect behavior. Cross-links to the limits page.","sha":"b3e4dac1189ebb9d24b75f4cfadc9fb0cae0b52b","url":"https://github.com/MicrosoftDocs/azure-docs/commit/b3e4dac1189ebb9d24b75f4cfadc9fb0cae0b52b"}]