You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/administrator/environments-administration.md
+5-11Lines changed: 5 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ manager: kvivek
6
6
ms.service: powerapps
7
7
ms.component: pa-admin
8
8
ms.topic: conceptual
9
-
ms.date: 07/30/2018
9
+
ms.date: 08/15/2018
10
10
ms.author: manasma
11
11
---
12
12
@@ -174,7 +174,7 @@ Each user can provision databases in two Trial environments and two Production e
174
174
PowerApps Plan 2. See [PowerApps pricing page][3] for details on all the plans that include this license.
175
175
176
176
### While trying to create a new environment, I am getting an error. How should I resolve it?
177
-
If you are getting the following error message: "Either your plan doesn’t support the environment type selected or you’ve reached the limit for that type of environment.", it can mean one of the two things
177
+
If you are getting the following error message: "Either your plan doesn’t support the environment type selected or you’ve reached the limit for that type of environment.", it can mean one of the two things:
178
178
179
179
1. You have already utilized your quota to create a specific type of environments. Say you were creating a Trial environment and you get this error message. That means, that you have already provisioned two Trial environments. You can view all the environments in [PowerApps admin center][1].
180
180
If you want, you can delete an existing environment of that specific type and create a new one. But, please make sure that you don't lose your data, apps, flows and other resources which you want to retain.
@@ -186,14 +186,8 @@ If you are getting any other error message or have more questions, please connec
186
186
### While trying to create a database in an environment, I am getting an error. How should I resolve it?
187
187
In following scenarios, you can get an error while trying to create a database:
188
188
189
-
1.**Default environment**: Creating a database is currently not supported in a default environment of the tenant.
190
-
191
-
2.**Environment for an individual use**: You get an environment for your individual use, by signing-up from the PowerApps Community Plan. If you have not created the database yet, then currently you can't provision a database in the environment for individual use.
192
-
193
-
3.**Environment in a different region, than your AAD tenant's home region**: Currently, you can only provision a database in the environments created in your Azure Active Directory Tenant home region. Ability to provision a database in the other regions, will be coming soon. So, make sure to keep the region same as tenant's default ___location, if you want to create a database in it.
194
-
195
-
4.**Creating databases not supported in certain regions**: There are certain regions, where creating databases is still not available. e.g. countries in South America. So, if your tenant's home ___location is South America, you currently can't provision a database in any environment.
196
-
189
+
**Default environment**: Creating a database is currently not supported in a default environment of the tenant.
190
+
197
191
We are working on enabling all of the above scenarios.
198
192
If you are getting any other error message or have more questions, please connect with us [here][5]
199
193
@@ -220,4 +214,4 @@ Yes, the ability to view the apps and flows for an environment is available from
Copy file name to clipboardExpand all lines: powerapps-docs/administrator/powerapps-powershell.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -126,8 +126,9 @@ To perform the administration operations in the admin cmdlets, you'll need the f
126
126
| Version | Date | Updates |
127
127
| --- | --- | --- |
128
128
| 1.0 | 04/23/2018 | <ol> <li> Initial launch of the PowerApps cmdlets for app creators (preview) including management cmdlets for Environments, Apps, Flows, Flow approvals, Connections, and Custom Connectors </li> <li> Initial launch of the PowerApps cmdlets for administrators (preview) including administrative cmdlets for Environments, Apps, and Flows </li></ol>|
129
-
| 2.0 | 05/24/2018 | <ol> <li> Minor bug fixes in both the cmdlets for app creators and administators </li> <li> Added the following new administrative cmdlets: <br> Get-AdminConnection <br> Remove-AdminConnection <br> Get-AdminConnectionRoleAssignment <br> Set-AdminConnectionRoleAssignment <br>Remove-AdminConnectionRoleAssignment <br>Get-AdminConnector <br>Remove-AdminConnector <br>Set-AdminConnectorRoleAssignment <br>Get-AdminConnectorRoleAssignment <br>Remove-AdminConnectorRoleAssignment <br>Get-AdminPowerAppsUserDetails <br>Get-AdminFlowUserDetails <br>Remove-AdminFlowUserDetails <br>Get-AdminApiPolicy <br>Add-AdminApiPolicy <br>Remove-AdminApiPolicy <br>Set-AdminApiPolicy <br>Add-ConnectorToBusinessDataGroup <br>Remove-ConnectorFromBusinessDataGroup </li> </ol>
130
-
| 3.0 | 07/30/2018 | <ol> <li> Added the ability to pass-in credentials to the Add-PowerAppsAccount (to enable recurring scripting) </li> <li> Minor bug fixes in both the cmdlets for app creators and administators </li> <li> Added the "PowerApp" or "Flow" prefix to each cmdlet for app creators </li> <li> Added the "AdminPowerApp" or "AdminFlow" prefix to each cmdlet for administrators </li> <li> Added the following new administrative cmdlets: <br> New-AdminPowerAppEnvironment <br> Set-AdminPowerAppEnvironmentDisplayName <br> New-AdminPowerAppCdsDatabase <br> Get-AdminPowerAppCdsDatabaseLanguages <br> Get-AdminPowerAppCdsDatabaseCurrencies <br> Get-AdminPowerAppEnvironmentLocations <br> Get-AdminPowerAppConnectionReferences <br> Set-AdminPowerAppAsFeatured <br> Clear-AdminPowerAppAsFeatured <br> Set-AdminPowerAppAsHero <br> Clear-AdminPowerAppAsHero <br> Set-AdminPowerAppApisToBypassConsent <br> Clear-AdminPowerAppApisToBypassConsent <br> Remove-AdminFlowApprovals </li></ol>
129
+
| 2.0 | 05/24/2018 | <ol> <li> Minor bug fixes in both the cmdlets for app creators and administrators </li> <li> Added the following new administrative cmdlets: <br> Get-AdminConnection <br> Remove-AdminConnection <br> Get-AdminConnectionRoleAssignment <br> Set-AdminConnectionRoleAssignment <br>Remove-AdminConnectionRoleAssignment <br>Get-AdminConnector <br>Remove-AdminConnector <br>Set-AdminConnectorRoleAssignment <br>Get-AdminConnectorRoleAssignment <br>Remove-AdminConnectorRoleAssignment <br>Get-AdminPowerAppsUserDetails <br>Get-AdminFlowUserDetails <br>Remove-AdminFlowUserDetails <br>Get-AdminApiPolicy <br>Add-AdminApiPolicy <br>Remove-AdminApiPolicy <br>Set-AdminApiPolicy <br>Add-ConnectorToBusinessDataGroup <br>Remove-ConnectorFromBusinessDataGroup </li> </ol>
130
+
| 3.0 | 07/30/2018 | <ol> <li> Added the ability to pass-in credentials to the Add-PowerAppsAccount (to enable recurring scripting) </li> <li> Minor bug fixes in both the cmdlets for app creators and administrators </li> <li> Added the "PowerApp" or "Flow" prefix to each cmdlet for app creators </li> <li> Added the "AdminPowerApp" or "AdminFlow" prefix to each cmdlet for administrators </li> <li> Added the following new administrative cmdlets: <br> New-AdminPowerAppEnvironment <br> Set-AdminPowerAppEnvironmentDisplayName <br> New-AdminPowerAppCdsDatabase <br> Get-AdminPowerAppCdsDatabaseLanguages <br> Get-AdminPowerAppCdsDatabaseCurrencies <br> Get-AdminPowerAppEnvironmentLocations <br> Get-AdminPowerAppConnectionReferences <br> Set-AdminPowerAppAsFeatured <br> Clear-AdminPowerAppAsFeatured <br> Set-AdminPowerAppAsHero <br> Clear-AdminPowerAppAsHero <br> Set-AdminPowerAppApisToBypassConsent <br> Clear-AdminPowerAppApisToBypassConsent <br> Remove-AdminFlowApprovals </li></ol>
131
+
| 4.0 | 08/15/2018 | Added an optional parameter to the New-AdminPowerAppCdsDatabase to make the function synchronous, by default (i.e. it will not return until the database is successfully provisioned)
0 commit comments