Some of our largest partners are already embedding Power Automate into their solutions. Adobe for example, as Satya mentioned in his keynote:” …is embedding Power Automate into Acrobat Sign so users can automate their document workflows directly from within the app itself. They can generate documents at scale and easily route agreements across stakeholders and systems.”

Earlier this year at the Microsoft Build conference, we also heard from Amy Bunszel, Executive Vice President of AEC Design Solutions at Autodesk. Autodesk is making design data more accessible and useable across their ecosystem of products, through a new integration with Power Automate that extends the value of low code to the AEC industry. Watch the full conversation between Julie Strauss and Amy Bunszel here starting at 0:31.

With this new approach to embedding both our low code capabilities along with licensing we have greatly streamlined both onboarding and operation of our embed capabilities: Whether you’re a long-time Microsoft ISV or brand-new partner to Microsoft, it is super simple for you to include Power Automate as part of your SaaS offering. There is no need to join the CSP , you can simply build and distribute your solution, and optionally, work with a reseller. Additionally, you can join the ISV Connect benefits program, should you want to do so. The standard revenue share fee does not apply to ISV Embed and if you have a Microsoft Azure Consumption Commitment (MACC), you can use that to cover the licensing cost for the Power Automate pay-as-you-go meter. Finally, you can set up Power Automate Embed pay-as-you-go with just an Azure Subscription where only requirement on your customers is an Azure Active Directory (AAD) tenant.

To summarize this amazing new approach, that simplifies how you can include Power Automate as part of your SaaS offering:

• We have made it super simple to enhance the value of your offerings and embed industry-leading low code automation capabilities into your SaaS offerings: No need for the customer to go procure the required Power Automate license from Microsoft themselves or for you to become a CSP in every market you want to sell into. You simply embed the capabilities you want to extend to your customer and sell and deploy it as a unified offer.
• Your customers can work with a single vendor instead of procuring software from multiple vendors to stitch together a solution: Customers want to buy a solution that helps deliver on a business outcome, they are not buying licenses and having to transact with multiple vendors complicates the desired outcome.

With pay-as-you-go pricing, you only pay for what your customers use and eliminate the work associated with license assignment: No need to identify how many, and which users will be using Power Automate. Using the new license embed capabilities enables users to build and run premium Power Automate flows that uses connectors defined by you – the ISV – as part of your product definition. Subsequent usage is then calculated based on the number of times each flow is run and billed against an Azure subscription owned by you completely eliminating the need for the customer to think about the billing of the Power Automate capabilities being used.

To join the Public Preview, please register here and let us help you get started.

For more details on the ISV Cloud Embed program, please tune into the Inspire session OD30 where Per Mikkelsen, Principal Group Program Manager, along with Ecosystem Marketing Embed program lead Jerry Weber goes into more details, as well as how Power Automate Embed can easily work for ISVs that are already in the existing Embed program or are considering trying out this new approach with Power Automate.

The post Power Automate pay-as-you-go for ISVs appeared first on Microsoft Power Platform Blog.

With GitHub Connector, you can create a GitHub repo, create a pull request, merge a pull request, compare commits, trigger a GitHub actions workflow and much more from Power Apps and Power Automate.

The GitHub connector works perfectly with the GitHub Actions for Power Platform released in preview recently. The create a repository dispatch event can be used in Power Automate or Power Apps to trigger a GitHub actions workflow in your repo. See how to set it up below or jump straight to this repo to setup and use the PowerOps app from Power CAT that has taken the concept to the next level.

1. Create a manually triggered Cloud Flow, and search for the GitHub Connector.
2. Select the action Create a repository dispatch event.
3. Enter the following details and save the flow:
   • Repository Owner – This is your GitHub Organization name.
   • Repository Name – This is your GitHub Repo name.
   • Event Name – This is the name of trigger that your GitHub workflow is listening to. 
4. In your GitHub workflow definition (yml file), ensure that your workflow has the following trigger:    repository_dispatch:   types: <Event Name entered in the flow definition in step 3 above>
5. Test the flow and validate that your GitHub actions workflow is triggered in your repo.

The post GitHub connector features for Power Platform appeared first on Microsoft Power Platform Blog.

This means that enterprises can now truly benefit from existing assets hosted on Azure, by making these available to Citizen developers with just a few clicks in the Azure portal, thereby eliminating the additional steps to go create custom connectors in the Power Apps or Power Automate maker experiences.

Citizen developers can use these API Management backed connectors in Power Apps hosted in Teams through the existing Teams licensing

Read more about API Management and how to export to Power Platform here.

The post Azure API Management connector on the Power Platform appeared first on Microsoft Power Platform Blog.

With GitHub actions for the Power Platform, you can create workflows that you can use directly in your source code repo to build, package, release and deploy to the Power Platform.

The actions can be used individually to create custom workflows, or pre-configured workflows can be used  to develop, and deliver Power Platform solutions.

We recently released similar capabilities for Azure DevOps with the Power Platform Build Tools and the release of GitHub actions for the Power Platform now offers developers additional flexibility. This will greatly improve the ability and efficiency of enabling  code-first and low-code teams to work together seamlessly as a fusion team. The Actions are available today, and will be available on GitHub Marketplace in October

Learn more about the GitHub action here. 

The post GitHub actions for the Power Platform now available in preview appeared first on Microsoft Power Platform Blog.

This release is part of our continued investment in mature Application Lifecycle Management (ALM) across the platform, hence the change of the name from Power Apps Build Tools that has been in preview until today, to Power Platform Build Tools. As part of this overall effort, we also recently announced a complete rewrite and restructuring of our ALM documentation along with continuous improvements to the solutioning system to support applications that use components across the Power Platform. This now includes canvas & model driven Apps, UI flows (RPA), automated flows, data flows, Power Virtual Agents, AI Builder and custom connectors. You can read more about the Power Platform Build Tools in our documentation here.

This release also includes support for creating an environment on demand and use that environment in subsequent tasks, for example to generate a build artifact.

The post Announcing general availability of Microsoft Power Platform Build Tools appeared first on Microsoft Power Platform Blog.

We have aimed to create a guide that covers everything from simply explaining ALM for beginners, to how you can move from an environment-centric development to a model where apps and automations are backed by source control and Continuous Deployment and Continuous Integration (CI/CD) implemented using Azure DevOps

We hope you find this new content helpful, whether you are a seasoned developer looking to implement DevOps for application development on the Power Platform, or a Citizen Developer wanting to learn how you can move to a more structured approach to application development.  We will be improving and adding more content to this guide as our features/processes evolve.

The post Finally – Application Lifecycle Management (ALM) on the Power Platform explained appeared first on Microsoft Power Platform Blog.

Your full set of options to assess the AppSource certification readiness of your solution includes:

• • Adopting the full set of Azure DevOps tasks outlined here  and include the ‘PowerApps Checker Task’ in your build pipeline, making the validation part of your continuous CI/CD pipeline.
  • Set up a simplified Azure DevOps pipeline with just the ‘PowerApps Checker task’  to validate the solution at any time
  • Use the new PowerApps Checker PowerShell module as announced here, to run the AppSource Certification Ruleset against your solution(s).

We are truly excited be able to offer these new capabilities, which will help  address feedback from partners asking for a faster, more simplified approach to the AppSource certification process. We are keep to continue to engage and would love to hear from you through aka.ms/isvstudioforum. Alternatively, send an email to ISVFeedback@microsoft.com.

The post Assess the AppSource certification readiness of your solution appeared first on Microsoft Power Platform Blog.

This initial release is the first step towards a more comprehensive, yet simplified story around ALM for PowerApps. A story we will continue to augment by adding features based on feedback, but equally important – by continuing to invest in more training and documentation with prescriptive guidance. In other words, our goal is to enable our customers and partners to focus more on innovation and building beautiful, innovative apps and less time on either figuring out how to automate or perform daunting manual tasks that are better done automated.

What is the PowerApps Build Tools?

The PowerApps Build Tools preview is a collection of PowerApps specific Build Tasks for Azure DevOps. Some of these tasks are outlined below, but a list of all available tasks is available here.

PowerApps Checker: This task enables you to run solution checks outside of the PowerApps Maker user experience in an automated manner. This means you can run static analysis check on your solution(s) against a set of best-practice rules to identify any problematic patterns you might inadvertently have introduced when building your solution.

This enables traditional developers to continuously validate their code and to do so much earlier in the development lifecycle. They can take advantage of both the standard set of rules used by the Solution Checker introduced earlier this year and, if you are an ISV, additionally run the rule set required to pass the certification test when publishing an app to AppSource.

For ISV’s, this means no more packaging everything up, submitting it for certification simply to wait for the results before you can start fixing any issues and start all over. This task is taking advantage of the PowerApps checker PowerShell Module announced in previous post
PowerApps Import Solution: No more manual imports. The import solution automatically imports your solution into a target environment.

PowerApps Export Solution: As above, just the other way around. This task automatically exports your solution from a source environment. No more waiting around for an export to complete before choosing where to save it, only to move it to a share location somewhere or into a repo as a .zip file.

PowerApps Unpack Solution: Want to get your solution metadata to source control? This task takes a compressed solution file and decomposes it into multiple XML files so that these files can be more easily managed by your source control system.

PowerApps Pack Solution: Packs your solution represented in source control into a solution.zip file that can be imported into your target environment.

We are truly excited to announce this preview and encourage everyone to submit ideas and provide general feedback through the PowerApps Forum

The post Automate your application lifecycle management (ALM) with PowerApps Build Tools (Preview) appeared first on Microsoft Power Platform Blog.