Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
13,307 questions
Suggestion on upgrading graph API from beta to v1.0 while changing permissions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 15%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Rohit Arora
5
Reputation points Microsoft Employee
Hi Team,
We have a Graph API, which we want to promote from beta to v1.0
But while promoting, we found out that some of the permissions should be changed.
As this beta version is currently used by many teams, which are using permissions, that are required to be removed, while calling this API. So, to do the API promotion we need a suggestion. One of the suggested paths for backward compatibility and API promotion can be:
- Maintain the current endpoint (beta) permissions unchanged. This ensures backward compatibility, causing no impact on existing clients or versions.
- For the v1.0 promotion, introduce the correct/pruned permission set. As clients integrate with v1.0, they'll utilize the appropriate permissions, preventing API call failures.
- At last beta version can also be changed to new set of permissions once all the clients migrate
Team, please suggest on this or if we have any other better suggestion?
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 7.000000000000001%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC3%3C/text%3E%3C/svg%3E)
Carolyne-3676 211 Reputation points2024-02-12T11:49:25.2633333+00:00 The proposed approach is workable. Additionally, lease review the endpoints supported by V1 and compare to what you have been using in beta to ensure that they are fully supported. Ideally it is not encouraged that users take dependency on beta as these APIs are subject to change. Overall ensure you monitor impact progressively.
Sign in to comment
Sign in to answer