I am expermimenting with people in MSGraph. I am attempting the "/me/people" graph call and getting a 403 forbidden. The People.Read permission states it does not need Admin Consent. People permissions. I expected that the first time the web part is used the user would be prompted to give consent. Instead I just get a 403 in Chrome's developer console.

My package-solution

"$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package- 
"solution": {
   "name": "sp-graph-people-picker-client-side-solution",
   "id": "xxx",
   "version": "",
   "includeClientSideAssets": false,
   "webApiPermissionRequests": [
     "resource": "Microsoft Graph",
     "scope": "User.Read.All"
     "resource": "Microsoft Graph",
     "scope": "People.Read"
 "paths": {
   "zippedPackage": "solution/sp-graph-people-picker.sppkg"

The code snip-it:

let ctx: WebPartContext = this.props.context;
let userSearch:string=`/me/people`;

    console.info("!!! people",people);

The code that uses the User.Read.All is nearly the same and works. The difference is I had our Admin approve it in the Sharepoint Admin center. I would like to use the permission scopes that do not need admin approval without having to get admin approval. Any suggestions?


The permissions requested in the SPFx package need to be granted by a SharePoint Admin explicitly. Even the ones which do not need an admin consent e.g. People.Read

This is so that all permission scopes allowed to be consumed from SPFx customisations have to go through Admin approval.

By default if no permissions are granted, the only available permissions scope is user_impersonation which allows you to get limited information from the Graph.

See these links for more details:



Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.