Test the waters

When building enterprise flows that is shared with a large set of users in your organization, it is often tough to predict how many users will want to use it. Now you can start with the pay-as-you-go option to gauge usage patterns then determine whether purchasing a pre-paid Power Automate subscription plan makes sense.

Share costs across your organization

Many organizations want to allocate software license costs to the department or team that used the licenses.  Pay-as-you-go makes this possible by letting teams pay for flow runs using Azure subscriptions linked to their own departmental budgets, and by providing the option to use Azure Cost Management and Azure tags to visualize and divide up costs.

Setting up Power Automate pay-as-you-go plan enables users to build and run premium Power Automate flows and to pay for their usage using Azure subscription based on the number of times these flows run.

Users and flows with standalone licenses will not incur charges for running flows. This means that you can simultaneously leverage the per user plan to license some users of your flows in a pay-as-you-go environment while also using the Power Automate pay-as-you-go meter to cover for seasonal/occasional usage. You can review usage reporting for Power Automate pay-as-you-go meters in the downloadable pay-as-you-go consumption report from the Power Platform admin center and move users to standalone licenses for optimal pricing.  For more details about how flow run charges work please review our documentation.

To make it easy to test and fix your flows no charges will be incurred if you’re testing your flow in the designer or resubmitting failed runs. Additionally, if you use the child flow feature for cloud flows or attended desktop flows, there will only be a single charge for the parent flow run, no charges will be incurred for child flow runs.

In addition to Power Automate, other services like Power Apps and Dataverse are available in a pay-as-you-go model offering flexible licensing across the Power Platform.

If your organization already has one or more Power Platform pay-as-you-go environments configured, Power Automate pay-as-you-go will be enabled for all those environments and any Power Automate usage in those environments that qualifies based on our documentation, will result in charges to your Azure subscription.

Check out this video for a deep dive on Power Automate Pay-as-you-go plan

aka.ms/PowerAutomatePaygovideo
Please give it a try and share your thoughts!
Questions: Power Automate community forum

The post Announcing public preview of pay-as-you-go for Power Automate appeared first on Microsoft Power Platform Blog.

You can change the owner to an individual or an Azure Active Directory service account. If the flow is using a service account, see here for guidance on licensing service accounts.

To change the owner, first select a solution flow and edit the flow details section:

Next, remove the current owner and search for the new owner:

If the flow is a scheduled or Automated flow, once the owner is changed, the flow will run under the license of the new owner and use their Power Platform request limits. If the flow is a manual flow, the flow will run under the license of the user who runs the flow. The Plan section shows whose license plan is used by the flow.

This change is limited to solution flows. For changing the owner of a non-solution flow, the flow must be exported and imported by the new owner. Check out this video to learn how to export and import as new owner.

For more details, see the documentation here.

Happy Automating!

The post Change owner of a solution flow appeared first on Microsoft Power Platform Blog.

For more information on Power Platform requests please visit aka.ms/platformlimits

Additionally, for customers with extremely high scale scenarios who need to exceed these boundaries, the Power Platform requests meter enables them to scale without getting throttled — only paying for the Power Platform requests used above the limits.  For example, if a user with Power Automate per user license used 45K requests in a day, since the license allows up to 40,000 requests/24 hours, they can just pay for the 5K additional requests used. For more information, please visit Pay-as-you-go for overages.

Note: as of Public Preview (11/01/21) if you link an environment to an Azure subscription this meter will not be reported or billed. Users and flows in the environment can consume more than their limits without being throttled or paying for overages. Reporting and billing will be turned on in the weeks following the Public Preview announcement.

We also revised the prepaid Power Platform capacity add-on to provide 50,000 requests per day to enable customers to scale in non-Pay-as-you-go environments.

The post Updates to the Power Platform request limits appeared first on Microsoft Power Platform Blog.

Look no further.  We have just launched a new set of documents by curating customer support asks and community asks to help you learn how to automate with top connectors in Power Automate. Whether you’re a businessperson who has never participated in an automation or you’re a “full stack” developer who wants to use Power Automate– this set of articles is for everyone who wants to learn or upgrade their skills with Power Automate.

What’s better? You can now access them while building flows. Just choose a connector/action/ trigger and launch the new contextual help pane (via ? in the title of the card) to see the corresponding documentation, community answered questions, blogs based on your selection.

We also launched an assistant for Power Automate to aid in authoring workflows in the form of a Power Virtual Agent bot (PVA bot) that provides the next level of assistance for customers in a question/answer interaction format. You can now get assistance in solving the most common workflows in Power Automate by accessing content in the form of templates, documentation, and community answers. Based on support tickets, we are starting with Email, Triggers and Licensing topics and will fast follow with SharePoint, Approvals and Forms. We continue to add more topics to PVA bot so please check back later for updates. If you have a question that isn’t covered in these topics, you can ask the bot and the bot will search for answers in docs/communities/blogs. Detailed documentation of both features can be found here

For easy access to all power automate documentation, bookmark Power Automate documentation – Power Automate | Microsoft Docs.  You can find the newer documentation in below section

Be sure to check out related topics in sections below to learn how to get started, using the best practices and guides to troubleshoot the most common issues by connector. 

We are planning to continually evolve these documents for better guidance. If you have any feedback on the documents, please feel free to make a feedback comment on the docs! 

Finally, to make it easier to debug flows we have also added new options to Show raw inputs and Show raw outputs on the flow runs view.

The post Discover, learn and create flows using in product help! appeared first on Microsoft Power Platform Blog.

Naturally, these investments are designed to help ISVs be more productive on the platform, but equally importantly they are intended to help ensure we can better serve customers in collaboration with our ISV ecosystem allowing partners to build high quality apps and proactively manage and monitor the performance of these apps.

The ISV Studio is an important step towards helping ISVs manage and monitor their applications across their install base. Something that has simply not been possible in the past. So, if you are an ISV and you extend Dynamics 365 Customer Engagement or build PowerApps on the Common Data Service, this is for you.

By participating in the preview, you will be able to experience the benefits of a consolidated view of your PowerApps and Dynamics 365 CE apps providing cross tenant application insights, which will allow you to monitor your apps, enabling you to better support your customers. You can gain insight into your install base and assess successful versus any potential failed attempts to install your app. Additionally, you can gain insights into your installed versions across tenants and environments, which will help you assess support impact and overall adoption of your apps.

To access the public preview of ISV Studio, navigate to https://aka.ms/ISVStudio.

Note:

• To access the ISV Studio, you must have an Azure Active Directory (AAD) account and be configured as App publisher owner/contributor in Cloud Partner Portal for that particular account.
•  If you want additional users to get access to ISV Studio, they can be added as app contributors in CPP. Instructions can be found at Managing users on cloud partner portal.
• The ISV Studio supports Dynamics 365 CE and PowerApps solutions built on the Common Data Service (CDS) that are published to and deployed through AppSource. As such, metrics shown are based on customer installations performed via AppSource only. For apps installed directly in the customer environment, metrics will not be shown.
• ISV Studio does not support apps installed in customer sovereign clouds.

Once you log in to the ISV Studio, you land on the Home page. If you are associated with multiple publishers in AppSource, you will see the app metrics by publisher and can toggle between publishers. The Home page shows your published PowerApps and Dynamics CE apps and the number of package installations by tenant. It also shows you the number of successful vs failed package installations across all production environments for the last 28 days. Below the summary section, you can access additional insights and can choose to further drill down into install history through the lens of Certified Apps or Tenants.  

The Home Page

App Metrics 
Through the lens of each application you published to AppSource, you can gain insight into cross tenant adoption patterns. Out of your successful package installs, you can see how many of them are Prod vs Sandbox, their tenant locations, their package versions by tenants. You can also see the install attempts (Success vs Failures) by tenant in the last 28 days.


Tenant Metrics
Adoption patterns are also accessible from a tenant perspective. Form the Home page, you can navigate to the tenant specific metrics of your apps, where you can monitor successful app installs by environment. Additionally, you can assess how many of the package installs are Prod vs Sandbox, their locations and package versions in the selected tenant.


Upcoming Capabilities 
The capabilities available in the ISV Studio today, is only the beginning and we will continue to invest in this experience adding new capabilities based on your feedback.
The two main capabilities we are planning to release in the near future:

• More detailed install error messages allowing you to more easily troubleshoot issues and take immediate action.
  
• Ability to seamlessly access the PowerApps Checker from within the ISV Studio, enabling you validate your app against the same criteria that Microsoft uses to certify your app as part of the AppSource publishing process.  This will allow you to validate your app before submitting it for certification and hence save  you significant time since you do not have to package up the final app and submit it for certification before you even know if there are issues with the code you need to resolve.
  

NOTE: As part of our continued effort to make the certification process faster and more transparent, we also recently announced the public preview of PowerApps Build Tools that includes an Azure DevOps Build task (PowerApps Checker task) to validate your app against the AppSource certification criteria. This means that you can start validating your app today and even do this continuously in an automated fashion as part of your Build process, thereby running the validation earlier in the lifecycle and closer to the developer where issues are much faster and cheaper to resolve.

If you are not using Azure DevOps, this same capability can still be accessed simply using PowerShell as announced in this post.

Where to get help
A huge thanks to everyone who provided valuable feedback as part of the private preview. To continue discussions around PowerApps ISV Studio, and to provide feedback on capabilities you would like to see us support, please visit our forum:

aka.ms/isvforum

To request access to the forum, please update your role as ISV in Insider profile (https://experience.dynamics.com/insider) and in My Programs, search for ISV Insiders and participate in Discussions.

Alternatively, send an email to ISVFeedback@microsoft.com.

Your feedback is important for us to shape the experiences moving forward.

The post PowerApps ISV Studio is now available for public preview appeared first on Microsoft Power Platform Blog.