See Create a trial (standard) environment in the Power Platform admin center The type of trial environment you create depends on where you start and your tenant-level permissions.
After it becomes a production environment, it will follow the paid license lifecycle. You can convert either type of trial environment to a production environment by switching it to consume from paid capacity, which will keep it from being disabled and deleted. Neither type of environment consumes paid capacity. An admin-managed subscription has an end date that can be extended. For new customers, an admin-managed subscription is created with a set number of licenses (usually 25) admins control which other users get licenses assigned to them. Tenant admins can add a trial (subscription-based) environment to their tenant, or new customers can sign up for a new tenant and become the Global admin. Trial (subscription-based): This is the type of trial environment that companies can use to develop larger, multiuser and multiple-department solutions and perform proof-of-concept reviews.After 30 days, the environment is disabled and deleted. If allowed for users, any user from that organization who has a suitable license can create a 30-day trial environment. Organization (tenant) admins can enable all users to create trials, or only tenant admins. Trial (standard): This is the type of trial environment that companies can use to allow users and department managers to try new features and quickly build low-code and no-code applications and processes.The two types of trial environments provide this level of control. Others want admins to completely control what's being tried and who's licensed to use the environment.
Some companies let users try features in a self-serve manner. This is especially true when it comes to deciding whether to allow users to try new capabilities. Not all companies and admins approach trials the same way. The term "trial," as used in all other topics and the user interface, refers to the standard type of trial environment rather than the subscription-based type.
0 kommentar(er)
