When you upgrade to the latest Dynatrace, you might want to prevent your users from using the classic Dynatrace apps. In this guide, you learn how to set up policies to block users from opening classic apps.
You need account admin permission to perform the following steps.
We use the IAM policies and policy boundaries to limit the access for certain users.
First, you need to create a boundary that limits user access, so users can only open the latest Dynatrace apps.
Go to Account Management.
If you have more than one account, select the account you want to manage.
Go to Identity & access management > Policy management.
Select the Boundaries tab.
Select Create boundary.
On the Policy boundary page, define the boundary.
Boundary name: enter a useful name, such as only latest Dynatrace
Boundary query: use the following:
shared:app-id not startsWith "dynatrace.classic";
Example:

Select Save.
In the next step, we will update the group whose members should not be able to access classic apps.
In Account Management, go to Identity & access management > Group management.
Find your group.
In that row, open the menu and select View group to edit the permissions of a group.
Select Permission and define the permission.
ALLOW app-engine:apps:run;.only latest Dynatrace).Select Save.
Example:

Dynatrace classic runs on the live subdomain (for example, playground.live.dynatrace.com). We can restrict access to this domain by applying the following steps.
Any permission of type ROLE
Any permission of type POLICY that contains a policy statement with ALLOW environment:roles*
Note down all applied policies.
environment:roles.