With Application ID, TenantID and App Secret information to be able toĬall Graph API with application permissions. I returned the HTTP-request and prepared variables triggerOutputs()Īfter those steps I have user email and number of days that needs to be This is the format to exclude parameters from the GET Trigger (get) to retrieve user email and number of away days in
Next I built a Azure Logic Apps that uses HTTP Request Read theĭocumentation (& about permissions) from Docs & JSON to set the Automatic Reply / Out of Office. After that it was all about figuring out the Graph API call Registration** (applicationid, secret) with suitable set of API – and still keep on using standard licensing (no need to go toįirst it was necessary to create the** Azure App Setting up a Azure API Management service so that Azure Logic AppĬan be called from the Cloud Flow running inside Power Virtual Agent.Azure Logic Apps that uses **Graph API **to set the Out of Office /.That user it required to go beyond the wall and say “there is no spoon”.Īnd I found it there wasn’t a spoon- just the miracle world of GraphĪPI. Office 365 Set Automatic Replies action always works on Little bot to set up Out of Office for the interacting user. Was clear that I had reached the wall when I was trying to make my And after digging some information out (Thank Interacting with a Power Virtual Agent bot required to do actions onīehalf of that person. Some limits are due to licensing but someĪre due to other good reasons. It is always interesting to hit the wall with limitations when you are
0 kommentar(er)
