Announcements
We are automating some steps in dynamics 365 using Power Automate, when testing some flows we noticed some employees are suddenly receiving an "Tenant xxx-xxx-xxx is not allowed to use the test environment" error. Anyone know how to fix this issue because i cannot find any information related to this issue.
We are getting this error for users that are trying to use an On-demand flow in Production. I shared the flow with these users last week and we are attempting to find more information on the error as we have not encountered this before.
We have this error in sandbox and production, but not for all users that's the odd thing. We allready tried a couple of things but it seems user related. Hope this will get fixed soon.
We have this also, users with identical permissions and licenses some of which can run the flow and some of which get the same error as in the screen shot.
Any luck in solving this issue? I have the same for test-users in a sandbox environment. I reproduced the issue with a test-user account and tried to solve it or atleast find an indication of the issue. No luck
Not yet, I got it working on an test user by removing and adding them again at the 'run only users' but repeating these steps with an real user it didn't work. I created an ticket at Microsoft, hoping to get this resolved asap.
I created a ticket with Microsoft also, I shared with them the link to this forum as I see the issue is now growing in the last 24 Hours to get higher priority attention on global issue.
I was having this issue when users tried to link a project to a roadmap in the project web app.
I somehow was able to solve it just by having the users login in the power automate web. I guess that created a workspace for them and then they were able to use the app normally.
I just was on call with Microsoft Support when you posted this message. After the call with MS I needed to extract some information from power automate from an user were the problem was active. After opening Power Automate with this users credentials the problem indeed disappeared. So we have an work-around now to get this fixed for users were the problem is active it seems.
I send the information they requred and an additional note that the problem seems to be fixed after login to power automate once.
We also get the same error for some users in our team. I am actually only an end users on the App. What I picked up from our side is users with the issues are users that were loaded in the past 6 months on the system.
On your work-around for the users to open Power Automate and then it will work. I tested it this morning but sadly this is not working or maybe I am doing this wrong. I requested the user to log in to his MS account and then select Apps and then open the Power Automate on his side. It requested him to log in with his email. Once done on the right hand side it open in the Enviorments - Personal Productivity. Is that correct or must this enviorment link to the business where the App is hosted on.
Any help in this is welcome.
I haven't really done any further research on this, but yes, most likely the user needs to sign in to the environment the app is hosted in.
You can easily switch environments by clicking the env name on the top right corner of the screen when in the Power Automate page (https://make.powerautomate.com/)
Lmk if you solve it, I might be able to help
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.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 551
WarrenBelz 430 Most Valuable Professional
Valantis 298
