{"id":110745,"date":"2016-10-31T12:51:41","date_gmt":"2016-10-31T19:51:41","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/intro-flow-admin-center\/"},"modified":"2016-10-31T12:51:41","modified_gmt":"2016-10-31T19:51:41","slug":"intro-flow-admin-center","status":"publish","type":"power-automate","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/intro-flow-admin-center\/","title":{"rendered":"Introducing Microsoft Flow Admin Center"},"content":{"rendered":"

Last week, we introduced environments for Microsoft Flow. In case you missed it, you can catch up by reading this blog post<\/a>. With the General Availability of Microsoft Flow, we are also introducing a brand\u00a0new admin center experience.<\/p>\n

The Microsoft Flow Admin Center, (https:\/\/admin.flow.microsoft.com<\/a>) allows you to create environments, manage permissions and set up Data Loss Prevention (DLP) policies, if you have admin privileges to an environment and a Microsoft Flow Plan 2. You can also find a link to the Flow admin center in the setting menu in the Flow portal. When you use the Microsoft Flow Admin Center, environments and policies that you create will also impact Microsoft PowerApps.<\/p>\n

\"\"<\/p>\n

Creating a new environment<\/h2>\n

Environments provide data locality, an isolation boundary for all resources, and the ability to create data loss prevention policies. Creating a new environment is easy, click on the \u201c+ New Environment\u201d in the top right corner of the Admin Center. In the wizard, choose a name and region for your environment. Remember, all the resources created in each environment will be geo-located to the region where your environment was created. This can NOT be changed later.<\/p>\n

\"\"<\/p>\n

When creating environments be sure to be aware of the limitations of environments — since they are an isolation boundary you can never reference different resources across environments. For example, you can only access the Common Data Service from the same environment as where the database is. As a result, be sure to create environments only where you need them.<\/p>\n

Managing environment permissions<\/h2>\n

Administrators have control over who can administrate, and create new content inside of environments, as well as who have access to the Database.<\/p>\n

\"\"<\/p>\n

Environments have two built-in roles that provide access to permissions within an environment. You can configure these roles on the Security<\/strong> tab when you select an environment.<\/p>\n

    \n
  1. Environment Admin<\/strong> role can perform all administrative actions on an environment including the following:\n