The app already has the Calendars.Read.Shared permission which lets you read any calendars shared with the logged-in user.
Things that could be added:
[ ] To read usernames the app additionally needs the User.ReadBasic.All delegated permission.
[ ] To book a meeting the app additionally needs the Calendars.ReadWrite delegated permission.
Also, would be nice, but not entirely needed:
To circumvent the slightly annoying device flow login process (the one which makes you paste in a code), the app needs to: (1) create a client secret (IT will need to give us the value); and (2) register a 'web' redirect URI that points to a port on localhost
The app will then need to listen on that port whilst the user authenticates. When the user logs in, Azure will send the token to localhost and the app can then parse it from there.
The user still has to log in to Azure to use the app, but they don't have to enter the code. If they are already logged into Outlook or other Azure services then the entire process should not require user input at all.
The app already has the
Calendars.Read.Sharedpermission which lets you read any calendars shared with the logged-in user.Things that could be added:
User.ReadBasic.Alldelegated permission.Calendars.ReadWritedelegated permission.Also, would be nice, but not entirely needed:
To circumvent the slightly annoying device flow login process (the one which makes you paste in a code), the app needs to: (1) create a client secret (IT will need to give us the value); and (2) register a 'web' redirect URI that points to a port on localhost
The app will then need to listen on that port whilst the user authenticates. When the user logs in, Azure will send the token to localhost and the app can then parse it from there.
The user still has to log in to Azure to use the app, but they don't have to enter the code. If they are already logged into Outlook or other Azure services then the entire process should not require user input at all.