Tag / Power Platform

an anime character who has a slight beard and no hair, he is slim. He is happy because he has just solved the problem. The character is detailed and they are sat in a corner office. Behind the is a city scape scene.
by Simon Doy

Power Platform Error: Office 365 Connector – List Group Members Fails with Request_ResourceNotFound


This article details the findings of an investigation into a problem that we had with a Power Platform, Power Apps based solution. The reason for the issue is that this organisation needs to be more secure than most.

The organisation operates under numerous compliance and regulatory standards and the application that was built helped them implement one of their compliance based business process .
This solution happened to be one of the first solutions we rolled out. We hit an issue that we had not seen before. Looking around the Internet, it seemed that neither had many others. So, I want to document it and share what we saw so that others can get up and running faster than we did!
As they say, “Sharing Is caring!”

The issue was that a Power App was using the Office 365 Connector to List Group Members and it was failing with the following error:
Office365Groups.ListGroupMembers failed: { “error”: { “code”: “Request_ResourceNotFound”, “message”: “Resource ’33cd8c47-a8dc-XXXX-XXXX-a2a699b80f66′ does not exist or one of its queried reference-property objects are not present.”, “innerError”: { “date”: “2025-01-03T13:55:43”, “request-id”: “e0d458b3-0292-4624-96dc-10a4cccbe4ec”, “client-request-id”: “e0d458b3-0292-4624-96dc-10a4cccbe4ec” } } }

Checking the resource object id, which was for a user, they certainly did exist! Ultimately it was this that led us to the solution which I will detail below.

The code is shown below:

 
Investigation

We quickly realised that it was down to some sort of permission. One of the problems with troubleshooting is you do second guess yourself and we started to wonder if the problem was down to the users not being a member of a group. Well, one of the things that we need to mention is that the member of the group, was a Microsoft Entra ID Security Group. There are various settings which we checked but they never seemed to be the right problem.

The main issue we had is that we have a iThink 365 Development tenant with Power Platform Development environment and we could not recreate the problem.

Another thing to mention is that if a user was a SharePoint Administrator with a Microsoft Entra ID Role then the problem did not occur. We proved this by giving one of the users who we trusted that right and everything worked beautifully.

Anyway, after a couple of days of investigation between the teams I spent some time looking through all the Microsoft Entra ID policies and settings. I found the following Microsoft article: https://learn.microsoft.com/en-us/entra/fundamentals/users-default-permissions.
One of the settings mentioned is “Read Other Users” which has the following description:

This setting is available in Microsoft Graph and PowerShell only. Setting this flag to $false prevents all nonadmins from reading user information from the directory. This flag might prevent reading user information in other Microsoft services like Microsoft Teams.
This setting is meant for special circumstances, so we don’t recommend setting the flag to $false.

The article did not explain how to make the change but after some searching an article was found which uses the Entra ID PowerShell module

The two commands that we used were:
Get Authorization Policy
This is used to get the authorization policy to see if the read other user permission was set to false.
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.entra/get-entraauthorizationpolicy?view=entra-powershell

Set Authorization Policy
This is used to set the authorization policy to set the read other user permission to true.
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.entra/set-entraauthorizationpolicy?view=entra-powershell

In turned out that the read other users permission was set to false!
Hurrah if we found something that could well be the problem, such a relief.. now to see if worked.

After a discussion with CTO and CIO who then mentioned some other issues that they were seeing ended up being related to this same setting. We got permission to make the change.


How long does the setting take to be applied?


One of the things that we were not sure of was, how long would the setting take to filter through the users.
Funnily enough it seemed to happen very quickly and when one of the users accessed the Power App it worked first time! So, to be safe give your users about 30 minutes for the change to take effect.

Conclusion


In this article I explained an issue we had with the Office 365 Group Connector which was reading the group membership and the users in the group. The Power App connector was failing.
This article explains how to fix the issue by setting the ReadOtherUser property to true. This is the default setting applied to accounts and it is unusual for the setting to be set to false.

I hope, not that if you are reading this and have this problem, this article will help you quickly resolve it! 😊

by Simon Doy

Manage and deliver your 90-Day Action Coach Success Plan with Microsoft 365 – Part Two


Introduction

If you are working with an Action Coach Business Coach like Iain Strachan as I am you will be used to the 90-day strategy planning session.

In these 90-day planning sessions, we define 4 Goals which are 3 business goals and one personal goal and build a plan on how to achieve those goals over the next 90 days.

This is the second post in a series on how you manage, track and deliver your 90 day Action Coach Success Plan, if you have not read the first post, then start there.

Viva Goals – The Key To Tracking Your Goals and Metrics

Viva Goals is part of the Microsoft Viva suite, allowing businesses to define objectives and key results. These OKRS are goals that are measured using key results to track your progress and define when the objective has been met.

You can access Viva Goals through the web address, https://goals.cloud.microsoft/.

Business leaders need to be able to bring their teams on the journey with them and have a way to communicate and track the progress of business strategy initiatives. Viva Goals is a great way to achieve this.

With Viva Goals, you keep the progress of your OKRs up to date by you and your teams checking in.

The frequency of check-in is configurable but to keep in line with Action Coach success pack delivery you would check in once a week to update your goals progress.

However, one of the challenges with OKRs is the process of keeping the data up to date and correct.

First of all you can start manually entering the stats you are measuring but you really want to make sure that it is easy to update, track and monitor.

With the initial version of Viva Goals, there were some integrations that allowed the check-ins to take place automatically but they were a little limited.

Fast forward to today and now the options are much more interesting and there are two integrations that we will focus on today.

The Viva Goals team have enabled Power BI, Planner and Project for the web integration. The Power BI integration is really a game changer because through Power BI we can integrate with a huge number of different data sources automatically by linking Power BI visualisations to the Viva Goals key result.

The important aspect of Power BI is that you create the Power BI with the visualisations which display the metrics that we wish to measure. These measurements are key to when you are building your 90 strategy plan, in your workshop you will be asked how you would measure the goal and track whether it has been achieved.

There are a couple of options for how you would track these metrics, you can manually track them but if you really want to automate and track these metrics then you should look at ways to pull this data from your business systems.

An example might be the net profit margin figure which you could manually enter which is fine, however, if you want to make life easier then you can automate it by pulling from Xero into Power BI through some integration.

When businesses are looking to achieve their goals there is often activities that need to be planned and tracked. Traditionally with the Action Coach this is done via a Microsoft Excel spreadsheet which is fine but often I would find that keeping in mind what the activities are and what was to do this week would require me to keep checking on the Excel spreadsheet.

However, with Viva Goals and Planner integration, it is possible to make the activities that go along with the goal part of your key result that supports the objectives.

You can create an initiative and then link that initiative to Planner. In the previous section, we talked about how we create a bucket for each objective/goal and using an initiative we can link the objective to that bucket in Planner and see the progress of the tasks that are taking place.

Let’s delve into how we might set this all up, via this video.

How do you get your data into Power BI?

Well this is the key to it all.

When you start, I suggest keeping it simple and tracking your key results metrics manually. As you build your capability you can start to look to automate it as shown in the video.

Of course, we at iThink 365, would love to help you get your data, Power BI, Viva Goals and Planner setup and give you something that you can then maintain and enhance.

Conclusion

By combining these Microsoft 365 services together, you can build a really powerful and excellent tool that will help you manage, track and deliver your 90-day plan.

I wish you good luck with your 90-day planning!

Let us know if this helped you and reach out if we can help you!