Updates on provisioning database with Common Data Service for Apps

Till now, with the latest version of CDS for Apps, you could provision a database in a 'Trial' or a 'Production' environment but only if the environment was in the same region as your Azure Active Directory (AAD) tenant. In addition, you couldn’t provision a database in an individual environment (using the Community Plan). The good news is that we now support both of these scenarios:

·       Provision a database in an environment not in your tenant’s AAD home location

With PowerApps, you can create environments in various regions across the globe, which enable your business in these ways:

·       Store your data closer to your users.

·       Maintain the compliance requirement of your geography.

With the current release of CDS for Apps,  you can create a database for an environment in one region (for example, United States) even if the AAD tenant is in another region (for example, Canada or Europe). But there are caveats:

·       If an AAD tenant is in India, tax laws prevent you from creating a database for an environment in Australia. Conversely, you can’t create a database for an environment in India if the AAD tenant is in Australia.

·       You can’t provision a database for an environment in the United States First Release region, regardless of where the AAD tenant is.

·       Users in South America can now provision databases

If your AAD tenant is in South America, you can provision a database for an environment in any region except Preview (United States). Our backlog includes work to create a region for South America, but it’s not yet available.

·       Provision a database in an environment for individual use (using Community Plan)

If you sign up for the PowerApps Community Plan, you can provision a database in the individual environment that the plan provides.

Watch out for more updates on CDS for Apps.

Thanks,

CDS for Apps team