Advanced Licensing Information

Scenario Breakdown

Scenario	Power Apps	Power BI	M365/Teams	Power Automate	Planner	Project	Copilot
Core Scenarios - Mandatory
View and update Altus Tasks and tasks in other systems1	Per user
Create/Update Projects, Tasks, Registers (Risks Issues, etc.), Portfolios, Programs, Benefits, Strategy2	Per user
Execute workflows inside Dataverse and non-premium connectors	Per user
View Power BI Reports		Power BI Pro / Capacity
Core Scenarios - Recommended
View and update Project Documentation			M365 E1, E3, E5 ...
Collaborate with other project members3			M365 + Teams
Additional Scenarios - Optional
Execute workflows with premium connectors4				Per Flow / Per user
View and update Tasks with Planner Basic					M365 E1, E3, E5 ...
View and update Tasks with Planner Premium					Project P1, P3, P5
View and update Tasks with Project Desktop						Project P3, P5
Smart Paste							(Not required while in Preview)
Natural Language Search							(Not required while in Preview)
AI Form Fill Assistance							(Not required while in Preview)
AI Row Summary							(Not required while in Preview)
AI Insights cards							(Not required while in Preview)
Allow users to converse with Altus Copilot Agent							M365 Copilot (1 needed for Agent publishing)

¹ – License multiplexing rules from Microsoft and external systems may apply and could require end-users consuming or authoring data to hold additional end user licenses. Contact the relevant third-party vendors for more information on their individual licensing requirements.

² – AAD Guest access to the Altus Teams & Power App is not currently supported, but is likely to be enabled by a future update.

³ - Guest access via Teams and SharePoint has limitations and additional tenant requirements.

⁴ - At least one Power Apps Per User or Power Automate Per User licenses are required to deploy any Power Automate Flows that consume premium connectors.

Warning

Use of External/Guest accounts is unsupported. There are known issues with accessing the Microsoft Power Platform, Teams and Altus via External/Guest accounts. While using an External/Guest account some features will be unavailable and performance will be impacted. For more information regarding External/Guest accounts please click here.

Note

We only provide indicative general licensing advice, consult your Microsoft licensing advisor to confirm the specific licensing costs/requirements for your deployment.

Licensing FAQ

Can my organization use pay-as-you-go plan licensing for Power Apps?

Yes. Pay-as-you-go is an alternative licensing plan for Power Apps. Microsoft provides documentation on this option here

In order to set up this option for licensing your users to use Altus, organizations should follow the Microsoft documentation here.

Can I use Power BI Free instead of Pro or Premium?

The shared and embedded reports in Altus require all end-users to have either a Power BI Pro license or to be hosted in a Power BI Premium capacity.

From Microsoft: "With sharing, whether you share content inside or outside your organization, you need a Power BI Pro license. Your recipients also need Power BI Pro licenses, unless the content is in a Premium capacity."

Can my organization use trial licensing for Altus?

Having trial licenses expire during the deployment or rollout is undesirable and very costly. For Production roll-outs please utilise non-trial licenses at least for the deployment account.

Does the Power Apps provide my end-users with Power Automate capabilities?

The Microsoft Power Apps license allows Power Automate Flows to be used in conjunction with the Power App.

From Microsoft:. "In the original introduction of the new licensing and as a consequence of the older model, it was thought that a separate license would be required for a Power App to use A Power Automate Flow when, in fact, it is only the cost of the Power App that will apply even if the Premium connector is only accessed via the flow. The key guidance here is to understand the use case of the flow itself whether it is created to service the app or if it is the type that is expected to be shared or used outside of the application as it will then be a case of selecting the appropriate Power Automate license."

License Multiplexing

Multiplexing is a complex topic and one that changes over time. Modern cloud services commonly offer many types of integration and the licensing requirements of each scenario can vary by the specific implementation and between customer agreements for the same product. Multiplexing may impact the licensing needs of Altus customers when individuals use hardware or software to pool connections, reroute or indirectly access information, and/or reduce the number of devices or users who directly access or use a product.

From an Altus perspective, there are several areas where multiplexing may be considered.

Inbound Dataverse Multiplexing

From the perspective of the Dataverse, inbound multiplexing occurs when users are able to enter data into the Dataverse without having a Power Platform license.

From Power Platform Licensing Guide - April 2024.pdf:

"Any user or device that inputs data into, queries, views data from or otherwise accesses Power Apps, Power Automate, Power Virtual Agents and Power Pages apps, directly or indirectly must be properly licensed"

Outbound Dataverse Multiplexing

Outbound multiplexing occurs when data is automatically extracted from the Dataverse and then consumed by users that do not have a Dataverse license:

From Licensing_Brief_PLT_Multiplexing.pdf:

"Any user or device that accesses the service, files, data, or content provided by the service that is made available through an automated process requires a Dynamics 365 service license"

Third-party multiplexing

There is also the potential for multiplexing with third-party applications. The exact requirements of each third-party application may differ, so please refer to your own individual license agreement with the third-party to assess the compliance requirements.