Types of Power Automate licenses
Organizations gain rights to use Power Automate via licenses (paid or trial) that are available either as standalone plans or as seeded plans.
Customers who need to create fully flexible, general-purpose workflows with either business process automation or Robotic Process Automation (RPA) capabilities, should consider purchasing standalone Power Automate licenses.
|Power Automate per user plan||This plan provides a user with rights to run an unlimited number of flows (within service limits) with the full capabilities of Power Automate, including standard connectors,premium connectors,business process flows, custom connectors,on-premises gateways based on their unique needs for a monthly fixed cost for each user.|
|Power Automate per user with attended RPA plan||This plan spans legacy and modern applications, allowing makers to create unlimited flows for API-based automation and automate legacy applications with desktop flows through Robotic Process Automation (RPA) and AI. This plan includes all Power Automate per user plan capabilities and the ability for users to run an attended RPA bot on their workstation. Additionally, this plan includes access to AI Builder capacity, supporting scenarios like forms processing, object detection, prediction, text classification, and recognition. This plan can be purchased for a monthly fixed cost for each user.|
|Power Automate per flow plan||With this plan, organizations can implement flows with reserved capacity that serve a team, a department, or an entire organization without having to license each user separately. This plan starts with a fixed monthly cost for five active flows.There is a monthly fee for each additional active flow (beyond the five flows that are included in the base fee).|
|Power Automate pay-as-you-go plan (preview)||With this plan, organizations can get started building flows without any license commitment or upfront costs and use their Azure subscription to pay only when their flows run.|
|Power Automate P1 and P2 plans (grand fathered)||These plans are no longer available for purchase nor via auto-renewal after December 31, 2020. Organizations with these plan licenses with renewals that are due on or after January 1, 2021 need to transition to either the Power Automate per user or per flow plan or to the Power Apps per user or per app plan to continue using the Microsoft Power Platform services. Customers with active contracts that started before January 1, 2021 with grandfathered licenses will continue to be supported until the contract end date. Contact your Microsoft account representative for more information or purchase licenses.|
Organizations also gain rights to use Power Automate if they are licensed to use any of the following plans where Power Automate licenses are seeded.
- Microsoft 365 (formerly Office 365).
- Dynamics 365 Enterprise.
- Dynamics 365 Professional.
- Dynamics 365 Team Member.
- Power Apps (Canvas and Model driven Apps)- Per App plans.
- Power Apps per user.
- Power Apps Plan 1 (grandfathered).
- Power Apps Plan 2 (grandfathered)
- Windows licenses.
When you use seeded plans, your flows must run within the context of the application in which the seeded plan is available. For example, flows included within a Dynamics 365/App created using Power Apps can connect to the following.
To any data source within the use rights of the Dynamics 365/App created using Power Apps.
Directly with the Dynamics 365/App created using Power Apps (via built in triggers/actions).
For example, if a flow uses premium connectors and it's triggered by an app, any user can run the flow if they have a Power Apps license.
If the flow is isolated and has nothing to do with the application, then a standalone Power Automate license must be purchased.
You can find more details can be found in Microsoft Power Apps and Power Automate Licensing Guide.
Compare Power Automate plans
Learn more about license entitlements.
Here's a chart that lays out the limits that are associated with the different license plans.
Dynamics 365 Sales Professional and Dynamics 365 Customer Service Professional.
Dynamics 365 Sales Enterprise, Dynamics 365 Customer Service Enterprise, Dynamics 365 Field Service, Dynamics 365 Project Service Automation, Dynamics 365 Retail, Dynamics 365 Talent, and Dynamics 365 Customer Engagement plan.
In Dataverse for Teams environments (included in select Office licenses) customers can use custom connectors built on Azure and Dataverse capabilities.
Connectors represent the app/service to which your flows connect. For example, OneDrive, SharePoint, Twitter, etc. are examples of services to which flows connect. The connectors in Power Automate are designed to speak the language of the apps/services to which your flows connect, as well as give Power Automate access to the account. Connectors are categorized as either standard or premium connectors.
Standard connectors are included in your standard Microsoft 365 subscription. We are continuously adding more standard connectors.
Premium connectors are not included in the Microsoft 365 license but included in all standalone plans.
Here's the full list of premium connectors in Power Automate.
Business process flows
You can create business process flows for a workflow to ensure that users enter data consistently and follow the same steps every time. Business process flows provide a streamlined user experience that leads people through the processes their organization has defined for interactions that need to be advanced to reach a conclusion.
You may want to communicate with apps/services that aren't available as prebuilt connectors. Custom connectors allow you to create (and even share) your own connectors.
Robotic Process Automation
What if I have an application that Power Automate doesn't have a connector for, and I can't create a custom connector because the app doesn't have an API? Robotic process automation (RPA) is perfect for scenarios such as this one. You can use RPA to create automation even in older systems that don't have an API. With RPA, you automate applications by teaching Power Automate to mimic the mouse movements and keyboard entries of a human user, as if a robot was using the computer. In other words, whereas digital process automation provides connectors so you can tell the application what to do, with RPA, you show it what to do.
On premises gateway
The on-premises data gateway acts as a bridge to provide quick and secure data transfer between on-premises data and several Microsoft cloud services. With gateways, organizations can keep databases and other data sources on-premises and securely use that on-premises data in cloud services.
AI Builder credits
With AI builder, you to add intelligence to your automated processes, predict outcomes, and help improve business performance. AI Builder capacity is expressed in the form of "service credits". Service credits serve as the single (common) currency across all the scenarios that AI Builder supports. Available service credits are deducted when AI Builder services are used. For instance, you could use these credits to extract data from a few documents with form processing or perform hundreds of basic OCR extractions with text recognition.
Different scenarios (for example, forms processing, prediction, etc.) consume service credits at different rates. Each per user with attended RPA license grants you 5000 credits, allowing you to assess the capabilities in AI Builder. Learn more about AI builder licensing.
Dataverse database and file capacity
Data volume continues to grow exponentially as businesses advance their digital transformation journey and bring data together across their organizations. Modern business applications need to support new business scenarios, manage new data types, and help organizations with the increasing complexity of compliance mandates. To support the growing needs of today's organizations, data storage solutions need to evolve continuously and provide the right solution to support expanding business needs. Microsoft Dataverse capacity storage is optimized for relational data (database), attachments (file), and audit logs (log). Power Automate standalone license customers receive a tenant-wide default entitlement for each of these three storage types. You can buy more storage in 1-GB increments. Learn more about Dataverse capacity storage.
Power Platform requests
To help ensure service levels, availability and quality, there are limits to the number of Power Platform requests users can make across all Power Platform products. Service limits are set against normal usage patterns in both five minute and per 24 hour intervals. Most customers will not exceed these limits.
The 24 hour limit is based on the per user or per flow license. If a user has a Power Automate per user plan, they can make 40,000 Power Platform requests across all of their flows in a tenant within a 24 hour period. This includes requests the platform makes to third party connectors too. The 24 hours is a sliding window, meaning that anytime a flow runs, the system looks at the requests in the past 24 hours to determine if the user is at their limit. Alternatively, if a flow has the per flow plan, the flow can make 250,000 Power Platform requests across all users of the flow in a 24 hour period. To prevent a usage-heavy flow or user from impacting other users, this capacity is tracked based on consumption at an individual user or flow level and it cannot be pooled at any other level like environment or tenant levels. For example, two users in a tenant may have per user licenses and each user gets 40,000 requests per 24 hour period. If the first person uses more than 40,000 requests 24 hour period, their flows will slow down and will not impact the second user who only used 20,000 requests and still has 20,000 requests remaining. Currently all customers are in a transition period so the transition period limits apply. After the transition period ends, the actual limits are applicable. Plan your flows based on actual limits.
The five minute limit is 100,000 requests and it is independent of a user's license. For example, flows with a per flow license can make 250,000 requests in 24 hours but they cannot make more than 100,000 requests within five minutes.
All customers are in a transition period. That means that enforcement isn't strict and limits are higher. The transition period ends after Power Platform admin center reports are generally available. Organizations will then have six months to analyze their usage and purchase licenses that are appropriate before strict enforcement on license limits begins.
Here are a few things of which to be aware during the transition period.
The transition period doesn't mean that there are no daily limits. It means that the currently enforced limits are more generous than the stated limits to prevent potential unintended impact on your apps or flows. See Requests limits and allocations to understand both plan limits and transition period limits.
These transition period limits are applied at the flow level during the transition period. Additionally, a separate per user level limit of 1,000,000 actions is applied during the transition period to ensure users do not go above 1M actions across all their flow runs in a day. After the transition period ends, the actual limits will be applied at user level for per user plans and flow level for per flow plans.
Since the limits are more generous during the transition period, stacking of user licenses isn't supported. If a user has multiple plans, such as a Microsoft 365 plan and a Dynamics 365 plan, the flow will use the higher plan (Dynamics 365 plan).
Power Platform requests capacity add-on packs are not assignable to users or flows during the transition period. However, Microsoft recommends that you purchase these add-ons to remain within your license terms and to be prepared for when the transition period ends. If your flows are currently being throttled, purchase add-ons and create a support ticket with the flow details and add-on details so that the support team can provide exceptions for your throttled flows.
Seeded license users can only use flows within the context of the app. See the seeded plans section to learn more. The enforcement on license limits is less strict during transition period and Microsoft recommends that you remain within your license terms to avoid any disruptions when the transition period ends.
Power Platform requests FAQs
Here are some of the frequently asked questions about limits, and their answers.
What counts as Power Platform request?
Based on license plan, there are limits to the number of actions a cloud flow can run in day. These limits are different from connector throttling limits. You can see the number of actions your flow runs by selecting Analytics from the flow details page and looking at the Actions tab.
Even when the flow uses fewer Power Platform requests, you can still reach your limits if the flow runs more frequently than you expect. For example, you might create a cloud flow that sends you a push notification whenever your manager sends you an email. That flow must run every time you get an email (from anyone) because the flow must check whether the email came from your manager. The limit applies to all runs across all your flows in a 24 hour period. Here are some guidelines to estimate the request usage of a flow.
One or more actions run as part of a flow run. A simple flow with one trigger and one action results in two "actions" each time the flow runs, consuming 2 requests.
Every trigger/action in the flow generates Power Platform requests. All kinds of actions like connector actions, HTTP actions, built-in actions (from initializing variables, creating scopes to a simple compose action) generate Power Platform requests. For example, a flow that connects SharePoint, Exchange, Twitter, and Dataverse, all those actions are counted towards Power Platform request limits.
Both succeeded and failed actions count towards these limits. Skipped actions are not counted towards these limits.
Each action generates one request. If the action is in an apply to each loop, it generates more Power Platform requests as the loop executes.
An action can have multiple expressions but it's counted as one API request.
Retries and additional requests from pagination count as action executions as well.
Consider the following flow where every email attachment is saved to OneDrive. The trigger consumes one Power Platform request, Apply to each consumes one request, and the actions within Apply to each consume multiple requests based on the number of times the loop runs. If there are four attachments, this section consumes eight Power Platform requests (4 x 2 actions). In total, this flow consumes 10 Power Platform requests.
Whose Power Platform request limits are used by the flow?
If a flow has per flow license, the flow will always use the per flow limits and not the creator/owner/invoking user's limits.
Automated and scheduled flows always use the flow creator/owner's Power Platform request limits regardless of who started the process or what accounts are used for connections inside of the process. For a solution flow, you can change the owner of the flow using Web API. After you change the owner, the new owner's API request limits are used. For a non-solution flow, the flow always uses the original creator's limits which can't be changed. If the original creator leaves the company, any co-owners of the flow can export and import the flow as a different owner. After you import the flow, it becomes a new flow and starts using limits from the new owner. Alternatively, you can assign a per flow license to the flow.
Instant flows (button, power apps, hybrid triggers) use the invoking user's limits.
If the flow owner is a service principal, the flow will use non licensed user limits.
If you share an automated/scheduled flow with another user and then that user triggers the same flow, it uses the limits of the original owner and not the new user's limits. But if the user then leverages the flow to make their own new flow, then that new user becomes the owner of the new flow and that flow uses the new user's limits.
If a parent flow calls a child flow, the child flow uses the parent flow's limits. For example, if the parent flow is an automated flow, the child flow uses the parent flow creator/owner's limits.
If the parent flow is a manual flow, the child flow uses the limits of the parent flow's invoking user.
If the child flow has a per flow license, it uses the per flow limits and not the parent flow's limits.
If a parent flow has a per flow license, the parent flow and all child flows use the per flow license.
During the transition period, there is a slight difference in this behavior. The child flow owner's license is used unless the child flow has a per flow license but once the transition period ends, the child flow owner's limits are ignored and only the parent flow owner's limits are used unless the child flow has a per flow license.
As a maker, what tools do I have to analyze my usage?
If you are experiencing delays or slowdowns when your flow runs, it's likely that you have exceeded the Power Automate limits for the day. For flows that are consistently delayed due to overages, users also receive a notification that informs them about these overages, along with tips and tricks on how to prevent delayed runs of their flows.
Here is an example of an email that was sent for a flow that was consistently exceeding action limits.
The Power Platform admin center contains reports on Power Automate requests. This reporting will help you to quickly view adoption and user metrics for your organization.
Additionally, you can see the action usage for a given flow by selecting the Analytics action from the flow properties page, and this works across all types of actions. This helps you to understand how many actions are running each day. It can help you understand usage patterns to optimize for capacity.
As an admin, what tools do I have to analyze my environment's usage?
The Power Platform admin center containsreports on Power Automate requests. These reports are currently in public preview. Admins have two reports available in the Power Platform admin center.
User report – This report displays the Power Platform request usage by every user in the environment, compared to their assigned limits.
Per flow report - This report displays the Power Platform request usage by every flow in the environment that has a per flow license.
Non-licensed user report - This report displays the Power Platform request usage for non-licensed users and the total entitlement for non-licensed users for that tenant. In future, power platform requests usage of flows running under service principal will be displayed in this report.
After the reports are generally available, users will have time to react and purchase higher licenses before enforcement begins.
What happens when my flow runs too many actions?
When you have a flow that runs many actions, it impacts the performance of your flow. You will see a banner on the flow if your flow is being throttled.
In the most common case, exceeding limits results in delayed runs of subsequent actions, and this will slow down the overall run time of your flow. These delays are proportional to the degree of overages caused by a flow.
Occasional overages are okay. For instance, if you exceed your daily limits by 500 actions it's not going to impact the performance of your flow, however exceeding your limit by 50,000 actions will have a significant performance impact on your flow potentially for multiple days.
What can I do if my flow is above limits?
Users won't be blocked from using an app or flow for occasional and reasonable overages.
Here are some things you can do if you've exceeded the limits of your license.
Revisit your design and check for any places that can help reduce the number of actions being called. Check out Best Practices section to create flows to use less actions.
If the flow is already optimized, but it uses many actions because of the nature of the business, consider buying a higher license. The per flow plan provides the best performance quota available (250K actions/24 hours/flow).
Turn on Pay-as-you-go for the environment to ensure none of the flows in the environment are throttled. Microsoft recommends this approach during the transition period.
Purchase the Power Apps and Power Automate capacity add-on for your organization. During the transition period, because enforcement is less strict, there is no facility to assign the Power Apps and Power Automate capacity add-on to a user or flow. However, Microsoft recommends that you purchase these add-ons now to remain within your license terms. Create a support ticket with the flow details and add on details to get temporary relief (30 days) from throttling. This temporary relief isn't available for flows that already have a per flow license assigned to them.
If a flow is consistently above the transition period limits for 14 consecutive days, Power Automate turns off the flow and sends a notification to the owner. You can purchase a higher license, and then turn it on anytime. You can edit and save the flow to reset the 14 day counter while you purchase the license.
What are connector limits and are they different from Power Platform request limits?
The connectors have separate limits as a service protection mechanism. For example, the SharePoint connector limits the number of actions at 600 per minute. A single SharePoint connection that's used across multiple flows can still only execute 600 operations per minute. Most connector pages have a throttling section that documents these limits. This limit is different from the request limits. For example, an Office user can run 6000 actions per day across all their flows but can still get throttled by the connector if they used more than 600 SharePoint actions in a minute despite not reaching the 6000 actions limit.
When a flow was throttled because it exceeded the connector limits, you might see a HTTP 429 (too many requests) error in your flow with error text like "Rate limit is exceeded. Try again in 27 seconds."
I am using COE Starter Kit , will the usage count towards my request limits?
Yes. Flows included in the COE Starter Kit also use limits from the owner. Microsoft recommends that you turn on Pay-as-you go for the environment or buy additional capacity and contact support to get temporary relief from throttling.
Can I use service principal in flows, and does it count against my request limits?
Yes, flows whose owner is a service principal will consume a separate quota called non-interactive limits. These limits are only applicable if the owner of the flow is a service principal. These limits are not applicable if the flow just uses a service principal in one of the actions.
Service principal flows running in context of D365 applications) listed in the table get 500,000 base requests + 5,000 requests accrued per USL up to 10,000,000 maximun pooled at the tenant level. If a tenant has 1000 D365 licenses, that tenant has a pool of 5,500,000 requests avaialble for all Power platform resources like Service principal flows, Dataverse requests etc per 24 hours. If a tenant has 2500 D365 licenses, that tenant has a pool of 10,000,000 requests avaialble for all Power platform resources like Service principal flows, Dataverse requests etc per 24 hours.
Premium service principal flows that are outside D365 app context will each need a per flow license. These flows get 250,000 requests per flow per 24 hours.
Standard service principal flows get 25,000 base requests with no per-license accrual for the tenant per 24 hours.
If you need additional requests, turn on Pay-as-you-go for the environment or buy additional power platform requests capacity.
Will desktop flows usage count consume my Power Platform request limits?
Only the desktop flow actions that are invoked from cloud flows count against the limit. Actions in the desktop flow are not counted towards request limits.
What happens to my Power Platform requests if I have multiple plans?
Since limits aren't strictly enforced during the transition period, stacking of user licenses isn't supported. If a user has multiple plans, such as a Microsoft 365 plan and a Dynamics 365 plan, the flow uses the higher plan (Dynamics 365 plan, in this example).
After the transition period ends, if a user has multiple plans assigned from different product lines, the total number of requests allowed would be the sum of the requests allocated to each license type. For example, if a user has both a Dynamics 365 Customer Service Enterprise license and a Power Apps per user license, then that user has a total of 40000 + 40000 = 80000 requests available per 24 hour period.
If a user has multiple licenses allocated within the same product line, for example if a user has a Dynamics 365 Customer Service Enterprise license as the base license and a Dynamics 365 Sales Enterprise license attached, the total number of requests would be the amount that the base license provides.
What are performance profiles and how do I know which performance profile my flow uses?
Microsoft 365 plans
Power Apps Plan 1, Power Apps Per App plans
Power Automate Plan 1
All license trials
Dynamics 365 Team Member
|Medium||Power Apps triggered flows, Power Apps Plan 2, Power Apps per user plan
Power Automate Plan 2, Power Automate per user, Power Automate per user with Attended RPA plans
Dynamics 365 Enterprise plans, Dynamics 365 Professional plans, Power Apps Plan 2, Power Apps per user plan
|High||Power Automate per flow plan|
Based on the license of the owner, a flow gets a performance profile which in turn decides the Power Platform request limits of the flow. If there are multiple licenses assigned to the owner, Power Automate picks the highest plan from the list.
|Performance profile||Limits during transition period||Limits after transition period|
In an organization, eight users have Office 365 licenses and their daily Power Platform requests would be 6000 requests per user, in each 24 hour period. Does that mean that it will be pooled to the tenant level with a limit of 48000 requests in each 24 hour period (8X6000) and all users can consume from this pool?
No. Power Platform requests are not pooled at the environment nor tenant level. This ensures that a heavy user doesn't consume all the Power Platform requests of the tenant and impact everyone else. Since the license is per user, the limit is per user too. So, all Office customers get 6000 requests each, whether they use them or not.
A guide to building enterprise ready flows contains great tips and best practices.
Best practice for design. Use the fewest number of actions possible to achieve your automation.
If you have 'Do until' or 'Apply to each' loops in your flow, see if you can reduce the number of loop iterations, possibly by retrieving fewer items to iterate through.
Many connectors have 'Filter query' and 'Top count' parameters that you can use to reduce the number of items and the amount of data retrieved by using OData.
If you have a scheduled flow that runs frequently, consider reducing the frequency. Many flows that run once per minute or once per hour could be revised to occur less often. Use trigger conditions to minimize the run frequency.
If your flow is interacting with files, be conscious of the file size and try to reduce it if possible.
If you need to reuse a single property returned by an action with large output size multiple times, consider using 'Initialize Variable' to store that property, and use the variable in later actions. Even if only one property is used from an output of an earlier action, all outputs of that action that will be passed into the later action as inputs.
Best practices to scale your flow.
If your flow runs thousands of actions daily, you should consider purchasing a Per Flow license to get better throughput and higher quotas.Per Flow plan provides the best performance quota available (250K actions/day). Please reach out to your tenant administrator to purchase the license and assign it to the flow. Once the license is purchased and assigned, the author of the flow should save it again. Alternatively, flows will be updated in the background once per week to reflect current plans.
Consider splitting the workload across multiple flows to achieve high scale.
Power platform requests Pay-as-you-go
We revised the Power Platform request limits for all licenses in late 2021. The new limits are designed to be sufficient for most customer scenarios. For more information on Power Platform request limits, visit the Requests limits and allocations page.
For customers with extremely high scale scenarios who need to exceed these limits you can link those environments to Azure subscription. By linking the environment, users and flows in the environment can consume more than their limits without being throttled and only pay for the Power Platform requests used above those limits. Flows still need to be licensed with a base license (either Power Automate per user, Power Automate per flow, Office 365, Power Apps, or Dynamics). For example, if you have Power Automate per user license, you have a limit of 40,000 Power Platform requests/per user/day. If the user used 45,000 requests a day, the additional 5,000 requests is multiplied by a $/request rate and billed to the Azure subscription. The total amount will be summed and billed based on the customer’s Azure billing cycle. Multiple meters are turned on when you turn on Pay-as-you-go at the environment. See How to set up Pay-as-you-go.
If you link an environment to an Azure subscription, this meter will not be reported or billed. Reporting and billing will be turned on by the end of calendar year 2021.
FAQs about request limits
You can consult this requests limits frequently asked questions for more information about requests limits.
If you sign in with work or school email address, you get all Power Automate capabilities included in Office 365. If you have a non-business user account (such as an account that ends with @outlook.com or @gmail.com), you can still use Power Automate with the free plan. Go to Power Automate and then select Try free.
You cannot share flows when you use the free plan.
To know which users have the free plan, admins can go to the O365 Admin portal, sign in, select Billing > Licenses to see how many free licenses are assigned vs available.
Select Assigned licenses to see which users have free license.
Power Apps Developer plan
There is a free Power Apps Developer plan to learn about Power Platform. You are not allowed to use it in production but can try out things and have access to all premium connectors. You can use this free developer plan also in a free Microsoft 365 developer tenant. Business process flows and RPA flows cannot be created in an environment with the Power Apps Developer plan.
Power Automate trials are available for 90 days. There are two types of trials available for Power Automate.
Admin managed trial
Global admins use the Microsoft 365 admin center to start these trials and assign them to users. These trials are for 30 days. Tenant admins can add a trial (subscription-based) environment to their tenant, or new organizations can sign up for a new tenant and become the global admin. For new organizations, an admin-managed subscription is created with a specific number of licenses (usually 25); admins control which other users get licenses assigned to them. An admin-managed subscription has an end date that can be extended once (another 30 days). Admins can get Power Automate attended RPA trial or Power Automate unattended RPA trial.
Follow these steps to get started.
Sign in to the Microsoft 365 admin center.
Go to Purchase services under the Billing section.
Search for "Power Automate", and then select a plan.
Select the details of a plan, and then select Start free trial.
You'll see a confirmation similar to this one.
After the free trial starts, go to Billing > Licenses to see the 25 new licenses available for you to assign to users.
Trials are different from free licenses. Once you start a trial, the sku name might not say Trial.
Users start these types of trials, either from the pricing page or from within Power Automate. This trial gives premium connector access, attended RPA, and unattended RPA. This trial is for 90 days.
User trials can also be started by user from within Power Automate. For example, when user tries to create a desktop flow without a Power Automate per user with attended RPA plan, the user is prompted to start a trial that includes usage of premium connectors, attended RPA, and unattended RPA.
Here are some of the frequently asked questions about trials.
How can I create an admin trial, check expiry and extend trials?
Check this document for instructions:
Follow these instructions to create an admin trial, check expiry, and extend trials.
How can admins allow or block trial licenses?
Admins can use PowerShell cmdlets to enable or disable trials. Once disabled, all existing plans of the specified type are removed from all users in the tenant. These aren't recoverable. Additionally, it will block all further assignment of plans of that type. Admins can enable trials at any time.
Learn how to create a trial (subscription-based) environment in the Power Platform admin center.
How can I convert a trial environment to a production environment?
You can convert either type of trial environments to a production environment by switching it to consume from paid capacity, keeping it from being disabled and deleted. After it becomes a production environment, it follows the paid license lifecycle.
Do trials work in GCC and government clouds?
No. Trials won't work in government clouds (GCC), and they can only purchase plans with volume discounting.
Can I see all trials using a PowerShell cmdlet?
Viral trials cannot be blocked by PowerShell cmdlet.
Submit and view feedback for