Answered

Bug: Environment admin centre not giving access to one environment

(0) Share

Report

Posted on by Meneghino

6,949

Hello, I wanted to delete an environment, but I am not able to access it via the environment admin page, as you can see from the screenshot below. It is the first environment on the list, and clicking on it does not do anything, whereas all is fine for the other environments.

It is bizzarre as the loading icon before the name is not moving, and the environment is not located where it should be, in Europe.

Any ideas?

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (1)

Sort by

v-monli-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

Have your tried:

1. test with other browsers?

2. test with another admin in your environment?

3. test with another pc?

If the issue still persists after all these, please feel free to get back.

Regards,

Mona

Was this reply helpful? Yes No
Meneghino 6,949 on at

Like (0)

Report
Copy link

Link copied!

Hi @v-monli-msft

1. Yes (Chrome, Edge, Explorer)
2. I am the only admin
3. Yes, same problem.

The issue persists.

Many thanks.

Was this reply helpful? Yes No
Verified answer

v-monli-msft Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi,

About the stuck behavior when you click on it, I think this is because that this environment is created before the GA. I have a few similar ones too:

See the detailed information here:

https://powerapps.microsoft.com/en-us/blog/powerapps-environments/

"Two weeks after PowerApps enters general availability (GA), environments containing preview content will be marked as read-only (with the exception of the default environment); all existing apps & flows will continue to work in these environments, but you will not be able to create new apps or flows. We highly recommend that users of these environments migrate their content to the default environment or another custom environment."

But since you cannot access the environment, you cannot migrate the content now. I have reported this to the product team. I will update you once I got further information.

Regards,

Mona

Was this reply helpful? Yes No
Meneghino 6,949 on at

Like (0)

Report
Copy link

Link copied!

Thank you @v-monli-msft
Actually I have access to the environment in that I can choose it in PowerApps Studio for example, but I cannot administer it.
All I want to do is to delete it.

Was this reply helpful? Yes No
davidme Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

[Edit 3/14/17 08:21 PDT] We have an internal repro of this issue now... looking into it.

Hi there @Meneghino,

These environments with user's names in them similar to "Giacomo's Environment" are what we refer to as "Legacy-CDS" (preview) environments. These were created automatically in October when we introduced environments for each CDS database that was provisioned in your tenant. The user who owned the database should have been set as the administrator for the legacy-cds environment. For the environment that you are trying to delete, is that you or some other user in the tenant?

Note that we didn't remove the permissions from these "legacy-cds" environments, but we did for the "(From Preview)" primary legacy preview environment for your tenant (only applies to tenants outside the USA).

Aside from an environment admin, the global tenant administrators for your AAD tenant should also have permission to log in to the admin portal and delete the environment.

WIth this information, if you feel there is still a product issue here, can you please reply with the ID of your environment or at least your tenant domain or tenantId so that we can take a look at the permissions on it?

Thanks!
-David Messner

Was this reply helpful? Yes No
Meneghino 6,949 on at

Like (0)

Report
Copy link

Link copied!

Hello @davidme
For the environment that I am trying to delete I am the administrator.
When you mentioned environment ID I had a brainwave and just bypassed the main environment page by directly placing this link in the browser in order to bypass the main admin page:
https://admin.powerapps.com/environments/Legacy-df27ff76-bce4-4a04-aa4f-27c2317f903a/security
This worked and I have now deleted the environment, so there is no issue with permissions.
I suspect it is a bug on the main environments page as described in my first post and as confirmed by @v-monli-msft

Was this reply helpful? Yes No