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
Sort

Issues list

[BUG] startDate&endDate returned by service should be in ISO 8601 format Billing bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. Service Attention Workflow: This issue is responsible by Azure service team.
#33009 opened Mar 5, 2025 by ChenxiJiang333
[Billing] Fix a type mismatch ARMReview Billing 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. NotReadyForARMReview PipelineBotTrigger resource-manager
#32870 opened Feb 26, 2025 by necusjz Loading…
1 of 8 tasks
Billing Demo: MPG + Suppression ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review Billing BreakingChange-Approved-Benign Changes are not breaking at the REST API level and have at most minor impact to generated SDKs. BreakingChange-Approved-BranchPolicyException Changes violate the branch policy but exception has been granted. aka.ms/azsdk/pr-brch-deep BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR BreakingChange-Approved-UserImpact Changes are not backward compatible and may cause customer disruption. BreakingChange-Go-Sdk-Suppression BreakingChange-Go-Sdk-Suppression-Approved BreakingChange-JavaScript-Sdk-Suppression 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 PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager
#30650 opened Sep 19, 2024 by wanlwanl Draft
ProTip! Mix and match filters to narrow down what you’re looking for.