BrightWork outlines the technical, licensing, environment, and governance considerations IT teams should review before implementing project and portfolio management software on Microsoft Power Platform.

BrightWork, a provider of project and portfolio management solutions built for Microsoft 365, is highlighting the key technical considerations IT teams should address before deploying a Project and Portfolio Management (PPM) solution on Microsoft Power Platform.

While deploying PPM technology within the Microsoft ecosystem can help organizations work with familiar tools and existing Microsoft 365 infrastructure, successful implementation requires more than installing an application. Licensing, Dataverse capacity, environment configuration, administrator permissions, reporting, automation, identity management, and governance can all influence deployment readiness.

BrightWork recommends that IT teams review these dependencies before project managers begin configuring project templates, workflows, dashboards, and portfolio processes.

Review Licensing Requirements Before Deployment

One of the first steps in a Power Platform PPM deployment is understanding which licenses are required for each type of user.

Different stakeholders may interact with a PPM solution in different ways. Project managers may need to create and update project records, portfolio managers may primarily review dashboards, while employees submitting project requests may have more limited requirements.

BrightWork 365 licensing and installation vary according to how users interact with the solution. Users who need to view, create, update, or delete records require a full BrightWork 365 license, while users who only submit Project Requests can be assigned a free BrightWork 365 license. BrightWork also notes that Microsoft Power Apps licensing requirements apply to BrightWork 365 users, while Power BI dashboard users require the appropriate Power BI licensing.

IT teams should therefore:

• Map user groups to the activities they will perform.

• Confirm required Power Apps licensing.

• Review Power BI requirements for dashboard users.

• Identify workflows that depend on premium Power Platform capabilities.

• Validate Microsoft 365 licensing before implementation begins.

Addressing licensing requirements early can help organizations avoid unexpected costs, access restrictions, or deployment delays later in the implementation process.

Select the Right Power Platform Environment

Environment planning is another important consideration for organizations preparing to deploy a Dataverse-based PPM solution.

BrightWork 365 installs into a Dataverse-enabled Microsoft Power Platform environment, and BrightWork recommends using a dedicated environment rather than the default environment. Organizations should also consider available Dataverse database and file capacity when preparing for deployment.

A dedicated environment can provide a clearer boundary for administration, security, application updates, capacity monitoring, and future expansion.

IT teams should consider not only the requirements of an initial pilot but also how the solution may evolve as more departments, projects, workflows, dashboards, and users are added.

Capacity planning should account for the expected growth of project records, tasks, risks, issues, documents, and other related information rather than focusing solely on the organization's initial rollout.

Establish Administration and Ownership

Deployment should also include a clear ownership model.

The administrator responsible for installing BrightWork 365 must have the appropriate Power Apps licensing and administrative permissions. BrightWork states that the installing user requires a Power Apps Premium license and must be a Power Platform Administrator or a System Administrator in the target environment.

Beyond installation, organizations should determine who will manage the environment and support the solution after launch.

Responsibilities may include:

• Managing application and environment access.

• Approving permission changes.

• Coordinating application updates.

• Monitoring Dataverse capacity.

• Supporting users and resolving technical issues.

• Coordinating technical decisions with the PMO.

BrightWork also notes that access can be managed by an IT administrator or delegated to a member of the project management or PMO team, allowing organizations to establish an operating model that fits their governance structure.

Evaluate Reporting, Automation, and Identity Dependencies

A PPM solution typically connects with other Microsoft technologies rather than operating as a standalone application.

BrightWork 365 is designed to work within the Microsoft ecosystem, including Power Apps, Power BI, Teams, and other Microsoft 365 services. The platform includes capabilities such as portfolio dashboards, project templates, project intake, workflow automation, resource management, and Power BI reporting.

Before deployment, IT teams should determine who will create, publish, share, and consume reports and dashboards. They should also ensure that reporting permissions align with application permissions so users receive the appropriate level of portfolio visibility.

Automation requires similar planning. Organizations should identify which accounts and connections will run approval, notification, and other workflows and establish ownership for maintaining those connections over time.

Identity management should also align with existing organizational policies. IT teams can determine whether access will be managed through groups, how new users will be provisioned, and how permissions will be removed when employees change roles or leave the organization.

Complete a Predeployment Technical Review

Before approving a Power Platform PPM deployment, IT and PMO teams should bring the major technical dependencies into a single review.

The assessment should cover:

• Licensing and user requirements

• Dataverse environment configuration

• Database and file capacity

• Administrator permissions

• Application ownership

• Power BI access

• Workflow and automation dependencies

• Identity and permission management

• Ongoing support and governance

BrightWork recommends that organizations evaluating BrightWork 365 review the product's documented licensing and installation requirements as part of technical planning. The requirements include information on BrightWork 365 licensing, Microsoft licensing, administrator permissions, Dataverse environments, and installation prerequisites.

Built for Project Management Within Microsoft 365

BrightWork 365 is designed to help organizations standardize project delivery, improve visibility, and manage projects and portfolios within their existing Microsoft environment. The platform supports project templates, portfolio dashboards, workflow automation, Power BI reporting, Teams collaboration, and project intake.

By completing the necessary technical checks before deployment, IT teams can establish the foundation for a more predictable implementation while allowing PMOs and project leaders to focus on process design, project governance, and user adoption.

About BrightWork

BrightWork provides project and portfolio management solutions designed to help organizations manage projects and portfolios within Microsoft 365. BrightWork 365 is built on Microsoft Power Platform and works with Microsoft technologies including Power Apps, Power BI, Teams, and SharePoint. The platform is designed to provide project visibility, standardized processes, workflow automation, portfolio management, and collaboration within an organization's Microsoft environment.

Media Contact Details

BrightWork

Send Email

www.brightwork.com/?utm_source=chatgpt.com