Search results

Clarify Permissive-In / Strict-Out Naming Policy in Guidelines

Status: Open.

#571 In microsoft/api-guidelines;

· apiarya opened on Jul 31, 2025

Issue: All down your Review Page is unanswered and unsatisfied Customers.

Status: Open.

#570 In microsoft/api-guidelines;

· DailyInvestors opened on Jul 2, 2025

Im

Status: Open.

#562 In microsoft/api-guidelines;

· 3BMarkW3D opened on Oct 5, 2024

Continue with the team

Status: Open.

#560 In microsoft/api-guidelines;

· Machine391 opened on Sep 9, 2024

Broken link for long running operations

Status: Open.

#559 In microsoft/api-guidelines;

· javieralvarezchiang opened on Sep 9, 2024

API Guidance does not explain the term workload

Status: Open.

#558 In microsoft/api-guidelines;

· apiarya opened on Aug 16, 2024

Integrate uniform versioning guidelines

Status: Open.

#554 In microsoft/api-guidelines;

· nickwalkmsft opened on Jul 16, 2024

Make auth guidelines more explicit

Status: Open.

#544 In microsoft/api-guidelines;

· tg-msft opened on May 6, 2024

Revisit response time requirements for non-LRO operations

Azure GuidelinesThis issue relates to the Azure Guidelines.This issue relates to the Azure Guidelines.

Status: Open.

#542 In microsoft/api-guidelines;

· mikekistler opened on Apr 30, 2024

Add guidelines to prefer "flat" over "nested" structures

Azure GuidelinesThis issue relates to the Azure Guidelines.This issue relates to the Azure Guidelines.

Status: Open.

#541 In microsoft/api-guidelines;

· mikekistler opened on Apr 22, 2024

Re-examine guidance for including eTag in response to PUT request

Azure GuidelinesThis issue relates to the Azure Guidelines.This issue relates to the Azure Guidelines.

Status: Open.

#540 In microsoft/api-guidelines;

· mikekistler opened on Apr 22, 2024

Why does collection response use value property instead of values in Azure API guidelines?

Status: Open.

#539 In microsoft/api-guidelines;

· zendu opened on Apr 15, 2024