--- title: "Integrate a Microsoft Project Plan (MPP) in the Altus app" url: "https://help.altus.pro/fr/article/integrate-a-microsoft-project-plan-mpp-in-the-altus-app" language: "fr" last_updated: "2026-09-21T07:04:13.183Z" --- # Integrate a Microsoft Project Plan (MPP) in the Altus app [Embedded content](https://player.vimeo.com/video/1001838994) The **Altus for Project add-in** connects a locally saved Microsoft Project Plan, or MPP file, to an Altus Project. This allows Project Managers to maintain the detailed schedule in Microsoft Project while publishing Task information to Altus for: - Centralised visibility - Project reporting - Resource management - Timesheet entry - Importing approved timesheet Actuals - Program and Portfolio oversight Microsoft Project remains the source of truth for schedule changes. Update the schedule in Microsoft Project, then publish it to Altus to keep both systems aligned. > **Important:** > The schedule owner must know where the linked MPP file is stored and have permission to access that location. > > The Microsoft Project indicator shown on the Altus Project confirms that the Project is linked to an external Microsoft Project schedule. It is **informational only** and is not a link or button for opening the MPP file. > > The MPP file must be opened directly from its saved location using Microsoft Project. * * * ## Altus for Project Add-In The Altus for Project add-in is normally activated automatically in Microsoft Project after it has been installed. However, your organisation may restrict which add-ins can be installed or activated. If the **Altus** ribbon does not appear after installation, refer to the [Altus for Project deployment and add-in activation guidance](https://docs.altus.pro/solutions/AltusForProject/Deployment.html?tabs=Admin%2CGA#microsoft-office-add-in-activation). > **Important:** > You must have the Altus for Project add-in installed and permission to use it in the relevant Altus environment. * * * ## Understand Link, Connect, and Publish The following actions perform different functions: - **Link** creates the relationship between the MPP file and the Altus Project. - **Connect** starts an active connection to the selected Altus environment so that publishing, resource management, and timesheet import actions can run. - **Publish** sends the Microsoft Project schedule Tasks to the linked Altus Project. - **Microsoft Project indicator in Altus** confirms that the Project is associated with a Microsoft Project schedule but does not open or locate the MPP file. > **Important:** > Linking the MPP file does not publish the schedule. > > After linking, you must connect to Altus and publish the MPP file before its Tasks become available in the Altus Project. > > Altus does not provide a button for launching the underlying MPP file. The schedule owner must locate and open the file from its saved location. * * * ## Before You Begin Confirm that you have: - The Altus for Project add-in installed - Microsoft Project installed - Access to the required Altus environment - Permission to use Altus for Project - Access to the relevant Altus Project - A saved local MPP file - Access to the location where the MPP file is stored The MPP file may be stored: - On the schedule owner’s computer - In an approved OneDrive location - In an approved SharePoint document library - In another organisation-approved file location > **Important: Know Where the MPP File Is Stored** > Altus does not store the MPP file or provide a direct link for opening it. > > The schedule owner must know the approved storage location and open the MPP file directly from that location using Microsoft Project. > > Store the file in a recognised and governed location so that authorised schedule owners can find and maintain it when required. * * * ## Eligible Altus Projects You can link an MPP file to an Altus Project where: - The Project uses the **Microsoft Project** Schedule Type or is otherwise eligible to transition from the native Altus Schedule Type - The Project is not already connected to another external scheduling tool - The Project does not already contain Tasks - You have access to the Project - You have permission to use Altus for Project > **Important:** > An Altus Project cannot normally be linked to an MPP file if it already contains Tasks or is connected to another external scheduling tool. > > Existing Tasks must be reviewed before changing the Schedule Type because establishing Microsoft Project as the schedule source can affect the Project’s existing schedule data. * * * ## Create an Altus Project for a Microsoft Project Schedule 1. Navigate to the Altus **Projects** list. 2. Select **\+ New**. 3. Complete the required Project fields. 4. Select **Microsoft Project** from the **Schedule Type** or **Project Schedule** dropdown. 5. Review the Next Steps information displayed in the form. 6. Select **Create**. The Project is created as a Microsoft Project external schedule Project. Until an MPP file has been linked and published, the Project may continue to display a **Next Steps** message. > **Important:** > The **Tasks** tab may temporarily be unavailable after selecting Microsoft Project as the Schedule Type. > > This is expected while the Project is waiting for an MPP file to be linked and published for the first time. * * * ## Understand the Microsoft Project Indicator in Altus After the MPP file has been linked, an indicator may appear within the Altus Project showing that Microsoft Project is the external schedule source. > **Important:** > The Microsoft Project indicator is **informational only**. > > It confirms that the Altus Project is linked to a Microsoft Project schedule, but it does not: > > - Open the underlying MPP file > - Show where the MPP file is stored > - Provide a link to the MPP file > - Launch Microsoft Project > > To update the schedule, the schedule owner must locate and open the linked MPP file from its approved storage location. * * * ## Prepare a Project Online MPP File If your organisation has moved from Project Online to Altus, the MPP file must be treated as a local file before it can be used with Altus for Project. Before linking: 1. Open the MPP file in Microsoft Project. 2. Select the **File** menu. 3. Review the connected account. 4. Open **Manage Accounts**. 5. Remove or stop using the previous Project Web App connection where required. 6. Set **Computer** as the default account. 7. Save and manage the MPP file locally or in your organisation’s approved OneDrive or SharePoint location. > **Important:** > An MPP file that remains connected to Project Online or Project Server cannot be published to Altus using the Altus for Project add-in. > > Follow your organisation’s migration and document-storage process when converting an existing Project Online schedule to a local MPP file. * * * ## Link the MPP File to Altus for the First Time The first time you link an MPP file, you must select the Altus environment containing the required Project. 1. Locate the MPP file in its approved storage location. 2. Open the saved MPP file in Microsoft Project. 3. Select the **Altus** ribbon. 4. Select **Linked Project Settings**. 5. Select **Link Altus Project**. 6. Sign in using the required Microsoft account if prompted. 7. Select the Altus environment. 8. Select **Next**. 9. Wait while Altus locates the Projects available to you. 10. On the **Select Altus Project** screen, select the required Project. 11. Confirm the link. The MPP file now stores its relationship with the selected Altus Project. > **Tip:** > The selected environment is remembered for later connections. You do not normally need to choose it again unless you want to connect to a different Altus environment. > **Important:** > Confirm that you have opened the correct MPP file before linking it. > > The Microsoft Project indicator that later appears in Altus will not allow users to locate or reopen the file. * * * ## Understand Unavailable Projects The Project selection screen displays Projects that are eligible for linking and that you have permission to access. Select **Show unavailable projects** to review Projects that cannot currently be selected. A Project may be unavailable because: - You do not have access to it - It is already linked to an external scheduling tool - It already contains Tasks - Your security access does not permit the connection - The Project does not meet the required Schedule Type conditions > **Tip:** > If the required Project does not appear, select **Show unavailable projects**. The displayed status may help identify why the Project cannot be linked. If the Project remains unavailable, contact your Altus administrator or implementation partner. * * * ## Connect the Linked MPP File to Altus After linking the file: 1. On the **Altus** ribbon, select **Connect to Altus**. 2. Sign in if prompted. 3. Wait for the connection process to complete. 4. Review the confirmation message. Connecting enables the other Altus for Project actions available for the linked schedule. Depending on configuration, the connection process can also refresh relevant Altus resource information in the MPP file, including: - Resource calendars - Calendar exceptions - Resource rates - Other configured resource information > **Important:** > You must connect the MPP file to Altus before publishing Tasks, managing Altus resources, or importing approved timesheet Actuals. > > Connect each time you reopen the MPP file and need to exchange updated information with Altus. If the connection fails: - Confirm that you are signed in with the correct Microsoft account - Confirm that you have access to the Altus environment - Confirm that the MPP file remains linked - Try connecting again - Contact your Altus administrator if the issue continues Permission to use Altus for Project can be controlled through Altus settings. * * * ## Connect to a Different Altus Environment To change the environment used by the add-in: 1. Locate and open the linked MPP file from its saved location. 2. Select the **Altus** ribbon. 3. Open **Linked Project Settings**. 4. Select **Link Altus Project**. 5. On the **Select Altus Project** screen, select **Change Environment**. 6. Select the required Altus environment. 7. Select **Next**. 8. Select the required Altus Project. 9. Confirm the new link. 10. Select **Connect to Altus**. > **Important:** > Changing the linked Project or environment must be handled carefully. > > Confirm that you are linking the correct MPP file, environment, and Altus Project before continuing. The **Tasks** tab may remain temporarily unavailable until the MPP file is published to the newly linked Project. * * * ## Publish the MPP Schedule to Altus Publishing sends the Tasks from the linked Microsoft Project schedule to the Altus Project. The MPP file must already be linked and connected before publishing. 1. Locate the linked MPP file in its approved storage location. 2. Open the file in Microsoft Project. 3. Select the **Altus** ribbon. 4. Select **Connect to Altus** if the active connection has not already been established. 5. Select **Publish Tasks**. 6. Monitor the **Processing Tasks** window. 7. Review any warnings or errors displayed. 8. When publishing is complete, select **Close**. After the first successful publish: - Tasks become available in the Altus Project - The **Tasks** tab becomes available - The external schedule indicator appears in the Project Details - Published Tasks are read-only in Altus > **Important:** > Microsoft Project remains the source of truth for published Task information. > > To change a published Task: > > 1. Locate and open the linked MPP file. > 2. Update the Task in Microsoft Project. > 3. Save the MPP file. > 4. Connect to Altus. > 5. Publish the schedule again. > > Do not attempt to maintain the published schedule directly in Altus. * * * ## Keep the Schedule Current The MPP file is normally linked to the Altus Project once. Ongoing schedule maintenance occurs from the linked MPP file. Before continuing, locate and open the linked MPP file from its saved location. You cannot launch the file from the Altus Project. 1. Locate the linked MPP file in its approved storage location. 2. Open the file using Microsoft Project. 3. Select the **Altus** ribbon. 4. Select **Connect to Altus**. 5. Review any refreshed Altus resource information. 6. Update the schedule in Microsoft Project. 7. Save the MPP file. 8. Select **Publish Tasks** when the updated schedule must be reflected in Altus. > **Important:** > Connecting and publishing are separate actions. > > Connect whenever you open the file and need to use Altus for Project features. Publish after making schedule changes that must flow to Altus. Unlike Project Online, there is no requirement to check out, check in, or force check in the schedule through Altus. * * * ## Manage the MPP File Location The linked MPP file should be stored in a location that supports continuity, access, and governance. The schedule owner should ensure that: - The approved storage location is documented - The file can be found when schedule updates are required - Appropriate backup and version-management processes are followed - Another authorised person can locate the schedule if the primary owner is unavailable - Schedule ownership is transferred when responsibilities change - The file is not moved or renamed without following the organisation’s file-management process > **Important:** > Altus does not display the MPP file path or provide a button to launch the linked file. > > The existence of the Microsoft Project indicator does not guarantee that other users know where the MPP file is stored. > **Best Practice:** > Record the approved schedule location in your Project documentation, schedule-management plan, handover notes, or another organisation-approved location. > > Avoid relying on one person’s memory or a local computer path that other authorised schedule owners cannot access. * * * ## Schedule Ownership and Handover When schedule ownership changes: 1. Confirm the location of the linked MPP file. 2. Confirm that the incoming schedule owner has access to the file. 3. Confirm that the incoming owner has Microsoft Project and the Altus for Project add-in. 4. Confirm that the incoming owner has access to the Altus environment and Project. 5. Explain the existing Link, Connect, and Publish process. 6. Review any outstanding schedule updates or unpublished changes. 7. Confirm the organisation’s backup and file-management process. > **Important:** > The Altus Project record does not replace the schedule handover. > > A new schedule owner may be able to see that the Project is linked to Microsoft Project but still be unable to maintain the schedule without knowing where the MPP file is stored. * * * ## Understand Published Task Behaviour Tasks published from Microsoft Project are read-only in Altus. This ensures that Microsoft Project remains the authoritative schedule source. Published information may include: - Task names - Start and Finish Dates - Duration - Effort - Remaining Effort - Effort Completed - Percentage Complete - Resource assignments - Milestones - Task hierarchy - Due Dates - Other configured fields > **Tip:** > Use the Altus Tasks view for visibility, reporting, timesheet availability, and wider collaboration. > > Make schedule changes in the linked MPP file, then connect and publish again. * * * ## Manage Altus Resources Before Publishing Where resources are assigned to Tasks, use the Altus for Project resource-management features to add or map the appropriate Altus resources. This helps ensure that: - Task assignments use recognised Altus resources - Assigned Tasks can become available for timesheet entry - Resource data remains consistent between Microsoft Project and Altus - Approved timesheet Actuals can be matched correctly Refer to the [Altus for Microsoft Project End User Guide](https://docs.altus.pro/solutions/AltusForProject/Help.html#index) for detailed Build Team and resource-management guidance. * * * ## Avoid Using Save As for Linked MPP Files Using **Save As** in Microsoft Project creates a new MPP file version with new Task and assignment identifiers. Publishing that newly saved file against the same Altus Project may: - Delete and recreate Tasks - Remove resource mappings - Disconnect previously completed timesheet entries - Disrupt the existing Task relationship > **Warning:** > Avoid using **Save As** to create a backup of an MPP file that has already been linked to Altus. > > To create a backup, copy the file using Windows File Explorer or your organisation’s approved file-management process. A copy created after the original file was linked may retain the linking information. A copy created before linking does not contain the established Altus relationship. > **Important:** > Where copies exist, clearly identify the authoritative linked MPP file and its approved location. > > Avoid having multiple users unknowingly maintaining different copies of the same schedule. * * * ## Understand Microsoft Project Baselines Baselines stored in the MPP file are not published to Altus through the standard Task publishing process. After publishing the Tasks, use the Altus baseline functionality where an Altus schedule baseline is required for reporting or variance tracking. > **Important:** > Microsoft Project baselines and Altus baselines are separate. > > Follow your organisation’s baseline governance process when establishing the reportable baseline in Altus. * * * ## Check Microsoft Project Milestones Altus identifies a Microsoft Project milestone based on its duration. A milestone must have a duration of **0 days** to publish as a milestone in Altus. If the duration is not 0 days, Altus treats the item as a Task. > **Tip:** > Review milestone durations in Microsoft Project before publishing to ensure they appear correctly in Altus. * * * ## Import Approved Timesheet Actuals Where Altus Timesheets are used, approved timesheet hours can be reviewed and imported into the linked Microsoft Project Plan. 1. Locate and open the linked MPP file. 2. Connect the file to Altus. 3. Select the applicable timesheet import action from the **Altus** ribbon. 4. Review the available approved timesheet Actuals. 5. Select the appropriate entries. 6. Apply the Actuals to the Microsoft Project schedule. 7. Review the effect on Task progress, Remaining Work, and Project dates. 8. Save the MPP file. 9. Publish the updated schedule back to Altus. > **Important:** > Approved timesheet data must be imported into the linked MPP file. > > The Microsoft Project indicator in Altus does not provide access to the file or initiate the timesheet import. Refer to the [Altus for Microsoft Project End User Guide](https://docs.altus.pro/solutions/AltusForProject/Help.html#index) for detailed timesheet-import guidance. * * * ## Unlink the MPP File After an MPP file has been published, it can be unlinked from the Altus Project. Depending on the selected unlinking option and your organisation’s process, published Tasks may be retained in Altus so that the schedule can transition to native Altus Task management. Use this capability carefully when: - Migrating from Microsoft Project to native Altus scheduling - Changing the schedule source - Retiring an MPP file - Resolving an incorrect connection Refer to the [Altus for Microsoft Project End User Guide](https://docs.altus.pro/solutions/AltusForProject/Help.html#index) for current unlinking guidance. > **Important:** > Confirm the intended schedule ownership before unlinking. > > Once the schedule becomes native to Altus, future Task maintenance should follow the native Altus scheduling process. > > Retain or archive the previous MPP file according to your organisation’s records-management requirements. * * * ## Troubleshooting ### The Altus Ribbon Is Missing Confirm that: - Altus for Project is installed - Microsoft Project meets the supported requirements - The add-in is enabled in Microsoft Project - Your organisation permits the add-in - An older add-in version is not preventing activation Refer to the [Altus for Project deployment and activation guidance](https://docs.altus.pro/solutions/AltusForProject/Deployment.html?tabs=Admin%2CGA#microsoft-office-add-in-activation). * * * ### The Altus Project Is Missing Confirm that: - You have access to the Project - You belong to the required Project group - The Project does not already contain Tasks - The Project is not linked to another external schedule - The correct Altus environment is selected Select **Show unavailable projects** for additional information. * * * ### The Tasks Tab Is Missing The Tasks tab may be unavailable when: - The Project has been configured for Microsoft Project but no file has been linked - The MPP file has been linked but has not yet been published successfully - The Schedule Type or external Project connection is incomplete Locate and open the linked MPP file, connect to Altus, publish the schedule, then reopen the Altus Project. * * * ### The Tasks Are Read-Only This is expected for Tasks published from Microsoft Project. Locate and open the linked MPP file, update the Tasks in Microsoft Project, then connect and publish the schedule again. * * * ### The Microsoft Project Indicator Does Not Open the File This is expected. The indicator confirms that the Project is linked to a Microsoft Project schedule, but it does not: - Launch Microsoft Project - Open the MPP file - Display the file path - Provide the storage location Contact the Project Manager, schedule owner, PMO, or relevant administrator to identify the approved file location. * * * ### The MPP File Cannot Be Found If the linked MPP file cannot be located: 1. Check the Project documentation and schedule-management records. 2. Check approved OneDrive and SharePoint locations. 3. Contact the current or previous schedule owner. 4. Check whether the file was stored on a local computer. 5. Confirm whether an approved backup exists. 6. Contact your PMO or administrator if the authoritative file cannot be identified. > **Important:** > Do not link a replacement or copied MPP file without confirming that it is the correct authoritative schedule. > > Linking or publishing the wrong file can affect Task relationships, resource mappings, and timesheet information. * * * ### The Connection Fails Confirm: - Internet and organisational network access - The signed-in Microsoft account - Access to the required Altus environment - Permission to use Altus for Project - The active link between the MPP file and Altus Project Retry the connection, then contact your administrator if the issue continues. * * * ## Key Considerations - Microsoft Project remains the source of truth for a linked MPP schedule. - The schedule owner must know where the linked MPP file is stored. - The Microsoft Project indicator in Altus is informational only. - The MPP file cannot be opened directly from the Altus Project. - The linked MPP file must be opened from its saved location using Microsoft Project. - The approved storage location should be documented and accessible to authorised schedule owners. - The MPP file must be saved locally or in an accessible OneDrive or SharePoint location. - Files still connected to Project Online or Project Server cannot be published through Altus for Project. - Link, Connect, and Publish are separate actions. - A Project cannot normally be linked if it already contains Tasks or uses another external schedule. - The Tasks tab may be unavailable until the first successful publish. - Published Tasks are read-only in Altus. - Connect before publishing, managing resources, or importing timesheet Actuals. - Publish schedule changes regularly to keep Altus current. - Do not use Microsoft Project **Save As** as the backup method for a linked file. - Clearly identify the authoritative linked MPP file where copies exist. - Microsoft Project baselines are not published to Altus. - Milestones require a duration of 0 days. - Access to the add-in and linking process may be restricted by an administrator. - Schedule handover must include the file location and access arrangements. - Unlinking should follow your organisation’s schedule-transition process. * * * ## Tips - Confirm the correct Altus environment before linking. - Use **Show unavailable projects** when the required Project cannot be selected. - Store the linked MPP file in your organisation’s approved location. - Record the file location in the Project’s schedule-management or handover documentation. - Ensure another authorised person can locate the file if the primary schedule owner is unavailable. - Do not interpret the Microsoft Project indicator as a link to the file. - Connect to Altus each time you open the file and need to use add-in features. - Save the MPP file before publishing. - Publish after meaningful schedule updates. - Maintain published Tasks in Microsoft Project, not Altus. - Use Build Team to manage recognised Altus resources. - Copy the MPP file through File Explorer for backup instead of using **Save As**. - Avoid moving or renaming the linked file without following your organisation’s file-management process. - Review milestone durations before publishing. - Follow internal governance before changing the linked Project, environment, file location, or schedule source.