Skip to main content

Notifications

Power Automate - Using Connectors
Unanswered

please include /contacts path in Office 365 Outlook connector send a HTTP request

(0) ShareShare
ReportReport
Posted on by 11

Hi,

 

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

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,422

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,711

Leaderboard

Featured topics