{"id":782,"date":"2021-09-08T16:12:16","date_gmt":"2021-09-08T20:12:16","guid":{"rendered":"https:\/\/blog.markdepalma.com\/?p=782"},"modified":"2021-09-08T16:12:18","modified_gmt":"2021-09-08T20:12:18","slug":"using-application-permissions-and-client-credentials-grant-flow-with-hybrid-exchange-graph-api","status":"publish","type":"post","link":"https:\/\/blog.markdepalma.com\/?p=782","title":{"rendered":"Using Application Permissions (and client credentials grant flow) with Hybrid Exchange Graph API"},"content":{"rendered":"\n

We recently came across an application that uses Graph API and we wanted to start using it for some our on-prem mailboxes. Hybrid Graph API only supports delegated authentication flows and not application authentication flows. Just because something isn’t “supported<\/em>” doesn’t mean you can’t make it work! There are two things that we’ll need to do to make this work.<\/p>\n\n\n\n

First, any internet-facing Exchange server will need to have ‘V1S2SAppOnly<\/strong>‘ OAuth support added. You can do this by adding V1S2SAppOnly<\/strong> to the OAuthHttpModule.Profiles<\/strong> key in the REST web.config<\/strong> (ex. …\\Program Files\\Microsoft\\Exchange Server\\V15\\FrontEnd\\HttpProxy\\rest<\/strong>). Once you add this value the key should look like this:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

After this has been added either perform an iisreset<\/strong> or restart the ‘MSExchangeRestFrontEndAppPool<\/strong>‘ app pool in IIS for each server where you did this modification.<\/p>\n\n\n\n

The next step is to add the appropriate ‘AppOnlyPermissions<\/strong>‘ to the Microsoft Graph partner application in Exchange\/AD. First we’ll take a look at our Graph partner application:<\/p>\n\n\n\n

Get-PartnerApplication | Where {$_.Name -like '*graph*'} | select *permissions* | fl\n\nAppOnlyPermissions : \r\nActAsPermissions   : {Mail.Read, Mail.Write, Mail.Send, Calendars.Read...}<\/pre>\n\n\n\n
The ‘AppOnlyPermissions<\/strong>‘ value should be blank. We need this to match the ‘ActAsPermissions<\/strong>‘ value. You’d think (and some other articles say) that you could just run Set-PartnerApplication -AppOnlyPermissions<\/em>… but this was not a supported parameter for me. To set this we’ll have to edit AD directly. You’ll need to fire up something like ADSIEdit<\/a>, load the AD configuration partition, and drill down to your Exchange org and partner application object. The path should be something like:<\/p>\n\n\n\n
CN=Microsoft Graph,CN=Partner Applications,CN=Auth Configuration,CN=YOUR_EXCH_ORG,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com<\/pre>\n\n\n\n
Once here you’ll need to open the ‘Microsoft Graph<\/strong>‘ object and copy the ‘msExchConfigurationXML<\/strong>‘ attribute value to the clipboard:<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
Next, we’ll use Notepad++<\/a> and the XML Tools<\/a> plugin to manipulate this. MAKE SURE YOU BACKUP THIS VALUE.<\/strong> We want to convert this to a nicely formatted XML output so that it is easy to work with. To do this we use the ‘Pretty print’ option in XML Tools.<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
Once we have this we’ll need to duplicate all of the ‘ActAsPermissions’ lines and then use find and replace to convert those tags to be ‘AppOnlyPermissions’. Doing this will create a set of application permissions based on our delegated permissions (ActAsPermissions).<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
Once completed we need to linearize the output again so that we can copy it back into AD. We can use the ‘Linearize’ option in XML Tools for this:<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
Once we have the XML in the proper format we can put it back in the AD object:<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
Now that we’ve updated the AD object we can verify everything looks good by checking Exchange again (AppOnlyPermissions<\/strong> should have the same values as ActAsPermissions<\/strong>):<\/p>\n\n\n\n
Get-PartnerApplication | Where {$_.Name -like '*graph*'} | select *permissions* | fl\r\n\r\n\r\nAppOnlyPermissions : {Mail.Read, Mail.Write, Mail.Send, Calendars.Read...}\r\nActAsPermissions   : {Mail.Read, Mail.Write, Mail.Send, Calendars.Read...}<\/pre>\n\n\n\n
At this point you should be able to access on-prem Exchange resources using the supported Graph API functions with Application Permissions.<\/p>\n\n\n\n
NOTE: One limitation of this is that application access policies<\/a> (set in EXO) DO NOT<\/em> apply and are ignored when accessing an on-prem mailbox.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"
We recently came across an application that uses Graph API and we wanted to start using it for some our on-prem mailboxes. Hybrid Graph API only supports delegated authentication flows and not application authentication flows. Just because something isn’t “supported” doesn’t mean you can’t make it work! There are two things that we’ll need to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[64,69,99,65],"tags":[24,35,186,45,185,106],"class_list":["post-782","post","type-post","status-publish","format-standard","hentry","category-active-directory","category-exchange","category-o365","category-security","tag-active-directory","tag-api","tag-client-credentials","tag-exchange","tag-graph","tag-hybrid"],"_links":{"self":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/782","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=782"}],"version-history":[{"count":11,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/782\/revisions"}],"predecessor-version":[{"id":800,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/782\/revisions\/800"}],"wp:attachment":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=782"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=782"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}