727-216-8010 / 805 618-1853 info@protekitsolutions.com

Microsoft Office 365 Power Automate has 2 different pricing models, a fixed monthly price or a Pay-As-You-Go per flow pricing model. See the article below and scroll down to see the per flow prices:

Pricing | Microsoft Power Automate

The fixed monthly pricing model is very easy to setup and assign to an Office 365 user. However the Pay-As-You-Go per flow plans requires multiple steps to setup a number of things in Azure for users to actually be able to use it. If you’re not already very familiar with Azure, this can be confusing at first and simple basic steps have been written from this viewpoint.

In summary you need to:

  • Create an Azure account and set up a subscription with a credit card.
  • Set up an environment and create a resource group tied to the azure subscription.
  • Create a billing policy and tie that to the resource group and environment.
  • Create security groups and tie users to it.
  • Tie the security group to the environment.
  • Then there are also security roles within azure environment that need to be tied to each user within the security group.
  • That user needs to select in the power automate app to use that specific environment for it to work.

Steps: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-set-up

Azure Pay as You Go – Setting up Pay as You Go Plan for a Power Automate per Flow Pricing Model

  1. Create a free Azure Subscription, using an admin user from the 365 account

https://azure.microsoft.com/en-us/free/

  1. Make sure to link a credit card at set up (won’t charge unless told to)

This creates your azure subscription

2. Sign in to https://portal.azure.com

  1. Create a “Resource Group” tied to that new Azure subscription
  2. Launch the Power Platform admin center: https://admin.powerplatform.microsoft.com/
  1. Click on environments and create a new “production” environment
  1. Go to Azure Active Directory: https://aad.portal.azure.com
  1. Go to Groups
  1. Create a “power Automate access” security group
  1. Add the users that you want to tie to the environment with the pay as you go billing policy we will soon create
  1. Go back to https://admin.powerplatform.microsoft.com/
  1. Click on the environment you created in step 5
  1. Click edit (in the details square)
  1. Click the pencil button next to security groups
  1. Add the security group made in step 8
  1. Click on settings in that environment
  1. Click users and verify the needed user(s) show up (members of security group)
  1. Go back to settings and click security roles
  1. Find “Basic User” and click on it
  1. Click “Add People”
  1. NOTE: unclear if other roles are required I added a bunch that I thought would help because the environment wasn’t showing up, Basic User seems to be for sure at least needed for them to be able to access anything in that environment.
  1. Add the needed users to give them this role
  1. Create the billing policy as laid out in this article to set up the pay as you go plan: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-set-up
    1. Navigate to https://admin.powerplatform.microsoft.com/azurebilling
    2. New Billing Policy
    3. Give it a name
    4. Choose to bill to the azure subscription you created earlier
    5. Tie it to the production environment you set up already
    6. Review and confirm
  1. Sign in with the users to power automate on the web and they will see the new environment is added to their power automate – they need to click in top right corner to access that environment.

More notes on stuff Microsoft assumes you will already know when trying to use the licensing:

  • No need to license power automate if setting up the pay as you go plan – once the above is set up they will have access to power automate and will be charged per flow.
  • The user will be able to access the desktop app download when they sign in to power automate on the web and select the correct environment.
  • The user if already using a free trial will need to move all of their created flows to the NEW environment, they aren’t linked.
  • You can link a default environment to a billing policy.

If you require further help, please leave a comment and we will answer it as soon as possible.

For professional IT support, please contact ProTek IT Solutions.