* Add Fabric Jobs Cancel Item Job Instance tool
Request cancellation once for an explicitly identified Fabric job, preserve accepted receipts and safe failure guidance, and cover routing, consent, and response edge cases offline.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Preserve cancellation failures for malformed Unicode metadata
Limit lazy JSON decoding handling to optional error metadata, retain HTTP status and retry guidance, add service and routed regression cases, and align the Jobs namespace overview with cancellation support.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Refresh Fabric REST API specifications and item definitions
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Prepare for Fabric MCP Server 1.7.0 release
Compile and curate synchronized Fabric release notes, preserving version 1.7.0 and consuming five pending fragments. Attribute resource refresh to #4078 and omit internal-only file I/O infrastructure.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Include shipped Fabric namespace concurrency fix in release notes
Attribute the user-visible namespace cache fix to #4057. Remote registry-only changes do not affect the shipped Fabric empty registry.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Keep merged resource refresh fragment consumed
Remove the fragment reintroduced by the squash-ancestry merge; its attributed release note is already present in both 1.7.0 changelogs.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Handle registry.json tool listing time-to-live and paging
* Few updates for paging and cache time handling
* Fix failing test
* Retain name filtering update
* Fix failing test
* Add opt-in source data for Search knowledge base retrieval
Preserve service defaults when the option is omitted, map all supported knowledge source kinds, and cover binding and SDK requests with focused tests.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Clean up bits of text
* Improve Search knowledge source lookup performance
Resolve knowledge sources concurrently and cache source-type metadata using the existing cache service.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* PR feedback
---------
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: alzimmermsft <48699787+alzimmermsft@users.noreply.github.com>
* Add Azure IoT Hub routing endpoint health and diagnostics tools
Provide a current endpoint-health snapshot and historical routing evidence, including downstream resource existence and per-metric availability without inferring overall hub health.
Use a dedicated routing service with cloud-aware ARM validation, SDK-default retries, bounded operations, and cancellation handling. Include command documentation, registration, unit tests, recorded tests, and routing test infrastructure.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Tighten IoT Hub routing metric fallback and ARM link validation
Only retry batched target metrics individually when Azure Monitor rejects
the batch with 400, the incompatible-metric case. Throttling and server
errors now fail the batch after SDK retries instead of fanning out into
per-metric requests that consume the operation budget.
Validate each ARM request URI, including nextLink continuations, before
resolving the tenant or credential so untrusted destinations fail before
any authentication work.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use IAzureService endpoint validation for IoT Hub routing ARM requests
#3884 removed the static EndpointValidator overload that took an executing tool namespace, so the routing service no longer compiles against main (CS1739). Validate ARM request and nextLink URIs through IAzureService.ValidateAzureServiceEndpoint, as IoTHubDeviceService now does. Tests use AzureServiceTestHelpers so endpoint validation stays real and shared ARM clients route through the test handler.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resolve IoT Hub routing targets only from the endpoint URI
Key-based endpoints have no endpointUri, and IoT Hub endpoint ids are opaque GUIDs rather than ARM resource IDs. The mapper fell back to the entity path or container name as the namespace or account name, so diagnostics checked a resource that does not exist and reported an existing target as notFound. Derive the target name only from the endpoint URI host so these endpoints report an unresolved target, and use opaque ids in the mapper fixture to match service responses.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Document unresolved IoT Hub routing targets for key-based endpoints
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Configure IoT Hub live test routing and devices in the post script
The live pipeline failed in test-resources-post.ps1 because the azure-iot CLI extension it used cannot be installed on network-isolated agents. Seed the test devices through the IoT Hub registry REST API with Microsoft Entra ID instead, and grant the test principal IoT Hub Data Contributor.
Also add the identity-based Service Bus routing endpoints in the post script rather than the template. IoT Hub validates those endpoints when they are created and rejects them (IH400117) until the routing identity's Service Bus Data Sender assignment takes effect. ARM cannot wait for that, so the post script retries until it does.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Validate IoT Hub resource names before building ARM resource IDs
Hub and resource group names were interpolated into ARM resource IDs. ResourceIdentifier accepts traversal segments, and URI normalization then sent the request elsewhere: rg1/../rg2 and rg1\..\rg2 read the hub from resource group rg2, and .. escaped to the subscription scope.
Reject names outside the Azure naming rules before any credential or network work. The check runs in the shared routing service path used by both routing commands, and in IoTHubService.GetIoTHub, which serves hub get and, through the hostname resolver, the device and query tools. Resource group names follow the documented rule: 1-90 letters or digits (Char.IsLetterOrDigit), underscores, hyphens, periods, or parentheses, not ending with a period. Routing targets built from the hub's endpoint configuration are reported as unresolved unless every name is a single path segment.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* [AzureBackup] Apply --storage-type when creating RSV vaults
RsvBackupOperations.CreateVaultAsync accepted storageType but never used it, so Recovery Services vaults were always created with the default GeoRedundant storage. After the vault PUT completes, apply the requested redundancy through the backupstorageconfig/vaultstorageconfig API (same path used by 'vault update --redundancy'). Invalid values are rejected before any ARM call, and storage-config failures report that the vault was created plus the 'vault update --redundancy' remediation.
Fixesmicrosoft/mcp#3981
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* [AzureBackup] Preserve RSV storage redundancy partial-failure guidance
Throw a dedicated VaultStorageRedundancyException (a RequestFailedException that keeps status and error code) when redundancy cannot be applied after an RSV vault is created. VaultCreateCommand surfaces its message ahead of the generic 409/403 mappings, so a storage-config conflict no longer reads as an existing-vault conflict. The retry command now includes --subscription and, when supplied, --tenant so it targets the vault just created.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Allow Azure Resource Graph Kusto endpoints in Kusto cluster URI validation
Add .arg.core.windows.net to KustoClient's domain suffix allow-list so the Kusto
tools can query Azure Resource Graph Kusto endpoints. The Kusto SDKs' well-known
endpoints already trust this suffix, and KustoClient already keeps the endpoint
path and requests the Kusto scope these endpoints use.
Fixes#4028
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: df5f4d96-6fea-431c-bc49-01af1461746b
* Make the KustoClient request test endpoint-agnostic
Rename the test and use neutral database and query arguments so it doesn't suggest
that Azure Resource Graph endpoints get special handling. Any cluster URI that
passes the allow-list works; this one includes a path to show it's preserved.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: df5f4d96-6fea-431c-bc49-01af1461746b
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: df5f4d96-6fea-431c-bc49-01af1461746b
* Add azurebackup operation get tool
Adds the azurebackup operation get command to read asynchronous RSV backup operation status at vault scope or protected-item scope. Returns timestamps, sanitized errors, and actual job IDs when present, without treating operation IDs as job IDs. Includes unit tests, a recorded integration test, docs, changelog, and consolidated-tools registration.
* Map OperationCanceledException to 504 in operation get command
Override GetStatusCode so all cancellations (including TaskCanceledException) return GatewayTimeout, matching the canceled GetErrorMessage instead of falling through to 500. Adds unit coverage for both exception types.
* Wait for operation-get live update LRO to complete before final assertions
The re-submitted protected-item update now awaits WaitForCompletionResponseAsync so the final-state checks observe the settled write and no operation lingers into later tests or cleanup. Re-recorded (assets tag 59d31d946a).
* Address operation get review feedback and refresh recording
* Add the Azure Resiliency Agent tool area
Exposes the Azure Resiliency Agent through a single conversation-level tool,
resiliencyagent_conversation_ask. A developer describes an application in their
own words and receives a zonal resilience assessment, or asks for zone-resilient
Bicep, ARM or Terraform templates for new resources.
The area holds no agent logic. It is a thin client over the agent's existing A2A
surface, so the backend keeps ownership of what a turn does, including which
scenario handles it and when to stop and ask the user something. That is why one
conversation-level tool covers both assessment and template generation rather
than one tool per Azure operation.
The agent is multi-turn: it asks its own clarifying questions before it can act.
A single tool call therefore carries an entire conversation. The command polls
the agent, raises an elicitation when the agent needs input, feeds the answer
back, and returns once. The host model issues one call and never sees the
polling, so clarifying questions reach the user exactly as the agent wrote them
rather than depending on a model to follow instructions about how to poll.
While a turn is running the agent publishes short reasoning steps. Those are
forwarded as progress notifications, which also resets client inactivity timers
on a call that can run for minutes.
Templates and reports are written to the caller's working directory and returned
as paths, following the pattern the Azure Migrate platform landing zone tool
uses. A generated template is more useful as a file that can be opened and
deployed than as text in a chat reply, and a long report does not have to travel
through the model's context. Artifact names arrive from a remote service and are
treated as untrusted input when used as file names.
The tool is marked LocalRequired because it asks the user questions over the
client connection, which is not available in HTTP mode.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Add Start Resilient Azure MCP tool surface
Add five architecture and IaC scenario tools, local file attachment with explicit consent and bounded in-memory caching, A2A FilePart forwarding, public data-boundary routing, MCP artifact content blocks, evaluations, documentation, and tests.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Clean up Resiliency Agent README entry
Remove stale POC prompts and use customer-facing service-area language.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Use generated Resiliency Agent evaluations
Remove the checked-in Vally specification and rely on the repository evaluator to generate unattended routing evaluations from the E2E prompt inventory. Normalize interactive scenarios to the supported context-required classification.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Evaluate inline resiliency IaC reviews
Add generated Vally coverage for inline ARM, Bicep, and Terraform reviews. Clarify that review commands accept source directly in the request while local files use attachment IDs.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Prefer attachments for IaC reviews
Guide complete and multi-file templates through the attachment flow while retaining direct support for templates pasted inline. Reserve existing IaC resiliency review for the format-specific Resiliency Agent commands instead of generic guidance tools.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Fix A2A inline file discriminator
Include the nested FileContent kind discriminator required by the A2A polymorphic contract so uploaded bytes, filename, and MIME type survive backend deserialization and blob offload.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Add general Resiliency Agent guidance
Add a conceptual guidance command and routing prompts, and make the public A2A endpoint plus delegated scope fixed production constants with no runtime environment overrides or auth bypass.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Add Resiliency Agent service owner
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Fix Resiliency Agent PR checks
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Handle canonical macOS temp paths in artifact tests
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Address Resiliency Agent review feedback
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Improve Resiliency Agent tool routing
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Improve Resiliency Agent artifact presentation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Materialize resiliency reports in workspaces
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Add clickable links for resiliency artifacts
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Retrigger PR checks
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Harden Resiliency Agent conversation handling
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Address Resiliency Agent artifact and test review
Preserve backend artifacts when workspace writes fail, harden metadata bounds, use factory-managed HTTP clients, and add recorded ARM/A2A playback coverage.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Fix Resiliency Agent cross-platform CI tests
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Clarify Resiliency Agent attachment evaluation prompt
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 974958dc-ded9-4351-bed3-07227e1bce92
* Add six resiliency Goals tools for GA 2026-10-01
Integrate the supplied GA SDK, typed tool contracts, lifecycle coverage, and published ECY recordings. Keep known CI readiness blockers explicit in the draft PR.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix Goals documentation links and trim investigation notes
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Trim Goals delivery documentation and consolidate regression tests
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use released Resilience Management SDK 1.0.0
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resolve Goals metadata tests through the command factory
Use the stable command lookup API so the new tests remain compatible with upstream CommandRegistration wrappers.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update existing Resiliency MCP Tools for GA Release
Migrate the Resiliency SDK integration and existing Drills API surfaces to GA. Add request validation, isolated fixtures, recording scenarios, HTTP contract tests, and documentation.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add SDK GA upgrade usage recovery plan
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* Resilience drills: keep integrated fixture plan Ready; align drill tools with GA SDK
- Drills fixture brings the recovery plan back to Ready (exclude new service-group members, finalize, checkReadiness) before and after the full failover/reprotect cycle; RO rejects failover unless the plan is Ready.
- Remove --recoveryplan from drill create/update: recoveryPlanId is read-only in the GA SDK and never serialized; the service links the service group's plan.
- Return the drill managed identity in drill get/create/update output.
- Always emit hasCompleted for drill resync, validation, add-or-update, and mark-complete results.
- Update docs, e2e prompts, skill reference, changelog, and tests.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resilience: expose remaining GA SDK request fields and re-record live tests
- Drill create/update: --identity, --chaos-resource-properties, --recovery-plan-properties, --monitoring-properties; update --resource-group.
- Drill run failover: --user-consent (Unspecified/Allowed).
- Recovery plan create: None identity, --default-group-unique-id, CustomRunbook action associatedIdentity (Zonal only).
- Recovery plan resource update: CrossZoneVMRecovery protection; rejected long-running updates now return 400 with the service error code.
- Usage plan create: --tags.
- Re-recorded affected live tests against GA 2026-10-01 (assets tag Azure.Mcp.Tools.ResilienceManagement.Tests_9f4bd3a70d), added a CrossZoneVMRecovery rejection test, removed orphan preview recordings.
- Tuned drill update and drill run failover descriptions (ToolDescriptionEvaluator: changed tools' non-clarification prompts min 0.618).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resilience: document drill update resource group as immutable after creation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resilience: consolidate test fixtures and record Goals tests on canary
Inline the drills post script into test-resources-post.ps1, remove the PR 3921 goal fixture scripts, add a dedicated goals service group to the main fixture, and record the Goals GA tests on canary until the service reaches production.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* up
* up
* up
* up
* Resilience: record drill run report tests and publish assets.json
- Read the report download URL and expiry from the raw operation response; the
service returns downloadUrl/expiryTimestamp, which the SDK model does not map.
- Sanitize the signed downloadUrl in recordings.
- Make the download URL test retry only on a 409 from a prior run operation and
stop generating a second report.
- Point assets.json at Azure.Mcp.Tools.ResilienceManagement.Tests_fe97a70f15
(79 recordings, including the three drill run report tests and a re-recorded
Should_create_usage_plan).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix cspell failure in drill run report eval doc
Remove the personal branch name that cspell flagged as unknown words.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix broken evaluator link in drill run report eval doc
Use the absolute GitHub URL, matching CONTRIBUTING.md, so the link check passes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* up
* up
* Resilience: read generate-report summary from the DrillRun envelope
generateReport returns 202 with the DrillRun resource, so the SDK model has no
value and the summary was always null. Read it from properties.report in the raw
operation response (same approach as the download URL), keep using the SDK
value when present, and assert the returned report in the recorded test. The
existing recording replays unchanged.
Also update the tool count in the Resilience skill tools reference to 49.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Dhruv Bharuka <dhruvbharuka@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add six resiliency Goals tools for GA 2026-10-01
Integrate the supplied GA SDK, typed tool contracts, lifecycle coverage, and published ECY recordings. Keep known CI readiness blockers explicit in the draft PR.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix Goals documentation links and trim investigation notes
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Trim Goals delivery documentation and consolidate regression tests
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use released Resilience Management SDK 1.0.0
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resolve Goals metadata tests through the command factory
Use the stable command lookup API so the new tests remain compatible with upstream CommandRegistration wrappers.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update existing Resiliency MCP Tools for GA Release
Migrate the Resiliency SDK integration and existing Drills API surfaces to GA. Add request validation, isolated fixtures, recording scenarios, HTTP contract tests, and documentation.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add SDK GA upgrade usage recovery plan
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* up
* Resilience drills: keep integrated fixture plan Ready; align drill tools with GA SDK
- Drills fixture brings the recovery plan back to Ready (exclude new service-group members, finalize, checkReadiness) before and after the full failover/reprotect cycle; RO rejects failover unless the plan is Ready.
- Remove --recoveryplan from drill create/update: recoveryPlanId is read-only in the GA SDK and never serialized; the service links the service group's plan.
- Return the drill managed identity in drill get/create/update output.
- Always emit hasCompleted for drill resync, validation, add-or-update, and mark-complete results.
- Update docs, e2e prompts, skill reference, changelog, and tests.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resilience: expose remaining GA SDK request fields and re-record live tests
- Drill create/update: --identity, --chaos-resource-properties, --recovery-plan-properties, --monitoring-properties; update --resource-group.
- Drill run failover: --user-consent (Unspecified/Allowed).
- Recovery plan create: None identity, --default-group-unique-id, CustomRunbook action associatedIdentity (Zonal only).
- Recovery plan resource update: CrossZoneVMRecovery protection; rejected long-running updates now return 400 with the service error code.
- Usage plan create: --tags.
- Re-recorded affected live tests against GA 2026-10-01 (assets tag Azure.Mcp.Tools.ResilienceManagement.Tests_9f4bd3a70d), added a CrossZoneVMRecovery rejection test, removed orphan preview recordings.
- Tuned drill update and drill run failover descriptions (ToolDescriptionEvaluator: changed tools' non-clarification prompts min 0.618).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resilience: document drill update resource group as immutable after creation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Resilience: consolidate test fixtures and record Goals tests on canary
Inline the drills post script into test-resources-post.ps1, remove the PR 3921 goal fixture scripts, add a dedicated goals service group to the main fixture, and record the Goals GA tests on canary until the service reaches production.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* up
* up
---------
Co-authored-by: Dhruv Bharuka <dhruvbharuka@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add Storage Intelligence disk diagnostics
* Support prefix-free application scopes
* Add host latency to disk diagnostics
* Remove Storage disk latency flag
* Improve storage disk diagnose tool description
* Support VMSS instances in disk diagnostics
* Add recorded live test for disk diagnostics
* Update disk resolver for Azure service API
* Default Storage Intelligence configuration
* Restore recorded endpoint for playback
* Address storage disk diagnostics review feedback
* Align disk diagnostics with latest command contract
* Fix disk diagnostics spelling checks
* Secure disk diagnostics endpoints and support tenant selection
* Adapt disk endpoint validation to the shared validator service
* Use Azure service facade for disk endpoint validation
---------
Co-authored-by: Pranjal Abhyankar <pabhyankar@microsoft.com>
docs: move Device Provisioning Service sections into alphabetical order
The sections added by #3898 were inserted between Insights and IoT Hub in all
three docs. Relocate them to their alphabetical position next to the other
Device services: between Deploy and Device Registry in azmcp-commands.md and
e2eTestPrompts.md, and between Database for PostgreSQL and Event Grid in the
README prompt list.
Pure block moves, no content changes; moved blocks contain no annotation
comments.
Fixes#3970
Co-authored-by: kun654 <273006726+kun654@users.noreply.github.com>
Amos HerschandCopilot App
azure-sdk-automation[bot]andazure-sdk
Alan ZimmerandCopilot Autofix powered by AI
Amishi-PanwarandCopilot
msalamanandCopilot App
Vinay GeraandCopilot
Christian Stump
Chidozie Ononiwu
vineetkalkiandCopilot
ghcp4a-bot[bot]andgithub-actions[bot]
Shraddha JainandCopilot
Karan SinghandCopilot
Steven Vukelich
Saswata PanditandCopilot
Connie Yau
pranjal-abhyankarandPranjal Abhyankar
kun654andkun654
KarishmaGhiyaandCopilot