Unanswered

Advice re: Which API e.g. Graph or Office365Users etc

(0) Share

Report

Posted on by Sandecker

Is someone able to provide some guidance please in relation to the correct API's to be using in Power Apps? I have some test apps using the built in connectors such as Office365Groups and Office365Users. I also have an app using a custom connector wth MS Graph and have downloaded one of the sample app templates for "Book a Room" which uses items like Office365.GetRoomsInRoomList and Office365.FindMeetingTimes.

I'm wanting to do the right thing in relation to not using 'the old way' of doing things

I did read that EWS using SOAP was depricated / being phased out and that REST via the Graph API was preferred.

I'm assuming that connectors / APIs like Office365Groups and Office365Users are here to stay?
Should I try and just use these built in connectors before using a custom connector with the Graph API?
Is the Office365.GetRoomsInRoomList type of API using EWS? still being used?
Should I start using the Graph API for everthing and not the Office365Groups and Office365Users ones?
I did see somewhere someone putting the graph explorer string in with Office365Users and httpRequest so is the way we should be going?

Hopefully the context of how I've described things is correct 🙂

Many thanks for any advice.

regards

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

HamidBee 932 Super User 2024 Season 1 on at

Like (1)

Report

The Microsoft Graph API is the recommended way to access Office 365 data, including data related to groups, users, and meetings. The built-in connectors like Office365Groups and Office365Users use the Microsoft Graph API under the hood, but they provide a simplified, pre-built set of actions that you can use in Power Apps.
The Office365.GetRoomsInRoomList and Office365.FindMeetingTimes actions you mentioned are built on top of the Microsoft Graph API and are still supported, but you may find that the Microsoft Graph API offers more capabilities and flexibility than these built-in actions.

If you're building a new app or need to access data that isn't available through the built-in connectors, then using the Microsoft Graph API directly is recommended. It's a RESTful API and you can use the Graph Explorer to test different queries and see what data is available.

The custom connector approach using MS Graph and httpRequest is also a good option if you need more control over the data being returned or if you need to access data that is not available through the built-in connectors.
In summary, it's good to use the built-in connectors if they meet your needs, but if you need more control and flexibility, the Graph API is the recommended way to access Office 365 data. And you can use the Graph Explorer to test different queries and see what data is available.

If my reply helped you, please give a 👍, & if it solved your issue, please 👍& Accept it as the Solution to help other community members find it more.

Was this reply helpful? Yes No
Sandecker 7 on at

Like (0)

Report

Thank you very much for that - that's definitely helped 🙂 - now I can carry on with with my app with confidence.

Was this reply helpful? Yes No