Share
Report
11Hi,
Currently 2nd level /contacts path of graph API is forbidden for Office 365 Outlook connector send a HTTP request action. But contacts CRUD is the responsibility of this connector. I want to put an extension attribute to a contact and it requires premium HTTP with Azure AD connector, when messages, events, tasks - don't. Is there any security or functional reason behind blocking /contacts path in the http request action of Office 365 Outlook, or is it a simple overlook of contacts resources that are clearly responsibility of this connector? Can it be reconsidered by the responsible product team?
Kind regards,
Tomasz Szalaj
Categories:
I have the same question (0)
All responses (
Answers (
