Comments
Also vote for: .... https://experience.dynamics.com/ideas/idea/?ideaid=e6ad237e-5c88-e911-80e7-0003ff68d30d ....and.... https://experience.dynamics.com/ideas/idea/?ideaid=692f6f72-fa1f-eb11-8441-0003ff68950e ....and.... https://experience.dynamics.com/ideas/idea/?ideaid=86ff7798-7722-eb11-8441-0003ff68950e .....Similar requests, as old as business central.
Also vote for:https://experience.dynamics.com/ideas/idea/?ideaid=e6ad237e-5c88-e911-80e7-0003ff68d30dandhttps://experience.dynamics.com/ideas/idea/?ideaid=692f6f72-fa1f-eb11-8441-0003ff68950eandhttps://experience.dynamics.com/ideas/idea/?ideaid=86ff7798-7722-eb11-8441-0003ff68950eSimilar requests, as old as business central.
Hi,Yes please. There are cmdlets available for some elements of Power Platform administration like creating environments but not for the creation of pipeline records, pipelines, and pipeline stages. In companies with a large number of environments the ability to automate these pipeline aspects is important, whether for self-service, standardising configurations or reducing administrative effort. The ability to configure their pipelines would safe considerable time and effort. As or more significantly, without about to automate this, self-service onboarding is not possible at all.
This poses a big issue when we consider companies that do skip lots combined with standard testing for all transactions. Especially for companies which are heavily regulated, and require a smooth cut-over, they can not afford to switch from failed tightened spec testing to normal during cut-over. The tightened testing must pass and be completed before the vendor is clear for the normal AQL. Please consider this as a very important gap in the design. Thank you very much