[{"author":"nikhilkaul1234","date":"2026-09-29T09:08:31+00:00","message":"Apply Authoring Assistant suggestion","sha":"923e10c76dc52877893d33ea9dde6d607497656c","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/923e10c76dc52877893d33ea9dde6d607497656c"},{"author":"nikhilkaul1234","date":"2026-09-29T09:02:53+00:00","message":"Chaos Studio Workspaces: add Key Vault, VM Hibernate, VM Maintenance Reboot templates and custom Scenario Actions\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>","sha":"eb85da6a52fb6ad295c66fd642060d9492955d9f","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/eb85da6a52fb6ad295c66fd642060d9492955d9f"},{"author":"nikhilkaul1234","date":"2026-09-27T09:53:34+00:00","message":"Frame Chaos Studio Experiments (classic) as replaced by Workspaces and add migration guide (#5498)\n\n* Frame Chaos Studio Experiments (classic) as replaced by Workspaces and add migration guide\n\n- Reword the classic servicing include to 'being replaced by Workspaces' and\n  link a new migration guide; move it directly under the H1 in all 49 classic articles.\n- Add chaos-studio-migrate-from-classic.md: identify model, concept map,\n  experiment-to-Scenario map, capabilities not yet in Workspaces, steps, cleanup.\n- Add the guide to TOC (Workspaces and classic sections) and landing page;\n  replace the 'Use Experiments (classic) when GA is required' landing link.\n- Recast the comparison, overview, and Workspaces overview articles as a transition.\n- Add 'which model am I using' sections to both troubleshooting articles.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Readability pass on Classic-to-Workspaces migration content\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Use 'after' for time sequence\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Address PR validation: TOC section size, table header\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Fix broken stress-ng reference links\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Fix Resource Graph query: experiments are in the resources table\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Address adversarial review findings\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Keep classic banner direct; tighten migration guide wording\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n---------\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>","sha":"56449d6fb9c1984374f73e1401915e6b22bb8f65","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/56449d6fb9c1984374f73e1401915e6b22bb8f65"},{"author":"bandersmsft","date":"2026-09-21T22:26:09+00:00","message":"BULK: Retire Azure Monitor Platform subservice (#5424)\n\n* Retire Azure Monitor Platform subservice\n\n* Fix migrated article links","sha":"a2e2f0dd741847fe6a9d9af7b42e03f6f9914eff","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/a2e2f0dd741847fe6a9d9af7b42e03f6f9914eff"},{"author":"nikhilkaul1234","date":"2026-09-06T08:42:37+00:00","message":"Improve Chaos Studio Workspaces technical SEO (#5324)\n\nApply the approved incremental documentation and navigation updates on authoritative MicrosoftDocs main, excluding previously merged Workspaces changes.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>","sha":"cd1cc85cbfa0c5b1db9cc70b55df6de116dba21c","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/cd1cc85cbfa0c5b1db9cc70b55df6de116dba21c"},{"author":"nikhilkaul1234","date":"2026-08-31T22:34:53+00:00","message":"Clarify Chaos Studio Workspaces documentation (#5285)\n\n* Clarify Chaos Studio Workspaces documentation\n\nMake Workspaces the current-model entry point, distinguish Experiments (classic), repair AKS and reference routing, and keep migration guidance limited to verified model-selection facts.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Correct Chaos Studio model guidance\n\nLabel Workspaces preview status on the landing page, retain general availability as a classic selection criterion, and align agent and identity descriptions with current model behavior.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Align classic navigation terminology\n\nUse Experiments (classic) consistently in navigation and keep the shared legacy notice accurate for both experiment and agent workflow articles.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\nCopilot-Session: 1fce7819-da5e-49b7-ab61-f178e80f0bf6\n\n* Address Learn authoring feedback\n\nApply grounded grammar and clarity improvements, preserve product-term capitalization, and remove an unsupported full-support claim for Experiments (classic).\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\nCopilot-Session: 1fce7819-da5e-49b7-ab61-f178e80f0bf6\n\n---------\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\nCopilot-Session: 1fce7819-da5e-49b7-ab61-f178e80f0bf6","sha":"e794ea56aaee7f1f847643e32d0296a605774d00","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/e794ea56aaee7f1f847643e32d0296a605774d00"},{"author":"nikhilkaul1234","date":"2026-08-25T23:01:09+00:00","message":"Rewrite AKS zone-down sample-app tutorial for async signals and hard placement (#5240)\n\n* Rewrite AKS zone-down sample-app tutorial for async signals and hard placement\n\n- Replace the fixed \"~5 minute\" Kubernetes reschedule claim with observable,\n  monitor-driven guidance; downtime duration is no longer asserted as a fact.\n- Add explicit Cloud Shell bootstrap (az account set, az aks get-credentials,\n  kubelogin convert-kubeconfig) before the first kubectl call.\n- Pin the front end to a single zone as an explicit, labeled demo\n  anti-pattern instead of relying on the scheduler's default placement,\n  so run 1's failure is deterministic instead of easy to miss.\n- Add a browser-based monitor (monitor.py) as the primary demo surface,\n  showing storefront HTTP status, target-node readiness, pod placement,\n  and a transition history; Metrics and kubectl become supporting signals.\n- Call out that the storefront HTTP signal and node NotReady status update\n  asynchronously, and that the HTTP signal is primary.\n- Set the Compute Zone Down scenario duration to 5 minutes for this demo,\n  with a note that other scenario types need their own duration guidance.\n- Replace the ScheduleAnyway topology spread constraint (previously\n  described as guaranteeing per-zone placement, which it doesn't) with a\n  DoNotSchedule hard constraint, plus an explicit verify-fix.sh check that\n  every zone has a Ready store-front replica before run 2.\n- Add a troubleshooting section for when run 1's impact isn't visible.\n- Reframe run 2's outcome as sustained availability through the outage,\n  not zero dropped requests, noting brief load-balancer convergence is\n  still possible.\n\nMirrors the final contract from the companion microsoft/chaos-studio\nsamples/aks-zone-down-demo update.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Strengthen monitor error visibility and run-2 wording\n\n- Monitor: call out that a failed kubectl/API poll surfaces as an explicit\n  error state per signal, instead of hanging on a \"checking\" placeholder.\n- Verification: clarify that verify-fix.sh retries transient kubectl/API/\n  JSON failures until its own timeout before failing, rather than exiting\n  on the first transient error.\n- Run 2: reframe explicitly as sustained availability with a possible brief\n  Azure Load Balancer convergence blip, not an unbroken \"stays green\n  throughout\" state.\n\nInterim update while the companion microsoft/chaos-studio sample branch\nfinishes its correction pass; not final until the revised contract lands.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Reconcile zone-pin, monitor, and verify steps with the immutable f9573c9 sample\n\n- Derive PIN_ZONE dynamically from the pod's actual node/zone label\n  (kubectl get pods -> node -> zone label), instead of asking the\n  reader to pick a bare zone number.\n- Move the deliberate-anti-pattern annotation to the Deployment's\n  top-level metadata.annotations (matches deploy.sh); use the exact\n  annotation key chaos-demo.aks-zone-down-demo/deliberate-anti-pattern.\n- Add the rollout restart/status wait and a self-check that the pod\n  landed back in $PIN_ZONE, mirroring deploy.sh's own safety check.\n- Pin the monitor.py / verify-fix.sh download URLs to the immutable\n  commit f9573c943694e88cf3aacbca38debe84fa91a62c instead of a 404ing\n  main branch link; note the move to a tagged ref once merged.\n- Pass $PIN_ZONE verbatim (full zone label) to monitor.py --target-zone\n  instead of a hardcoded eastus2- prefix.\n- Tighten the monitor error-state wording to match the real red banner\n  behavior, and the verify-fix.sh wording to match its rollout-wait +\n  per-zone Ready check.\n- Point the scenario zone-number entry and troubleshooting steps at\n  $PIN_ZONE instead of an ad hoc 'the zone you pinned' reference.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Remove unsupported fixed recovery-time claim in run 2 wording\n\nReplace 'recovery within a few seconds' with environment-dependent\nwording: a brief Azure Load Balancer convergence blip is possible with\nno fixed time bound, and the monitor's transition history is what\ndistinguishes a transient blip from a sustained outage.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n* Apply Learn Authoring Assistant style suggestions\n\nAccepts 10 of 11 flagged suggestions: splits four semicolon-joined\nindependent clauses into separate sentences, replaces 'may' with\n'might' per style guide, removes a dangling 'below' reference, adds\na noun after the demonstrative 'these', and replaces a dash-joined\nclause with a full sentence introducing a cross-reference.\n\nRejects the suggestion to drop the trailing colon on 'Remove the zone\npin you added earlier:' (line 256) because it would break the\nestablished colon-before-code-block pattern used by every other\nnumbered step in this article that introduces a fenced code block\n(for example, the 'Create a resource group and the cluster:' and\n'Deploy the application:' steps).\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\n\n---------\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>","sha":"988cd73e8d68eaba2b8b49a7e8399c249f45658b","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/988cd73e8d68eaba2b8b49a7e8399c249f45658b"},{"author":"nikhilkaul1234","date":"2026-08-19T16:54:05+00:00","message":"Remove unsupported VM Hibernate scenario\n\nRemove VM Hibernate from the Chaos Studio Workspaces scenario catalog because the action is unavailable in both the portal and API.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>","sha":"33c04135c35a8392bd94ef23998c626b59e062a5","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/33c04135c35a8392bd94ef23998c626b59e062a5"},{"author":"nikhilkaul1234","date":"2026-08-18T02:54:29+00:00","message":"Merge upstream main into Terraform docs update\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>","sha":"2fb881596925e11c68efa4a98b9827c86527c4cc","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/2fb881596925e11c68efa4a98b9827c86527c4cc"},{"author":"nikhilkaul1234","date":"2026-08-18T02:28:52+00:00","message":"Clarify Terraform support for Chaos workspaces\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>","sha":"048ea74bfd840535b2b984fcaae972c5673195db","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/048ea74bfd840535b2b984fcaae972c5673195db"},{"author":"nikhilkaul1234","date":"2026-08-06T22:17:26+00:00","message":"Separate Chaos Studio Classic docs and document the AKS Chaos Mesh admin-credential limitation (#5123)\n\n* Separate Chaos Studio Classic docs and document the AKS Chaos Mesh admin-credential limitation\n\n* Address PR review: bullets for non-sequential list, include metadata, remove dead link","sha":"1feb8a60e7415a68206bf7009dbfd959acc6bc6d","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/1feb8a60e7415a68206bf7009dbfd959acc6bc6d"},{"author":"spoortiSideProjs","date":"2026-08-02T08:32:28+00:00","message":"Add agent network connectivity troubleshooting to workspaces and scenarios article (#4967)\n\n* Add agent network connectivity troubleshooting section\n\nDocuments the network configurations that block the Chaos agent from reaching Chaos Studio (private subnet/outbound access, NSG, firewall/UDR, proxy, DNS, IMDS) with fixes and diagnostics, plus a pointer from the Scenario-run-fails section. Rebased onto current main.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>\n\n* Link agent-based Scenario requirements to the connectivity troubleshooting section\n\n* Clarify recognition step with verified error string and Scenario run failure banner\n\n* Lowercase 'scenarios' per Learn style guide (capitalize_proper_nouns)\n\n* Add Portal/Azure CLI tabs to the subnet outbound-access and NSG fixes\n\n* Fix list-effective-nsg JMESPath fields and match link-text casing per review\n\n---------\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>","sha":"f1c3f1f6e1196f9482ed5ba6b94a24c17cfcab08","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/f1c3f1f6e1196f9482ed5ba6b94a24c17cfcab08"},{"author":"prmerger-automator","date":"2026-07-30T20:51:31+00:00","message":"Merge pull request #5080 from nikhilkaul1234/permission-flow-reconciliation\n\nReconcile Workspace permission-flow docs with the shipped experience","sha":"b4e847b9997b6c36e4a55c5627894e49a0b35620","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/b4e847b9997b6c36e4a55c5627894e49a0b35620"},{"author":"nikhilkaul1234","date":"2026-07-30T19:26:23+00:00","message":"Apply style suggestions","sha":"c9127f498ab70b2ca73035ddb74063fa34fcb3b5","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/c9127f498ab70b2ca73035ddb74063fa34fcb3b5"},{"author":"nikhilkaul1234","date":"2026-07-30T19:20:50+00:00","message":"Reconcile Workspace permission-flow docs with the shipped experience\n\nEngineering confirmed the only automatic RBAC fixing for Workspaces is\nthe Reader banner on the Workspace and the Fix Permissions option on\nthe Scenario configuration page (fixResourcePermissions via REST).\nRemove the create-time Automatic role assignment step from the\nquickstart, document the three assignment paths on the permissions\npage, retitle the service-group known issue, and align the overview,\ncomparison, limitations, and classic security pages. Link the\nleast-privilege custom-roles article from the permissions page.","sha":"570da4254d23b90b046a65f4462c945adc4ea439","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/570da4254d23b90b046a65f4462c945adc4ea439"},{"author":"nikhilkaul1234","date":"2026-07-30T19:08:35+00:00","message":"Apply engineering review feedback to the sample-app tutorial\n\nChanges that were pushed to the sample-app-tutorial branch after #5073\nmerged: document the confirmed permission flow (Reader banner on the\nworkspace, Fix Permissions on the scenario configuration page when\nvalidation reports missing RBAC, least-privilege custom roles linked as\nthe alternative), pin the sample manifest to the 2.2.0 release, and\nmake the fix step deterministic with a zone topology spread constraint.","sha":"6213bf5ff807f500da46019358342c4323938454","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/6213bf5ff807f500da46019358342c4323938454"},{"author":"RenzoPrettoMS","date":"2026-07-30T16:37:23+00:00","message":"Add least-privilege custom roles how-to for Chaos Studio Workspaces (#5076)\n\nAdds guidance for customers who opt out of fixResourcePermissions and build least-privilege custom roles from scenario validation output. Adds a TOC entry under the Workspaces section. Rebased onto latest main to resolve TOC.yml merge conflict; applies accepted style suggestions.","sha":"cf5edf0f8c7c091d4e7023ec7edf7355bb2753ca","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/cf5edf0f8c7c091d4e7023ec7edf7355bb2753ca"},{"author":"nikhilkaul1234","date":"2026-07-30T10:47:06+00:00","message":"Add sample-app zone resilience tutorial for Chaos Studio Workspaces (#5073)\n\n* Add sample-app zone resilience tutorial for Workspaces\n\nAdds an end-to-end tutorial that deploys the AKS store demo sample app\nto a zone-redundant cluster and runs the Compute Zone Down scenario\nfrom a workspace, with TOC entry and cross-links from the workspace\nquickstart and the AKS guidance page.\n\n* Apply style suggestions\n\n* Rework tutorial into a break-fix-prove arc\n\nRun the zone-down scenario first against the app's default\nsingle-replica front end so the storefront visibly fails, then scale it\nout and rerun to validate the fix. Adds a monitoring-signals section\nand a report-comparison section.\n\n* Apply style suggestions","sha":"0379b0a7604e0213c352c67c54a9c620511809fd","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/0379b0a7604e0213c352c67c54a9c620511809fd"},{"author":"nikhilkaul1234","date":"2026-07-27T07:22:08+00:00","message":"Chaos Studio: remove How-to guides and agent sections from the hub page (#5030)\n\n* Remove How-to guides and Chaos Studio agent sections from the hub page\n\n* Label classic agent docs and redirect workspace users to agent-based scenarios\n\n* Add Linux distribution support for agent-based Scenarios\n\n* Restore Physical Memory Pressure and agent requirements lost in merge","sha":"d466fc84977e6525b9d94df9db5ae1844ce3ad7b","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/d466fc84977e6525b9d94df9db5ae1844ce3ad7b"},{"author":"nikhilkaul1234","date":"2026-07-20T15:00:51+00:00","message":"Document confirmed agent-based scenario support: restore Physical Memory Pressure, add requirements, update private networking","sha":"d48569e062303e149854bfd230f4ec024b0ed03b","url":"https://github.com/MicrosoftDocs/azure-monitor-docs/commit/d48569e062303e149854bfd230f4ec024b0ed03b"}]