Tenant xxx-xxx-xxx is not allowed to use the test environment

[Schloesser]

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.

[je-sendra-dymsa]

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

[MKeppel]

Can confirm. I had user just log into https://powerautomate.microsoft.com/en-nz/ and the flow worked for them.

[Kevin_Stocky]

Hi everyone,

I am getting the same issue but in my case the system is only used by Guest Users.

Anyone has an idea how the workaround could work in that case ? Because l can't get the Guest users to log in the Power Automate platform of the Tenant which present the issue....

I have been digging the issue for hours now and nothing seems to work.

[Togusa]

We're getting the same error on random users and I've found a possible fix or temporary workaround.

I'll try to add more background information first.

We developed a new Solution, with Dataverse tables and a model-driven App and a few PA flows.

After some initial testing on the Production environment, where everything worked just fine, we dicided to create a Test Environment and migrate (export from main + import in test) the Solution to this environment for further development, where we made some changes and more testing.

Then we exported the Solution from the Test environment and updated the Production solution with it.

After this operation, we started having the abovementioned "not allowed to use the test environment" problem.

My temporary workaround or fix was to:

- in the Production environment, delete all the "Dataverse" or "Dataverse (legacy)" connections used by the flows from PowerAutomate (not from PowerApps)

- open and edit each flow, from PowerAutomate again

- upon entering the edit interface, I'm immediately prompted to re-authenticate for the missing connections

- then, simply save the flow once it's open for editing

Doing this solved the issue for us.

It seems that when we updated the flow from an environment to the other, the Dataverse connections in the flows still "pointed" to the dataverse tables in the test environment instead of the production one.

UPDATE: Even though this solution seemed to fix the problem at first, it seems that other users still had it.
I've found another workaround... but it's harder to implement.
You need the user reporting the error to open PowerAutomate, go to Data\Connections and "Add a new connection" to Dataverse (the standard one, not legacy) and confirm the login.

Once the new connection to Dataverse is listed among the other connections, the problem should have gone away.

UPDATE 2: Now it seems that by simply opening PowerAutomate with the user reporting the problem (if said user have never opened PA before), without creating any new connections, is fixing the problem.

This is beyond absurd if you ask me...

[Djufair]

Hi

Tenant [xxx]  is not allowed to use the test environment. popped up on my side as well.

Really weird

Can you please look into this

Djufari

[Kevin_Stocky]

Hi ya'll,

I escalated to Microsoft as well but for now the product team has no strong fix. Espacially in my scenario with only Guest Users working in this environment...

My workaround : changed all my triggers by the dataverse "When an action is performed" (which is not in Preview). I have created a Catalog and an dataverse Action for each of my flow. Then I am calling the actions in my BPFs instaed of calling directly the Cloud flows.

It seems to work like a charm and I am less scared of the connection/loggin issue reappearing. 

[FuzzyPinny]

Thank you, I seen your comment about logging the affected user into Power Automate, this solved my problem

[BeheerderLani]

We are having the same problem with this issue. Is Microsoft working on a fix?

[Kevin_Stocky]

The answer I have received from MS support is that product group had planned a roll out on March 3rd, 2023. I don't know if that will be the case.

As my fix work fine I think it will remain for the long haul...

[AJVenter_1234]

Good day everyone.  Any news on an fix for the issues of running flows.  Will Microsoft release it if they do on their website.  From my side we tried the work a round but not working for us.  Thank you all