For organizations that use the standard dev, test, production environment method, would you recommend each of those environment types to be production?
Great video as always. I have a somewhat unrelated question, for virtual connectors for dataverse, are those compatible with PowerApps/Dataverse for Teams?
I think it should be noted that you cannot change the Environment URL of a Dev Environment, or so I found via a Community post. What I don't yet understand, is why I cannot change the Environment URL for an Environment I just created with it saying that Environment URL is already in use...
With Prod and UAT environments; would users just to need be members of the security group assigned to the environment, to run apps shared with them in the environment? In reality, would they also need Basic User role, to be able access, say backend data sources (SharePoint, SQL Server etc) , if these resources are referenced in environment variables, with both definitions and values stored in Dataverse?
Dev is now an environment type you can choose for developing apps. You can run them here as well as long as they're just for testing. There's a big "Not for Production" banner going across. You can build here though and move to a different environment. The nice thing about dev environments is there's no cost behind them and you can use premium connectors without a charge while you're working. There's also no cost behind Dataverse there.
Hello PW, if i license 40 people with per-app power app licence (app should use dataverse) . The app was built in the traditional Default aka P.P. Environment, How much Dataverse storage will be allowed? Will i have to create a solution and move it to say a new PROD environment? does the prod environment allow full dataverse capabilities?
Each per app license gives you 50MB of Dataverse space allocated to the overall tenant, regardless of the environment. Ideally, yes, you should move those critical apps out of the default environment and into a prod environment though but that's a separate reason. -Brian
Waiting for your next video on the CoE toolkit,Brian! 🙌🏻
You bet! I have to wrap up the DLP one Friday and then COE is next week.
- Brian
@@PragmaticWorks thanks Brian ❤️
@@PragmaticWorks Does this video exist? I just scrolled through every video posted on the Channel and could not find it.
For organizations that use the standard dev, test, production environment method, would you recommend each of those environment types to be production?
Great video as always. I have a somewhat unrelated question, for virtual connectors for dataverse, are those compatible with PowerApps/Dataverse for Teams?
I think it should be noted that you cannot change the Environment URL of a Dev Environment, or so I found via a Community post.
What I don't yet understand, is why I cannot change the Environment URL for an Environment I just created with it saying that Environment URL is already in use...
With Prod and UAT environments; would users just to need be members of the security group assigned to the environment, to run apps shared with them in the environment? In reality, would they also need Basic User role, to be able access, say backend data sources (SharePoint, SQL Server etc) , if these resources are referenced in environment variables, with both definitions and values stored in Dataverse?
environment types matter? I am trying to create DEV, QA and PROD environments but not sure what type to use for DEV environment.
Dev is now an environment type you can choose for developing apps. You can run them here as well as long as they're just for testing. There's a big "Not for Production" banner going across. You can build here though and move to a different environment. The nice thing about dev environments is there's no cost behind them and you can use premium connectors without a charge while you're working. There's also no cost behind Dataverse there.
@@PragmaticWorks How about the test environment what type should that be ?
How does this work with PowerApps for Teams or does it?
Those Teams environments are more personal or small team by nature and don't kill your overall DV space. So you can be a little more siloed on those.
Hello PW, if i license 40 people with per-app power app licence (app should use dataverse) . The app was built in the traditional Default aka P.P. Environment, How much Dataverse storage will be allowed? Will i have to create a solution and move it to say a new PROD environment? does the prod environment allow full dataverse capabilities?
Each per app license gives you 50MB of Dataverse space allocated to the overall tenant, regardless of the environment. Ideally, yes, you should move those critical apps out of the default environment and into a prod environment though but that's a separate reason. -Brian
@@PragmaticWorks If Dataverse can host millions of Rows, what are this 50 mb used for?