MS Project Ops 365 Integration

I am looking for an experienced Microsoft integration developer to build a simple, cost-effective MVP connecting our existing project scheduling environment with Microsoft Teams and Power BI.

The objective is to establish a single, controlled source of project schedule information, enable site staff to submit progress updates through Teams, and provide management with a clear dashboard showing project progress and schedule performance.

The solution should prioritise simplicity, reliability, and the use of existing Microsoft 365 licences wherever possible. Daily synchronisation is sufficient; real-time integration is not required.

Scope of Work

1. Master Schedule Integration

Connect the existing Microsoft Project / Dynamics 365 Project Operations scheduling environment to the reporting and progress-update workflow.

Import or synchronise relevant schedule information, including task ID, task name, WBS, planned dates, baseline dates, actual dates, percentage complete, status, and task owner where available.

Use the existing task ID as the primary reference to avoid duplicate activities.

Review the current environment and recommend the simplest supported integration approach, using existing connectors, Power Automate, APIs, or a file-based method if necessary.

The freelancer must validate the exact scheduling product, available APIs/connectors, permissions, and licensing requirements before finalising the solution design.

2. Microsoft Teams Progress Updates

Enable approximately 10 users, including site staff and supervisors, to submit daily progress updates through Microsoft Teams.

Capture basic information such as task ID, percentage completed, current status, actual start/finish where applicable, and remarks.

Make submitted updates available in the reporting dashboard and, where technically feasible, synchronise approved actual-progress fields back to the master schedule.

Provide basic notifications or exception alerts for failed synchronisation and issues requiring PMO review.

The implementation method may use a Teams form, workflow, adaptive card, or another suitable approach, depending on feasibility and cost.

3. Schedule Governance and Data Control

The approved master schedule must remain the controlled source of truth for schedule structure and planning.

The approved baseline, planned start/finish dates, dependencies, and task structure must not be changed automatically by routine site updates.

Site staff should be able to submit progress and status updates only.

Changes to the master schedule or approved baseline must remain under authorised PMO control.

Conflicting, invalid, or failed updates should be flagged for manual review rather than silently overwriting schedule data.

4. Power BI Management Dashboard

Develop a basic Power BI dashboard using the available schedule and progress data.

The dashboard should include:

Overall project progress and activity-level progress.

Planned versus actual progress and dates.

Overdue and blocked activities.

Upcoming milestones and key deadlines.

WBS/activity-level drill-down and last-update information.

The report should refresh automatically at an agreed frequency, preferably daily. The freelancer should confirm the required Power BI licence, data connection, and refresh limitations.

Advanced analytics, earned value management, cost forecasting, and financial-system integrations are not required for this MVP.

Expected Deliverables

A working integration between the existing scheduling environment, Microsoft Teams progress-update workflow, and Power BI dashboard.

A tested daily synchronisation process with basic error logging and a manual recovery or rerun procedure.

One Power BI report covering the agreed project progress and schedule KPIs.

Testing covering schedule-data synchronisation, Teams progress submissions, dashboard refresh, and protection of the approved baseline.

Deployment, configuration documentation, and a short handover guide explaining how to operate and maintain the solution.

A clear list of software licences, premium connectors, permissions, and other dependencies required to run the solution.

Timeline and Commercial Expectations

Target delivery: Within 1 week, Max 2 week

Initial user base: Approximately 10 users.

Scope: Design validation, build, testing, deployment, and handover.

Budget approach: Cost-effective MVP using existing Microsoft tools and licences wherever feasible.

Ongoing support: AMC, ongoing support, and future enhancements are outside the current scope.

Please quote the one-time implementation cost separately from any mandatory software, connector, or recurring license costs.

Required Experience

Experience with relevant Microsoft technologies, including:

Dynamics 365 Project Operations and/or Microsoft Project.

Microsoft Teams integration and workflow automation.

Power BI reporting and scheduled refresh.

Power Automate, Dataverse, APIs, and authentication where applicable.

Proposal Requirements

Please include the following in your proposal:

Your recommended architecture and why it is the simplest cost-effective option.

Your experience integrating Microsoft Project or Dynamics 365 Project Operations with Teams and Power BI.

The information you need to validate our existing environment before development.

A breakdown of one-time implementation costs and recurring licence costs.

Any limitations, licensing dependencies, or risks that could affect the two-week timeline.

Your proposed milestones for development, testing, deployment, and handover.

The exact integration method is open for recommendation. We are looking for a practical, reliable solution that meets the core requirements without unnecessary custom development or ongoing costs.