Skip to content

Issues: Azure/azure-rest-api-specs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort

Issues list

Review request for Microsoft.Peering to add version stable/2025-05-01 ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review BreakingChange-Approved-Benign Changes are not breaking at the REST API level and have at most minor impact to generated SDKs. BreakingChange-JavaScript-Sdk BreakingChange-JavaScript-Sdk-Approved BreakingChange-Python-Sdk-Approved BreakingChange-Python-Sdk-Suppression BreakingChange-Python-Sdk-Suppression-Approved BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. new-api-version NotReadyForARMReview Peering PipelineBotTrigger ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test resource-manager
#34377 opened Apr 30, 2025 by JonathanSaraco Loading…
3 of 9 tasks
Peering: backend will "silently" remove subscription from registration list Peering Service Attention Workflow: This issue is responsible by Azure service team.
#9904 opened Jun 22, 2020 by magodo
ProTip! Find all open issues with in progress development work with linked:pr.