Last 20 commits touching this section.
[SRE Agent] Improve the evaluation experience for new customers (#320216) * [SRE Agent] Rework evaluate.md as a new-user entry point The Evaluate article is the first node under Get started, but it opened on billing mechanics that assumed the reader already knew the product, the pricing model, and the vocabulary. This revision restructures the page around the go/no-go decision a first-time reader is actually making. Changes: - Add a product orientation opening. Two sentences on what the agent does, with links to the overview and run modes, so the trial offer has a subject before any charge is mentioned. - Add "How Azure SRE Agent charges". Defines Azure Agent Units, always-on, and active usage once each at first use, in a two-row table that contrasts the fixed and variable components and states what the trial waives. Adds the load-bearing concept that an agent bills because it exists, and that deletion is the only off switch. Magnitudes only; pricing-billing.md keeps ownership of rates and AAU math. - Rename the trial table to "What the trial includes" and add a self-qualification row. Align the agent-count wording with the legally reviewed "per account" phrasing instead of the conflicting "per customer". Replace "consumption charges" with the now-defined "active usage". - Add "Before you start", a short qualification summary covering subscription, region availability and the unregistered-subscription signal, the create-agent role requirement, model provider availability, and the fact that no trial enrollment step exists. Qualification only; create-and-set-up.md keeps the full prerequisite list. - Replace the "Get started" setup walkthrough and "Top use cases" with "What to try during your evaluation". Cuts the duplicated connector instructions down to one handoff link, adds a minimum-viable evaluation path (one agent, one service, one known problem), and reorders the use cases as a prioritized list. - Expand "When the trial ends" with the automatic day-31 transition, the per-agent window, and the explicit delete-to-stop-charges instruction with the stop-versus-delete distinction. - Add a "Not ready to create an agent yet?" exit path for readers who need overview, pricing, security, or region background first. This replaces the single-link Related content section it duplicated. - Correct ms.topic from reference to concept-article for a Get started entry node, and refresh ms.date. Terms and conditions is byte-identical to the legally reviewed version (SHA256 F10D4EBE36E486C9AAF9D3365FC7D681AB320A8B008C66B7342115722B9B19B5 before and after). Unresolved billing and UI facts are flagged in place with non-rendering HTML comments rather than guessed: the eligibility unit and snapshot date, whether deleted agents count permanently, the scope of the no-feature-limitations claim, and the trial banner location. All relative links and heading anchors were verified against the article's own directory. No other file is touched. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * [SRE Agent] Annotate unresolved evaluate trial claims Add actionable, non-rendering evidence comments for offer eligibility, snapshot scope, deleted-agent accounting, per-agent timing, automatic enrollment, trial feature parity, and the deletion UI label. Also mark plan acceptance gaps for first-use cost terminology, article-only month-one arithmetic, and the remaining setup walkthrough. Remove the now-source-confirmed banner comment. Rendered prose and the legally reviewed terms block remain unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * [SRE Agent] Resolve SME findings in the evaluate article Rework the rendered prose so every reader-facing claim is traceable to published product docs or to the legally reviewed offer terms, and so the page stops promising mechanics that no available source establishes. Findings resolved: - Run-mode contradiction. The opening no longer links run-modes.md, which contradicts runtime mode semantics. The sentence now names the two controls an evaluator actually sets - the permissions they grant and the approval settings they choose - and links permissions.md, which documents the Reader and Privileged levels chosen at agent creation. The run-modes.md dependency defect remains open with its owner, but this page no longer depends on it. - Always-on defined at first use. The second sentence of the article now defines the always-on charge inline as the fixed hourly charge every agent accrues for as long as it exists, before the charge table restates it. - Cost decision usefulness without invented arithmetic. The active usage paragraph now carries published AAU magnitudes from the pricing article's task table (roughly 1-4 AAUs for a quick question, 12-35 for an automated incident investigation, 30-87 for a full diagnose-and-fix run, across the published models), tells the reader to total the runs they plan, and hands off to the Azure SRE Agent pricing page for the regional price. It also states the ceiling mechanism: a monthly AAU allocation set in Settings > Agent consumption, minimum 500 AAUs, after which the agent stops responding until the next month. No currency figure is invented. - Unsupported offer mechanics removed. The trial table now states only what the offer terms state: always-on waived during trial access, customers new to Azure SRE Agent, up to three agents per account, up to 30 days, active usage still charged, and automatic transition to standard pricing unless the agent is deleted first. The fixed Aug 25, 2026 snapshot date, the historical eligibility self-check, the deleted-agents-count claim, the per-agent 30-day window, the Day-31 calculation, the automatic-enrollment claim, and the absolute no-feature-limitations claim are all gone. The limitations row now says what is true and checkable - the terms describe billing, not feature gating - plus the abuse and suspension clause the terms do state. - Setup walkthrough removed. "What to try during your evaluation" now scopes the evaluation (one agent, one known service, one known problem) and hands off once to create-and-set-up.md. No connector instruction remains. - Collaboration destinations narrowed. "Close the loop" no longer claims ServiceNow incident updates through a connectors anchor that documents only Teams and Outlook. It now names GitHub issues, Azure DevOps work items, Teams, and email, and links execute-mitigations.md, which documents those response paths. - Deletion UI corrected to the shipped labels: Settings > Basics, then in Delete SRE Agent select Delete. - Trial-end section rewritten around the terms: standard pricing applies automatically with no second confirmation step, with the delete escape hatch and the stop-versus-delete distinction in the same place. Banner behavior is tied to the trial period rather than to an unverified Day 31. Retained comments, all non-rendering and owner-addressed: eligibility rule and scope (Product/Commerce), meaning of account and whether deletion frees a slot (Product/Commerce/Control Plane), derivation of the trial end date and whether the window is per agent or per account (Control Plane/Billing), how trial access is granted (Product/Control Plane), trial entitlement matrix if a positive no-limitations claim is wanted (Product), and a month-one currency figure or worked currency example (Pricing). Terms and conditions is byte-identical to the legally reviewed version (SHA256 97E47F875E3E9AB8A85D2FEA1276A0FFD3C42AE684E2F3098E1C1D0AD52C67F1 before and after). All relative links and heading anchors were revalidated against the target files. No other file is touched. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * [SRE Agent] Finalize evaluate article with editorial pass Final copyedit of articles/sre-agent/evaluate.md for a first-time reader making a go/no-go evaluation decision. Prose, terminology, and scanability only; no technical claims were changed, and every unresolved item stays in a non-rendering comment beside the claim it qualifies. Editorial changes: - Split the intro sentence pile-up so the permission and approval boundary reads as its own statement, and clarified that the agent investigates with all connected context in one place. - Used the approved short form "SRE Agent" in the charges section to stop the product name repeating directly under its own heading, and dropped the serial comma from the two-item bill description. - Replaced the "the concept that matters most" framing with the plain claim that an agent costs money because it exists. - Converted the three inline AAU task estimates into a scannable Task/Example/ Typical cost table so a budget owner can size an evaluation without parsing a sentence, and stated that ranges vary by model provider. - Named the spending cap as a monthly active usage allocation, matching the active-flow limit documented in pricing-billing.md, and split the run-on into separate sentences. - Removed colon splices joining independent clauses in the evaluation lead-in and in both trial-end paragraphs. - Cut the duplicate "health checks" clause and the "ensure the stability of your systems" filler from the operational risks item. - Replaced the internally named "query trigger" and the "threshold-based log query crosses its threshold" repetition with a behavior description, and flagged the missing public label in a comment. - Tightened the trial enrollment row, the prerequisites lead-in, and the offer table lead-in. Comment hygiene: - De-duplicated the trial-window question so the table row asks for the per-agent versus per-account rule and the trial-end section asks how the end date is derived. - Kept the eligibility row as the single owner of the "what does account mean" question and reduced the agent-limit comment to slot accounting only. - Removed source-provenance phrasing from the agent-limit comment. - Reflowed the pricing evidence-gap comment; the request is unchanged. Validation: - Terms and conditions block is byte-identical to the legally reviewed version in a6cb2e5d06d3 (829 characters, exact match). - All 18 relative links and anchors resolve, including the same-page terms anchor; AAU figures still match pricing-billing.md. - No Output Blocklist terms, TODO markers, provenance narration, or internal context in rendered prose; all 8 HTML comments are well formed and non-rendering. - Branch scope is a single file: articles/sre-agent/evaluate.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * [SRE Agent] Apply author feedback to the evaluate article Resolve the outstanding publication blockers in evaluate.md from direct author guidance and restore the pre-revision evaluation scenarios. - Fold the approved consumption-charge sentence into the intro paragraph. - Remove the "Typical cost" AAU estimate table, its framing sentences, and the "To size an evaluation" paragraph; static estimates go stale, so point readers to the pricing calculator and Pricing and billing instead. Drop the Pricing evidence-gap comment that qualified the removed text. - Resolve the eligibility blocker: customers know whether they are new to the service, so no additional eligibility-check mechanism is documented. - Resolve the deleted-slot blocker: the offer covers three spots total and deleted agents still count, so deleting doesn't free a spot. - Resolve the billing-window blocker: the trial period begins the day the first Azure SRE Agent is created and concludes 30 days after, stated consistently in the offer table and the trial-end section. - Resolve the feature-matrix blocker: no features are limited during the trial, so the limitations answer states that directly. - Remove the "Trial enrollment" row and its blocker comment. - Rewrite the evaluation-scope paragraph with the approved wording. - Restore the original wording and order of the evaluation scenarios list. - Clarify that the fixed charge begins if the agent still exists after 30 days. - Remove the "Not ready to create an agent yet?" section. - Update ms.date to 09/03/2026. The Terms and conditions block is unchanged and byte-identical to upstream/main. The only comment retained is the unrelated, still-actionable log-query trigger blocker. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Apply batched suggestions from code review Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> Co-authored-by: Craig Shoemaker <craigshoemaker@gmail.com> * Fix grammar: 'always-on change' to 'charge', 'includes' to 'include' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Address review feedback on evaluation guidance Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> Co-authored-by: craigshoemaker <127797+craigshoemaker@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d
[SRE Agent] Improve workflow automation guidance (#320226) * Improve the Automate workflows getting-started article Rework the final getting-started article so a first-time builder can finish the workflow without stalling on unstated prerequisites or conflicting names. - Remove "Step 5" from the title and replace the numbered cross-references with article titles, matching the rest of the getting-started set. - Standardize on "custom agent" for the built object, matching the portal Create menu and the concept, connector, and scheduled-task articles, and note once that some surfaces call the same object a subagent. - Expand prerequisites to cover the SRE Agent Administrator role, a Microsoft 365 account with an active mailbox, tenant consent for the OAuth sign-in, Azure resource access for the example task, and the required prior articles. - Explain the sign-in and managed-identity split before the connector steps instead of after, and state that Azure creates the identity with the agent. - Replace the unconfirmed Jira and Grafana connector examples with connectors named in current articles, and expand MCP on first mention. - Correct the connector wizard labels to "Set up tools" and "Permission", and drop the Preview qualifier from the Office 365 Outlook card. - Warn that a scheduled task in Autonomous mode runs an Ask operation without approval, which is what makes the locked recipient matter. - Orient the reader to the Agent Canvas, gloss tools, skills, and hooks, and add guidance on what makes a custom agent instruction work. - State time-zone behavior explicitly, including the UTC custom cron field, and add recurring metered-usage guidance where the schedule is set. - Add an "If the task doesn't run" section covering execution history, failed runs, and the four most common silent failures. - Rewrite the closing summary to claim only completed outcomes, with a conditional line for the optional investigation and incident articles. - Add non-rendering verification comments beside the ten claims that need an owner or SME answer, and update ms.date. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Add SME evidence comments to workflow tutorial Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Resolve SME findings in workflow automation tutorial Correct the connector preview badge, wizard labels, Automation navigation, UTC and daylight saving behavior, global tool inheritance, agent identity, execution and failure visibility, role gate, and scheduled task field labels against SME evidence and sibling articles. Replace the unsupported Review-mode failure row with guidance the execution grid can support, and add workflow alternatives for readers whose first automation isn't an email report. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Editor pass on workflow automation tutorial Apply Microsoft style, Learn formatting, and terminology consistency to articles/sre-agent/automate-workflows.md. Fix two alert blocks whose pseudo-titles collapsed into the body text, move the alternative-workflow paragraph under How it works so Add a connector opens on its own subject, promote cleanup guidance to a Clean up resources section, expand RBAC at first use, and correct a comma splice in the task details example. Trim meta-narration and tighten UI label capitalization. No technical claims changed; all five VERIFY comments retained. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Apply suggestion from @learn-build-service-prod-06[bot] Co-authored-by: learn-build-service-prod-06[bot] <274430002+learn-build-service-prod-06[bot]@users.noreply.github.com> * Apply PR review feedback to workflow automation tutorial Use the Build + setup navigation label, remove directional language, add the wizard Next and Create steps, italicize role names, lowercase autonomous mode, rename the test section to Verify the outcome, and remove the resolved evidence comments and redundant callout headings. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Apply suggestion from @craigshoemaker * Apply Learn Authoring Assistant style suggestions Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-06[bot] <274430002+learn-build-service-prod-06[bot]@users.noreply.github.com> Co-authored-by: craigshoemaker <127797+craigshoemaker@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d
[SRE Agent] Update Agent Canvas creation instructions (#320756) * Update Agent Canvas creation instructions (cshoe_microsoft/squad-sre#51) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Update articles/sre-agent/create-skill.md Co-authored-by: learn-build-service-prod-01[bot] <274427437+learn-build-service-prod-01[bot]@users.noreply.github.com> --------- Co-authored-by: craigshoemaker <127797+craigshoemaker@users.noreply.github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-01[bot] <274427437+learn-build-service-prod-01[bot]@users.noreply.github.com>
[SRE Agent] Improve complete setup guidance (#320223) * Rewrite complete-setup.md as the connection decision aid Reframe the article around which sources to connect and why, rather than a walkthrough of the setup page progress bar. - Open by addressing both readers, the person who skipped sources during onboarding and the person whose investigation came back thin. - Add a minimum-viable statement so the source table doesn't read as required work. - Rebuild "What each source adds" as a decision table keyed to the question each source lets the agent answer, with per-source access requirements in their own column. - Add conditional connection guidance branched by symptom instead of a single flat order, and flag Azure resources and incidents as the connections most likely to need someone else's approval. - Add a prerequisites section covering agent role, Azure role for resource scopes, per-source access, and existing alert rules. - Name the telemetry providers and their authentication model, and link the telemetry connector article for the full list. - Locate the setup entry point on the Operations Hub Overview status bar and describe connected card state. - De-emphasize the progress bar and state what it measures. - Add a verification section covering card state plus a per-source prompt that proves the agent can reach the new source. - State the behavior change from connecting an incident platform and the metered-usage implication of more connected context. - Update Related content and refresh ms.date. Three unresolved claims carry non-rendering HTML comments for SME confirmation: the setup-page Logs provider set, the role required for telemetry and incident connectors, and the progress denominator. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Add SME verification comments to complete setup Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Resolve SME findings in complete setup Narrow the additive-and-reversible claim to the sources that accumulate, state the one-active incident platform behavior, add provider visibility and per-role access detail, scope the alert-rule prerequisite by platform, explain the progress bar denominator, paraphrase the unverified UI string, drop the unverified /learn behavior and knowledge navigation label, correct the connection verification signal, and align cost wording with metered processing rather than connections. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Apply final editorial pass to complete setup Tighten prose to Learn style and natural voice: recast the log-provider paragraph around how each provider authenticates, correct the code and logs access requirements, replace the jargon lead-in for the conditional list, clarify what the progress bar measures, invert the knowledge-review cross-reference, and use a placeholder instead of a bare X in the sample resource-group prompt. No technical claims changed, and the open incident-platform role comment is retained. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d * Apply suggestion from @learn-build-service-prod-02[bot] Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> --------- Co-authored-by: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d
Add Brazil South, Japan West, Central India, and South India regions Closes cshoe_microsoft/squad-sre#35 - Add Brazil South (South America) - Add Central India (Asia Pacific) - Add Japan West (Asia Pacific) - Add South India (Asia Pacific) These regions are added to the supported regions table in alphabetical order. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
[SRE Agent] Add disaster recovery guidance (#320098) * Add disaster recovery guidance for Azure SRE Agent Adds articles/sre-agent/disaster-recovery.md, a new reference article covering cold-standby disaster recovery for Azure SRE Agent: - Key DR terms (RTO, RPO, cold standby, blast radius) and the shared responsibility model between Microsoft and the customer. - How a cold-standby deployment works: two independent agent resources, a shared user-assigned managed identity, and distinct system-assigned identities per agent. - Preparation checklist to complete before an outage, including infrastructure-as-code definitions, regional networking, activation-source fencing, and isolated recovery drills. - A step-by-step failover procedure (declare outage, fence the primary, start the backup, validate dependencies, switch callers, activate production work, monitor) with explicit guardrails against running two production agents at once. - A controlled failback procedure back to the primary region, since runtime state created by the backup can't be merged back. - Guidance for setting realistic RTO/RPO targets and fitting DR into a broader business-continuity plan. Registers the article in articles/sre-agent/toc.yml under Reference, directly after "Deploy with Infrastructure as Code" since the DR workflow builds on that IaC deployment path and precedes the FAQ section. Validation performed: - Confirmed toc.yml parses as valid YAML. - Confirmed only the two intended files changed in the diff. - Verified every relative link and anchor in the new article resolves to an existing file/heading (api-reference.md#control-plane-arm-operations, pricing-billing.md#what-happens-if-i-stop-my-agent, supported-regions.md, deploy-iac.md, data-privacy.md, network-integration.md, network-requirements.md, audit-agent-actions.md). - Verified frontmatter fields (title, description, ms.topic, ms.service, ms.date, author, ms.author, ms.reviewer, ms.ai-usage, ms.custom, customer intent comment) match the conventions already used across articles/sre-agent/**. - Verified heading structure (single H1, H2 sections, closing "## Related content") matches Learn authoring conventions used elsewhere in the service. - Scanned the new article for internal-only terminology and session artifacts; none found. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3e81954a-724a-4e83-b955-35faefbca06e * Apply batched suggestions from code review Co-authored-by: learn-build-service-prod-01[bot] <274427437+learn-build-service-prod-01[bot]@users.noreply.github.com> * docs(sre-agent): improve readability of disaster recovery article - Add blank lines between top-level bullets in Prepare for a regional outage checklist for easier scanning. - Add an introductory paragraph under Fail over to the backup agent framing failover as a controlled sequence. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3e81954a-724a-4e83-b955-35faefbca06e * Apply suggestion from @craigshoemaker * Convert sequential disaster recovery steps to numbered lists Address the blocking review on PR 320098. The preparation checklist, the primary-fencing checks, and the backup activation steps are all ordered procedures, so they now use numbered lists instead of bullets. Numbering style matches the existing failback and RTO lists in the same article. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d --------- Co-authored-by: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-01[bot] <274427437+learn-build-service-prod-01[bot]@users.noreply.github.com> Copilot-Session: 3e81954a-724a-4e83-b955-35faefbca06e Copilot-Session: 92bf1425-8f57-4c2d-8ac1-c132675c479d
Apply batched suggestions from code review Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com>
Apply batched suggestions from code review Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com>
Update data residency section in data-privacy.md Clarified data residency standards for SRE Agent, specifying data transfer and storage policies.
[SRE Agent] Update: Azure SRE Agent overview (#319771) * Refresh the Azure SRE Agent overview Restructure the overview around customer outcomes, add a security and governance section, and correct run-mode, connector, provisioning, and pricing claims. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ba292050-b2e1-492b-8c6f-4f1ec4119ddc * Apply suggestions from code review Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * update overview * Apply suggestions from code review Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> * personal panel update * Apply suggestions from code review Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> * clarity edits * clarity edits * Apply suggestions from code review Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> --------- Co-authored-by: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> 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-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> Copilot-Session: ba292050-b2e1-492b-8c6f-4f1ec4119ddc
[SRE Agent] Fix Azure SRE Agent getting-started guidance (#319870) * docs: correct SRE Agent getting-started journey * Apply learn-build-service-prod-05 style suggestions Accept the 8 Microsoft Writing Style Guide suggestions from the learn-build review on PR 319770 (active voice, may->might/can, concise sentences, by using). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6a765436-3a6c-4969-a11f-674a58dcc728 * adding final punctuation --------- Co-authored-by: dm-chelupati <dchelupati@microsoft.com> Co-authored-by: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: Diana Richards <103777760+v-dirichards@users.noreply.github.com> Copilot-Session: 6a765436-3a6c-4969-a11f-674a58dcc728
[SRE Agent] Add live reports preview documentation (#319753) * init live metrics article * update VNET article * inspect * simplify live reports * Apply suggestions from code review Co-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[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> * Prepare live reports documentation for publishing Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Restore network controls article date Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update articles/sre-agent/network-integration.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * Update articles/sre-agent/network-integration.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * Update articles/sre-agent/network-integration.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * Apply suggestion from @craigshoemaker * updates * Integrate live reports feedback from PR #319741 Applies source commit ca96be37a7b653cad4b304424aa89c2e6d3e14ee ("update nits") from MicrosoftDocs/azure-docs-pr PR #319741 onto this branch. Conflicts in articles/sre-agent/live-reports.md were resolved to keep the source commit's intent while preserving the later corrections already reviewed on this branch: the model-generated analysis caveat, the cache authorization recheck statement, the active-flow pricing anchor link, article ownership metadata, list and heading structure, and the "The preview" wording. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ba292050-b2e1-492b-8c6f-4f1ec4119ddc * Apply suggestions from code review Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Cary Chai <69606408+cachai2@users.noreply.github.com> * update user roles table * reset to live version (with a few cuts) * cuts * Update articles/sre-agent/network-integration.md Co-authored-by: learn-build-service-prod-06[bot] <274430002+learn-build-service-prod-06[bot]@users.noreply.github.com> --------- Co-authored-by: Cary Chai <69606408+cachai2@users.noreply.github.com> Co-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[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: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-06[bot] <274430002+learn-build-service-prod-06[bot]@users.noreply.github.com> Copilot-Session: ba292050-b2e1-492b-8c6f-4f1ec4119ddc
[SRE Agent] Update: Evaluate SRE Agent (#319446) * Add trial access section to pricing and billing documentation for Azure SRE Agent * Add into to trial access section * updates * Apply suggestions from code review Co-authored-by: Craig Shoemaker <craigshoemaker@gmail.com> * update explanation copy * update landing page with free trial links * updated copy * Add evaluation and pricing details for Azure SRE Agent; update onboarding content * Apply suggestions from code review Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * fix broken link * Add trial end details and consumption tracking information to evaluation and pricing documents * Fix evaluate.md title/description and evaluate-offer include link Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * update landing page * Apply suggestions from code review Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> * Fix description for Azure SRE Agent evaluation trial duration * Add trial terms and conditions for Azure SRE Agent evaluation * update landing page * update evaluate copy * Apply suggestions from code review Co-authored-by: zozomsft <mibrzozowski@microsoft.com> * add get started sections * update terms * update offer table * update intro paragraph and offer table * updates * updates * updates * add next step action button * Add ms.topic metadata to evaluate-offer.md --------- Co-authored-by: Craig Shoemaker <craigshoemaker@microsoft.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@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: zozomsft <mibrzozowski@microsoft.com> Co-authored-by: James Barnett <v-jabarnett@microsoft.com>
Change subnet size requirement for Azure VNet (#319424) Updated subnet size requirement from /28 to /27 for Azure Virtual Network.