Project For The Web Admin Help

Contents
Admin home
Get started
Project for the web get started guide for admins
Deploying Project for the web
Scheduling modes
Turn Project for the web or Roadmap on or off
Project architecture overview
Project for the web limits and boundaries
Office 365 user view access to Project for the web and Roadmap
Remove Project from the Office 365 App Launcher
Project for the web setup requirements for business units
Frequently Asked Questions
Resource management
Create and apply a work calendar in Project for the web
Create non-user resources in Project for the web
Overview of Universal Resource Scheduling in Project for the web
Maintain user data
Learn about Dataverse security roles in Project for the web
Access a project in Project for the web after its Office 365 group has been deleted
Export user data from Project for the web
Delete user data from Project for the web
Handling data for Project
Remove Project for the web or Roadmap from Office 365
Release notes
Project Service Core solution version history
Roadmap's Portfolio service solution version history
Project for the web admin help
2/9/2022 • 2 minutes to read • Edit Online
Learn about resources available for Project for the web admins.
IC O N TO P IC IC O N TO P IC IC O N TO P IC
Get started with What is Project Project for the

Project for the for the web? web and Project
web for admins Online
Project Project for the Project for the

UserVoice web API web end user
help
Featured articles
Project for the web get started guide for admins
Turn Project for the web off for users in your organization
Connect to Project for the web data through Power BI Desktop
Project for the web get started guide for
administrators
Project for the web is a new service that is now available to Office 365 users. You can make it available to your
users through the following licenses:
Project Plan P1
Project Plan P3 (previously called Project Online Professional)
Project Plan P5 (previously called Project Online Premium)
If your users are currently using Project Online Professional or Project Online Premium licenses, Project for the
web is available to them now.
This article provides administrators with information to help them better understand and manage the service.
Learn more about Project for the web

The follow can be helpful to you if you are an admin who wants to learn more about Project for the web. It can
be especially helpful if your organization currently uses Project Online or the Project Online Desktop Client.
What is Project for the web?
What can you do with Project for the web?
Project for the web and Project Online
Project for the web and Project Online desktop client
Customizing Project for the web
Microsoft Project Service Description
Turn off Project for the web for specific users

If your organization currently uses Project Online Professional (renamed to Project Plan P3) or Project Online
Premium (renamed to Project Plan P5), users with these licenses will automatically get Project for the web. If you
are not ready to make Project for the web available to some of these users, you can turn it off. Learn how to turn
off Project for the web in Turn off Project for the web.
Help your users

Project for the web is designed to be easy-to-use and intuitive. You can use the following articles, quick starts,
and videos to help your users learn how to better use Project for the web.
QuickStart guide: Create your project
QuickStart guide: Build your project
QuickStart guide: Manage your project
Share a project in Project for the web
Project training
Reporting information on Project for the web data

Project for the web data is stored in your Dynamics 365 Dataverse default instance. You can view Power BI
reports by connecting to the data with Power BI Desktop, which is described in the following article:
Connect to Project data through Power BI Desktop.
Dataverse
Your Project for the web and Roadmap data is stored in Dataverse (formerly Common Data Service).
Initial use of Project for the web or Roadmap in your tenant will automatically create the default Dataverse
instance. Administrators have the option to deploy Project to more environments.
Resource setup in PowerApps

While sharing and access to your project in Project for the web is done through Office 365 groups, it is
important to note that Project for the web uses the PowerApps platform. Some resource setup tasks such as
adding non-user resources or creating a work schedule template and applying it to resources are done in
PowerApps.
Searching for user data for Project for the web

If you need to find a specific user's data in Project for the web (for example, all project the user owned or
created), you can find that information in the following articles:
See Also
Project for the web is available for use in the Default Environment and in Sandbox and Production Dataverse
environments.
Project for the web in the Default environment enables customers to quickly get started creating projects,
managing schedules, and sharing them with other users in the organization. Because everyone is a member of
this environment by default, enabling users to create and manage Projects only requires that you assign a
Project license to them.
For some situations, you should consider deploying Project to additional environments. These are:
Customizing Project to behave differently for different business units
Application Lifecycle management (Development/Test/Production)
If you are looking to deploy to additional environments, you will need to create the environments, deploy
Project, and configure access for users.
Learn more about Dataverse environments.
Deploying to the Default environment
Deployment of Project to the Default environment is done for you automatically. When Project for the web or
Roadmap is first used in an Office 365 tenant, a Default Dataverse instance is provisioned for the tenant and the
solutions are deployed.
Provisioning a new environment

NOTE
This section only applies to Admins interested in deploying Project to a non-Default environment.
Project is supported in the following types of environments:

Default
Production
Sandbox
To be able to deploy to Sandbox and Production environments, the environment needs to be created with a
database and the "Enable Dynamics 365 Apps" toggle must be disabled .
NOTE
If you set a security group for the environment, only the users in that group will be able to view those projects and other
information of the environment. Additionally, tasks can only be assigned to users in that group.
Learn more about creating and managing environments.

Deploying Project to the environment
Once the environment is created, you can deploy Project to the environment from within the Power Platform
Admin Center (PPAC).
Open the Resources > Dynamics 365 apps page from the left-hand navigation menu. Then, install the
Project Ser vice Core package into your environment.
NOTE
If the installation package isn't appearing in the list of available packages, either the tenant doesn't have a Project license,
or the environment was created with the "Enable Dynamics 365 Apps toggle" enabled.
Learn more about using the PPAC to deploy applications.
Configuring Roles and Security

Sandbox and Production environments require additional configuration. Assign the Project Common and
Project User roles to anyone who will be creating Projects in the environment. Also, ensure these users have
the appropriate Project license.
There is no additional configuration needed to enable users to manage Projects in the Default environment.
Users in the Default environment only need a Project license to be able to create and manage Projects.
Learn more about Project’s security roles.
NOTE
Project-related roles are only available after the Project Service Core package has been deployed to the environment.
Creating and managing projects in non-Default environments

In non-Default environments, projects are created and managed via the Project Power App. Users with the
Project User and Project Common roles will see the Project app tile appears in Office.com – All Apps section.
Deploying an environment to a different Geography

All environments will be created in the geography where the tenant was initially created. To create an
environment in a different geography, you will need to contact your Microsoft Sales Representative or Reseller
to get this enabled.
Learn more about managing multiple environments.
Troubleshooting
System requirements
To provision and use Project for the web, there are system prerequisites that are expected to be on. These pre-
requisites are enabled by default. The details of these system prerequisites are provided in the table below.
Enterprise applications
The following enterprise applications should be enabled:
A P P L IC AT IO N N A M E A P P L IC AT IO N ID
Dynamics Provision 39e6ea5b-4aa4-4df2-808b-b6b5fb8ada6f
Common Data Service 00000007-0000-0000-c000-000000000000
Microsoft Flow 7df0a125-d3be-4c96-aa54-591f83ff541c

A P P L IC AT IO N N A M E A P P L IC AT IO N ID
Microsoft PowerApps 475226c6-020e-4fb2-8a90-7a972cbfc1d4
Dynamics CRM Online Administration 637fcc9f-4a9b-4aaa-8713-a2a3cfda1505
Project Online f53895d3-095d-408f-8e93-8f94b391404e
Verifying status of Enterprise applications

To verify whether the required Enterprise applications are enabled, perform the following steps:
1. Sign in to as the tenant admin using https://aad.portal.azure.com/
2. Click Enterprise Applications . The Enterprise applications screen appears.
3. From the Application Type dropdown, choose All Applications and click Apply .
4. Use the textbox right below and search for the application ID listed in the table. For example, 39e6ea5b-
4aa4-4df2-808b-b6b5fb8ada6f . The application Dynamics Provision is displayed in the result pane.
5. Click Dynamics Provision . The Dynamics Provision screen appears.
6. Click Proper ties on the left pane.
7. Ensure that Enabled for users to sign-in is set to Yes .

8. Repeat Steps 1-7 for each of the Enterprise applications listed above.
Verifying status of required Enterprise applications using Azure Active Director y PowerShell for
Graph
For administrators who prefer using Azure Active Directory PowerShell for Graph instead of the above manual
steps, they can use the following script to check if the above list of Applications is enabled. In addition, it also
checks to ensure that the required Enterprise Apps exist and the AppRoleAssignmentRequired property is
correctly set:
Connect-AzureAd
$ProjectRequiredApps = Get-AzureADServicePrincipal -Filter "

AppId eq '00000007-0000-0000-c000-000000000000'
or AppId eq '475226c6-020e-4fb2-8a90-7a972cbfc1d4'
or AppId eq '637fcc9f-4a9b-4aaa-8713-a2a3cfda1505'
or AppId eq '7df0a125-d3be-4c96-aa54-591f83ff541c'
or AppId eq '39e6ea5b-4aa4-4df2-808b-b6b5fb8ada6f'
or AppId eq 'f53895d3-095d-408f-8e93-8f94b391404e'
"
$ProjectRequiredApps | Select DisplayName, AppID, ObjectID, AccountEnabled, AppRoleAssignmentRequired,

ReplyURLs | ft
#Check that all required Enterprise Apps are present. Create hashtable to check that app exists and if so
remove from list. Entries left behind means it's missing.
[hashtable]$EntApps = [ordered]@{"Dataverse" = "00000007-0000-0000-c000-
000000000000"
"Microsoft Flow Service" = "7df0a125-d3be-4c96-aa54-
591f83ff541c"
"Dynamics Provision" = "39e6ea5b-4aa4-4df2-808b-
b6b5fb8ada6f"
"Dynamics CRM Online Administration" = "637fcc9f-4a9b-4aaa-8713-
a2a3cfda1505"
"PowerApps Service" = "475226c6-020e-4fb2-8a90-
7a972cbfc1d4"
"Portfolios" = "f53895d3-095d-408f-8e93-
8f94b391404e"
}
Foreach ($App in $ProjectRequiredApps) #Remove from hashtable if app exist.

{
If ($EntApps.Item($App.DisplayName))
{
$EntApps.Remove($App.DisplayName)
}
}
If ($EntApps.Count -gt 0)
{
Write-Host "Check#1: One or more required Enterprise Apps are missing." -ForegroundColor Red
Write-Host "Please check that you have 1 or more of the following subscriptions: Project Plan 1, Project
Plan 3 or Project Plan 5." -ForegroundColor Red
$EntApps | ft -a
}
else
{
Write-Host "Check#1: All required Enterprise Apps are present." -ForegroundColor Yellow
}
#Check that required apps are enabled (AccountEnabled=True) if not display message to enable the required
Enterprise Apps.
If ($ProjectRequiredApps | ? {$_.AccountEnabled -eq $false})
{
Write-Host "Check#2: The following required AAD Enterprise App is disabled."
Write-Host "Instructions on how to enable the required app via Azure Active Directory Admin Center are at:
Write-Host "Instructions on how to enable the required app via Azure Active Directory Admin Center are at:
https://docs.microsoft.com/project-for-the-web/deploying-project" -ForegroundColor Red
Write-Host "If you prefer using Powershell, for each App in the list use the Powershell cmdlet ""Set-
AzureADServicePrincipal"" to enable the app." -ForegroundColor Red
Write-Host "Example:`n" -ForegroundColor Red
Write-Host " Set-AzureADServicePrincipal -ObjectId "“ObjectId GUID from below output."”-AccountEnabled
`$true" -ForegroundColor Red
Write-Host "`nMore info on the cmdlet ""Set-AzureADServicePrincipal can be found"" at:
https://docs.microsoft.com/en-us/powershell/module/azuread/set-azureadserviceprincipal" -ForegroundColor Red
$ProjectRequiredApps | Select DisplayName, AppID, ObjectID, AccountEnabled | ? {$_.AccountEnabled -eq
$false} | ft
}
Else
{
Write-Host "Check#2: All required Enterprise Apps are enabled." -ForegroundColor Yellow
}
#Check that AppRoleAssignmentRequired for all required apps is set to False

(AppRoleAssignmentRequired=False).
If ($ProjectRequiredApps | ? {$_.AppRoleAssignmentRequired -eq $true})
{
Write-Host "Check#3: The AppRoleAssignmentRequired property for the specified Enterprise App is set to
True." -ForegroundColor Red
Write-Host "Out of box this setting should be set to False. If set to True, it can prevent Project for the
Web from working correctly." -ForegroundColor Red
Write-Host "This setting can only be modified via Powershell, for each App in the list use the Powershell
cmdlet ""Set-AzureADServicePrincipal"" to change the AppRoleAssignmentRequired to False." -ForegroundColor
Red
Write-Host "Example:`n" -ForegroundColor Red
Write-Host " Set-AzureADServicePrincipal -ObjectId "“ObjectId GUID from below output."”-
AppRoleAssignmentRequired `$false" -ForegroundColor Red
Write-Host "`nMore info on the cmdlet ""Set-AzureADServicePrincipal can be found"" at:
https://docs.microsoft.com/en-us/powershell/module/azuread/set-azureadserviceprincipal" -ForegroundColor Red
$ProjectRequiredApps | Select DisplayName, AppID, ObjectID, AccountEnabled, AppRoleAssignmentRequired | ?
{$_.AppRoleAssignmentRequired -eq $true} | ft -a
}
Else
{
Write-Host "Check#3: The AppRoleAssignmentRequired property for all required Enterprise Applications are
set correctly." -ForegroundColor Yellow
}
Scheduling modes
Project for the web enables administrators to define how their organization manages key variables in project
tasks. Based on the specific needs of the organization, administrators can make changes to the scheduling mode
when a project is created.
Change your organization’s scheduling mode

Project for the web sets Fixed duration as the out-of-the-box default scheduling mode for all organizations.
However, administrators can choose a different default scheduling mode at the organizational level.
To change the scheduling mode for your organization, perform the following steps:
1. Launch the Power Apps portal.
2. On the bottom-left corner in the navigation pane, click Projects .
3. Navigate to Settings > General > Parameters , and then select the project parameter. The Project
Parameters page appears.
4. Choose the scheduling mode that you want to apply from the Schedule Mode field, to make it the
default one.
Enable project managers to override default scheduling mode

Administrators can determine if project managers can override the default scheduling mode on their projects. To
enable the override, perform the following steps:
1. Choose Settings > General > Parameters , and then select the project parameter. The Project
Parameters page appears.
2. Set Project Level Schedule Mode Override Permitted to Yes .
NOTE
If this setting is set to No , all projects in the organization will have the organization’s default scheduling mode.
If this setting is set to Yes , project managers can override the default scheduling mode setting & set a custom scheduling
mode on their projects.
Project Manager
A project manager creates a project and is, therefore, entitled to change the default scheduling mode for that
project.
Changing the scheduling mode setting on a project
To change a project's default scheduling mode, perform the following steps:
1. Create a new project in the Project Power app. Once the project is created, its summary page appears.
2. Navigate to the Schedule Mode setting.
3. Change the scheduling mode to your desired mode.
4. Save the changes.
NOTE
The scheduling mode can only be edited while a project is being created. After your project has been saved, you cannot
edit the scheduling mode.
Even when this parameter is set to Yes , you can only change the scheduling mode for the project; you cannot change the
scheduling mode of individual tasks.
Copy projects
A project manager has the privilege to create projects by cloning from an existing project. If the newly created
project is a cloned one, the project manager can't set the scheduling mode. The destination project will always
default to the mode defined at the organizational level.
Copy tasks
A project manager has the privilege to copy a task from one project to another. Such cloned tasks inherit the
scheduling mode of the destination project.
The following three scheduling modes are available in a project:
Fixed duration (default)
Fixed effort
Fixed unit
The values affected by the definition of a specific scheduling mode are determined by the following formula:
Effort = Duration x Units
When you define a project’s scheduling mode, you are setting one of these values to remain unchanged.
Holding this value as a constant places a priority on that value, which notifies the system not to change it when
the other two values change. The following table provides information about the impacts of selecting a specific
mode:
IN T H IS TA SK IF Y O U REVISE UN IT S IF Y O UR REVISE DURAT IO N IF Y O U REVISE EF F O RT
Fixed units task Duration is recalculated Effort is recalculated Duration is recalculated
Fixed effort task Duration is recalculated Units are recalculated Duration is recalculated
Fixed duration task Effort is recalculated Effort is recalculated Units are recalculated
For more information about the implications of a given mode, see Change the task type for more accurate
scheduling.
NOTE
In the topic, the term Work is used instead of Effor t .
Turn Project for the web or Roadmap on or off for
users in your organization
Access to Project for the web is available to users if they are assigned one of the following licenses:
Project Plan 1
Project Plan 3 (previously called Project Online Professional)
Project Plan 5 (previously called Project Online Premium)
Users who have Project Plan 3 and Project Plan 5 licenses have access to not only Project Online and the Project
Online Desktop Client, but also Project for the web and Roadmap.
NOTE
Users only have read-only access to Roadmap through the Project Plan 1 license.
How admins can control access to Project for the web and Roadmap
An Office 365 admin may want to control user access to Project for the web or Roadmap in their Office 365
tenant for various reasons. For example:
An admin may want to turn on Project for the web for the organization, but turn it off for a some users
who currently work exclusively in Project Online.
An admin may want to turn off Project for the web temporarily to all users so that they can roll it out
gradually.
The admin may want to turn the Roadmap feature on to all users in the tenant, even if Project for the web
is turned off.
The admin may want to only provide Project for the web and Roadmap to specific users, and does not
want to give them access to Project Online.
This article describes how admins can use do the following to address the above and similar scenarios:
Turn Project for the web on or off for all users
Turn Project for the web on or off only for specific users
Turn the Roadmap feature on or off to all users
Turn off Project Online to specific users
Turn Project for the web on or off for all users in your organization
An admin can turn Project for the web on or off for all users in their organization through the Project settings
page in the Microsoft 365 admin center.
IMPORTANT
This setting is only available in the new Microsoft 365 admin center. If you are using the classic admin center, you will
need to switch to the new Microsoft 365 admin center to access this setting.
To turn on or off Project for the web:

1. In the Microsoft 365 admin center, expand the navigation menu, select Settings , and then select Org
Settings .
2. Select Project .
3. On the Project settings page, select or deselect Turn on Project for the web for your organization , and
then click Save changes .
If an admin tries to access the Project settings page and receives the error message Unable to retrieve settings,
have a licensed user go to their Project Home page (project.microsoft.com). This will initiate Project for the web
on the tenant and will make the Project settings available for the admin.
IMPORTANT
Currently, if you turn on Project for the web, actual activation on your tenant will happen at a later date (see your
Message Center for more details).
IMPORTANT
Turning Project for the web on or off will have no effect on your ability to use Project Online.
Project for the web is not turned on for your organization

If your licensed users were previously able to use Project for the web, but are no longer able to, you can resolve
this by turning on Project for the web in the steps described above.
The problem will appear as:
Your users will no longer see the New blank project option on the Project Home page.
When opening a project, users will see the error Project is not turned on for your organization .
Turn off Project for the web for specific users in your organization
An admin can manage access to Project for the web for specific users by turning off the service for their
associated Project Plan licenses. This assumes that that Project for the web is turned turned on for the
organization in the Project settings page in the Microsoft 365 admin center.
If you want to turn off Project for the web for specific users in your organization, an admin can do this by
turning off the Project P3 service for the user in the Microsoft 365 Admin Center.
You might want to do this if your users currently use Project Online (through Project Plan P3 or Project Plan P5
licenses) and you don't want to give all of your users access to Project for the web at the moment.
NOTE
Turning off Project for the web for the individual user will also turn off the Roadmap feature for them, even if the Roadmap
admin setting is turned on.
To turn off Project for the web for a user:

1. In the Microsoft 365 Admin Center, select Users , then select Active Users .
2. From the Active users list, select the checkbox next to the user, and then click Manage product
licenses .
3. On the user information page, select the licenses and app tab, in the Apps section, select the user's
Project Online license from the Show apps for drop down menu. This would be either Project Online
Professional or Project Online Premium.
4. In the list of apps that display, uncheck Project P3 , and then click Save changes .
You can repeat this procedure for each user that you don't want to use Project for the web.
IMPORTANT
The service plan that disables Project for the web is called Project P3 . It is important to distinguish it from Project Plan
3 , which is one of the three licenses in which Project for the web is available. Project Plan 1, Project Plan 3, and Project
Plan 5 are all licenses that have the Project P3 service plan.
Turn Project for the web off for multiple users using Windows PowerShell
If you need to turn off Project for the web for a large number of users, it may be easier for an admin to do this
through Windows PowerShell instead of through the Microsoft 365 admin center.
NOTE
Before attempting this, you first need to install the required modules and be a global admin on your tenant.
Also, when you open Windows PowerShell, make sure to run as an administrator.
1. In Windows PowerShell, type and enter the following to sign into your tenant.
Connect-MsolService
2. Type the following to find the AccountSkuId of your Project Online licenses.
Get-MsolAccountSku
You should see a list of the licenses available on your tenant, for example:
3. Look for the accountSKUid values that contain PROJECTPREMIUM or PROJECTPROFESSIONAL .

PROJECTPREMIUM is Project Plan 5 (Project Online Premium)
PROJECTPROFESSIONAL is Project Plan 3 (Project Online Professional)
The value will be prefixed by the tenant domain name. For example, in the image above, the
AccountSKUID value for the Project Online Premium license is M365x115998:PROJECTPREMIUM .
4. Create a $LicenseOption object that disables the Project P3 service plan (PROJECT_PROFESSIONAL) from the
Project Plan 3 and Project Plan 5 licenses (the AccountSKUID values).
In our example, the following will disable the Project P3 service plan in a Project Plan 5 license.
$LicenseOptionsPremium = New-MsolLicenseOptions -AccountSkuId "M365x115998:PROJECTPREMIUM" -DisabledPlans

"PROJECT_PROFESSIONAL"
If the tenant had Project Plan P3 licenses (Project Online Professional) , the following will disable it in that
license.
$LicenseOptionsProfessional = New-MsolLicenseOptions -AccountSkuId "M365x115998:PROJECTPROFESSIONAL" -

DisabledPlans "PROJECT_PROFESSIONAL"
5. After you've created the objects, create a list of your user accounts in which you'd like to disable Project for
the web. There are different ways to do this, such as importing from a CSV file. For our example, we'll create
a UPNList with the user accounts in which we want to disable Project for the web.
`$UPNList = @("AdeleV@M365x115998.OnMicrosoft.com","AlexW@M365x115998.OnMicrosoft.com")
6. After creating your list, apply the applicable $LicenseOption object to each user account.
For our example, we're applying the $LicenseOptionsPremium object to each user in the UPNList, which
would disable Project for the web from each user who has a Project Plan P5 license.
ForEach ($UPN in $UPNList)

{
Set-MsolUserLicense -UserPrincipalName $UPN -LicenseOptions $LicenseOptionsPremium
}
For more information about disabling services through Office 365 PowerShell, see Disable access to services
with Office 365 PowerShell.
Turn Roadmap on or off

An admin can do the following to turn Roadmap on or off for their organization:
1. In the Microsoft 365 admin center, expand the navigation menu, select Settings , and then select Settings .
2. Select Project .
3. On the Project settings page, select or deselect Turn on Roadmap for your organization , and then click
Save changes .
4. Project Roadmap may requires the Project Roadmap connector to be added to a Data Policy in the Power
Platform admin center. At the moment, the Project Roadmap connector does not show up in the GUI of the
Data Policy . Therefore, please follow along this guidance in order to add the Project Roadmap connector to
the data group Business in the desired Data Policy .
$userName = "<your username>"
$userPassword = "<your userpassword>"
$DlpDisplayName = "<your desired DLP Policy DisplayName"
# Connect to PowerApps
Add-PowerAppsAccount -Username $userName -Password $userPassword
# Get all Power Platform DLP policies (Data Policies)

Get-AdminDlpPolicy
# Set desired DLP policy to be modified

$DlpPolicy = Get-AdminDlpPolicy | Where-Object DisplayName -EQ $DlpDisplayName
# Get BusinessDataGropup connectors of specific DLP Policy and check for ConnectorId
'/providers/Microsoft.PowerApps/apis/shared_projectroadmap'
Get-AdminDlpPolicy -PolicyName $DlpPolicy.PolicyName | Select-Object –ExpandProperty BusinessDataGroup
# Add Connector "Project Roadmap" to BusinessDataGropup of DLP policy and check for Status 200 / Description
OK
Add-CustomConnectorToPolicy -PolicyName $DlpPolicy.PolicyName -ConnectorId
'/providers/Microsoft.PowerApps/apis/shared_projectroadmap' -GroupName hbi -ConnectorName "Project Roadmap"
-ConnectorType "Microsoft.PowerApps/apis"
# Verify DLP policy settings

Get-AdminDlpPolicy -PolicyName $DlpPolicy.PolicyName | Select-Object –ExpandProperty BusinessDataGroup |
Where-Object name -EQ "Project Roadmap"
Roadmap is not turned on for your organization

If your licensed users were previously able to use Roadmap, but are no longer able to, you can resolve this by
turning on Roadmap in the steps described above.
The problem will appear as:
Your users will no longer see the New Roadmap option on the Project Home page.
When opening a roadmap, users will see the error Roadmap is not turned on for your organization .
Turn Project Online off

An admin may want certain users to have access to Project for the web and the Roadmap feature, and not
Project Online. To do this, the admin would not only need to turn on Project for the web and Roadmap in Project
settings, but also need to turn off the Project Online service for the user through their assigned Project Plan 3 or
Project Plan 5 license.
To turn off Project Online:
1. In the Microsoft 365 Admin Center, select Users , then select Active Users .
2. From the Active users list, select the checkbox next to the user, and then click Manage product
licenses .
3. On the user information page, select the licenses and app tab, in the Apps section, select the user's
Project Online license from the Show apps for drop down menu. This would be either Project Plan 3
or Project Plan 5 .
4. In the list of apps that display, uncheck Project Online Ser vice , and then click Save changes .
You can repeat this procedure for each user that you want to use only Project for the web and Roadmap.
IMPORTANT
Turning Project Online on or off for a specific user will have no effect on their ability to use Project for the web.
See Also
This article gives you an overview of the logical architecture that exists for key apps that are provided in Project.
Key Project apps

The architecture diagram above shows the key apps that are available through Project Plan subscriptions:
Project for the web
Roadmap
Project Online
Project Online Desktop Client
For more information about features that are available through these project apps and services, see Feature
availability across apps and subscriptions in the Microsoft Project service description.
Project Plans
The key Project apps described in this article are available in the following Project Plans.
PLAN P RO JEC T P L A N 1 P RO JEC T P L A N 3 P RO JEC T P L A N 5
Project for the web Available Available Available
Roadmap Read-Only Available Available
Project Online Team member access Available Available
Project Online Desktop Not Available Available Available

Client
NOTE
In Project Plan 1, users can only view roadmaps in read-only.
For more information on Project Plans, see the Microsoft Project Service Description.
Project for the web

Project for the web provides simple, powerful work management capabilities to meet most needs and roles.
Project managers and team members can use Project for the web to plan and manage work of any size.
Platform
Project for the web is built on the Microsoft Power Platform. The Power Platform consists of PowerApps, Power
Automate, Power BI, and Dataverse. Integration with the Microsoft Power Platform lets you easily use its
components to create custom business solutions and do advanced analytics and reporting on project data.
Just like Project Online, users can access their Project for the web projects through the Project Home page. It will
by default list projects that were recently viewed, owned by, or shared with the user.
Data storage
Project for the web data is saved in Dataverse. Dataverse is part of the Microsoft Power Platform, which Project
for the web is built on.
Project for the web data is saved in entities in Solutions that are in a Dataverse instance, and can be identified by
their display name of Project .
Reporting
You can use PowerBI Desktop to import and analyze your Project for the web and Project Online data. You can
use the same Project Power BI template to view a Portfolio dashboard of reports that can be helpful in analyzing
your data.
Roadmap
Use Roadmap to create a collective view of projects that are important to you. Your roadmap can connect to
projects created in multiple tools, such as Project Online, Project for the web, and Azure DevOps.
Data storage
Roadmap data are saved to solutions in the Dataverse Default instance. While Project for the web data is saved
as entities in Project solutions, Roadmap data is saved to entities in Dataverse solutions that have a display
name of Por tfolio Ser vice .
Project Online
Project Online is a flexible online solution for Project Portfolio Management (PPM) and everyday work. Project
Online provides powerful project management capabilities for planning, prioritizing, and managing projects and
project portfolio investments—from almost anywhere on almost any device. Project Online can be used by
administrators, portfolio managers and viewers, project and resource managers, and team leads and members.
Platform
Project Online is built on the SharePoint platform, and uses key SharePoint features such as web parts,
collaborative sites, and SharePoint security groups. Access is provided through a supported web browser.
Users can access their Project Online projects through the Project Home page. It will by default list projects that
were recently viewed, owned, or shared with the user.
Data Storage
Project Online data is stored to the SharePoint Content Database in Office 365. Each Project Online site created
within the tenant creates a separate partition within the content database so that each instance is independent
of each other. For example, custom fields used in one Project Online site are independent of another Project
Online site.
Reporting
You can use PowerBI Desktop to import and analyze your Project Online data using Power BI. You can use the
Project Power BI template to view a Portfolio dashboard of reports that can be helpful in analyzing your data.
And as noted earlier, the same Project template can be used to include your Project for the web data as well.
For larger Project Online instances with very large amounts of data, you may want to use SQL Server
Integration Services (SSIS) to access and analyze your data.
Project Online Desktop Client

Many project managers use the Project Online desktop client as a personal productivity tool for their project
management needs. They build schedules in the client, save them as .mpp files, share these files with others, and
keep them updated as the project progresses.
You can also use the Project Online Desktop Client to connect to a Project Online site to take advantage of its
enterprise project and portfolio management capabilities.
See Also
Turn Project for the web off
Project for web get started guide for admins
Microsoft Power Platform documentation
Project for the web and Project Online
Project for the web and Project Online Desktop Client
Develop applications and reports for the new Project for the web
Project for the web limits and boundaries
There are important limitations that you should know if you are using Project for the web. These limits apply to
projects and tasks.
Project limitations
F IEL D L IM IT
Maximum total tasks for a project 500
Maximum total duration for a project 3650 days (10 years)
Maximum total resources for a project 150
Maximum total links (successor only) for a project 600
Maximum total custom fields for a project 10
Task limitations
F IEL D L IM IT
Maximum hierarchy level 10 levels
Maximum links (successor + predecessor) 20
Maximum duration of leaf task 1250 days
Maximum duration of a summary task 3650 days (10 years)
Maximum resources assigned to a task 20 resources
Supported date range for a task 1/1/2000 - 12/31/2149

Office 365 User view access to Project and
Roadmap
An appropriate Project Plan license is required for your Office 365 users to use Project for the web or Roadmap.
However, users that are assigned certain Office 365 licenses are allowed to have view access to Project for the
web and Roadmap. This provision will allow them to have read-only access to projects and roadmaps that are
shared with them, without needing to be assigned a Project Plan license.
If your users need to be able to edit or create projects or roadmaps, you will need to purchase the appropriate
Project Plan license and assign it to the user.
NOTE
For more information about Project Plan subscriptions and understand what the capabilities of an Office 365 user are, see
the Project service description.
Office 365 subscription with view access

Office 365 view access applies to the following families of Office 365 suites and their education counterparts.
Microsoft 365 F3 and Office 365 F3
Office 365 E1
Microsoft 365 for business
Microsoft E3 and Office 365 E3
Microsoft E5 and Office 365 E5
Within each subscription, there are two apps that can be seen from the Microsoft 365 Admin center.
Project for Office (Plan X)
Dataverse
The "Plan" in the title of Project for Office comes from the family of suite the app is included in. Both apps (from
the same subscription) must be assigned to the user to view Project for the web or Roadmap.
Project for Office App
A DM IN C EN T ER DISP L AY
FA M ILY SUB SC RIP T IO N NAME ID NAME
F3 Project for Office (Plan F) 7f6f28c2-34bb-4d4b- PROJECT_O365_F3

be36-48ca2e77e1ec
E1 Project for Office (Plan E1) a55dfd10-0864-46d9- PROJECT_O365_P1

a3cd-da5991a3e0e2
E3 Project for Office (Plan E3) 31b4e2fc-4cd6-4e7d-9c1b- PROJECT_O365_P2

41407303bd66
E5 Project for Office (Plan E5) b21a6b06-1988-436e- PROJECT_O365_P3

a07b-51ec6d9f52ad
NOTE
Microsoft 365 for business subscriptions include Project for Office (Plan E1), Project for Office (Plan E3) or Project for
Office (Plan E5).
Common Data Service App
A DM IN C EN T ER DISP L AY
FA M ILY SUB SC RIP T IO N NAME ID NAME
F3 Common Data Service ca6e61ec-d4f4-41eb-8b88- DYN365_CDS_O365_F1

d96e0e14323f
E1 Common Data Service 40b010bb-0b69-4654- DYN365_CDS_O365_P1

ac5e-ba161433f4b4
E3 Common Data Service 4ff01e01-1ba7-4d71-8cf8- DYN365_CDS_O365_P2

ce96c3bbcf14
E5 Common Data Service 28b0fa46-c39a-4188- DYN365_CDS_O365_P3

89e2-58e979a6b014
See Also
Office 365 platform service description
If you have users with one of the Office 365 User view access to Project and Roadmap, a Project tile will display
in the Office 365 App Launcher.
An admin may want to keep the Project tile from displaying for the user in some situations, such as:
If the user does not have a Project license and does not care to view Project for the web projects or
roadmaps.
If the user has a Project license, but doesn't use Project for the web or Roadmap.
To remove the Project tile from the App Launcher for a user, an admin needs to remove the Project for Office
service for the user’s Microsoft 365 or Office 365 license in the Microsoft 365 admin center.
IMPORTANT
Removing the Project for Office service will not only remove the Project tile, but will also no longer allow the user to view
Project for the web projects and roadmaps.
To remove the Project tile for an individual user

1. In the Microsoft 365 Admin Center, selectUsers , then select Active Users .
2. From theActive users list, select the checkbox next to the user, and then click Manage product
licenses .
3. On the user information page, select thelicenses and apps tab, in theApps section, select the user's
Microsoft 365 or Office 365 license from theShow apps for drop-down menu.
4. In the list of apps that display, uncheck Project for Office , and then clickSave changes .
You can repeat this procedure for each user that you don't want to use Project for the web.
To remove the Project tile for multiple users
If you need to remove the Project tile for a large number of users, it may be easier for an admin to do this task
through Windows PowerShell instead of through the Microsoft 365 admin center.
Make sure to use the latest Azure Active Directory module.
IMPORTANT
Again, note that removing the Project for Office service will not only remove the Project tile, but will also no longer allow
the user to view Project for the web projects and roadmaps.
1. In Windows PowerShell, type and enter the following to sign into your tenant.
Connect-AzureAd
2. After connecting to Azure Active Directory, you can use the following to get a list of the Office 365 or
Microsoft 365 licenses that have view access to Project for the web and Roadmap on your tenant.
$returnObject = @()
Get-AzureADSubscribedSku | % {
$cds = $_.ServicePLans | ? ServicePlanName -in
("PROJECT_O365_F3","PROJECT_O365_P1","PROJECT_O365_P2","PROJECT_O365_P3")
if( $cds -ne $null )

{
$returnObject+=
[pscustomobject]@{SkuId=$_.SkuId;SkuPartNumber=$_.SkuPartNumber;ServicePlan=$CDS[0].ServicePlanName}
}
}
if ($returnObject.Count -eq 0) {
Write-Host "No Skus found"
} else {
$returnObject
}
3. You can use the following script to help you to disable the Project for Office service plan for specific users
and their associated license. For each user, you will need to know the $skuPar t value for their license
(you can find this value in the results of step 2).
#disable the plan for the user/sku combination
$user = "<user>@tenant.onmicrosoft.com" #user

$skuPart = "ENTERPRISEPREMIUM" #sku to disable the plan on from the previous step
$plansToDisableList = @("PROJECT_O365_F3","PROJECT_O365_P1","PROJECT_O365_P2","PROJECT_O365_P3")
#Get the SKU details

$sku = Get-AzureADSubscribedSku | Where {$_.SkuPartNumber -eq $skuPart}
#Get a reference to the service plan we are disabling

$newPlansToDisable = $sku.ServicePlans | ? {$_.ServicePlanName -in $plansToDisableList}
#Get any disabled service plans (apps) on the SKU assigned to the user
$existingDisabled =Get-AzureADUserLicenseDetail -ObjectId $user | ? {$_.SkuPartNumber -eq $skuPart
} | Select-Object -ExpandProperty ServicePlans | ? {$_.ProvisioningStatus -eq 'Disabled' }
#Merge the lists together so we are maintaining disabled service plans (apps)
$totalDisabledPlans = @($newPlansToDisable,$existingDisabled)
#Create a license with the service plan (apps) disabled

$license = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
$license.SkuId = $sku.SkuId
$license.DisabledPlans = $totalDisabledPlans.ServicePlanId
$licenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses

$licenses.AddLicenses = $license
#Assign updated SKU

Set-AzureADUserLicense -ObjectId $user -AssignedLicenses $licenses
See also
Office 365 user view access to Project and Roadmap
Office 365 platform service description
Project for the web setup requirements for
Dynamics 365 business units
In Dynamics 365, you can create more business units in your Dataverse instance. If you want Project for the web
users in the business unit to be able to access and use it, you need to make sure that the associated team in
which your users are members have the Project Common and Project User roles applied to it.
NOTE
You only need to do this if you add a new business unit to your default CDS instance. This will automatically be applied to
your root business unit's team settings.
To apply the Project User role to a business unit

NOTE
You must be a Global Admin to do this.
1. In the Dynamics 365 Administration Center, for your default instance, click Open .
2. On the PowerApps Settings Apps page, click Project .
3. On the Project page, click the gear icon in the toolbar and click Advanced Settings .
4. On the Dynamics 365 Settings page, click the Settings menu in the toolbar, and in the Systems section,
select Security .
5. On the Security page, select Teams .
6. Select the team for your business unit from the Team Name column, and then click Manage Roles in the
toolbar.
7. In the Manage Team Roles screen, select Project User and Project Common , and then click OK .
See Also
Create or edit business units
Frequently Asked Questions
Using Project
Does Project for the web include a way to record timesheets?
No. If this is something that you need, let us know at the Project for the web User Voice site!
Why is the Tasks tab in the Project Power App blank?
This may be happening because third-party cookies are disabled for your web browser. In your browser settings,
choose to allow ‘third-party cookies’.
What is the Project Power App?
The Project Power App can be used by you and your organization to completely customize Project for your
workflows and processes. It is automatically deployed to the Default Dataverse environment the first time you
open Project.
How can I reach the Project Power App?
You can find the Project Power App in the Microsoft 365 app launcher. Just look for the Project app with the
purple icon.
Customization
Can I customize the Project Power App?
Yes! It is a model-driven Power App, which means you use the Power Apps designer to edit the look and feel of
Project.
How can I add custom fields at the Project level?
Use the Power Apps designer to add columns to the Tables, Views, and Forms in the Project Power App.
I need to use more than five custom tables with Project for the web, how can I do that?
Create a new Power App and add any tables you need into it. You can have all the core Project tables, views, and
forms, as well as any additional custom tables that you need. Users of this new Power App will need at least a
Project Plan 3 or Plan 5 license, as well as a license to PowerApps. If you intend to use tables from other
applications, be sure to follow any licensing guidelines for those apps.
How can I change the access rights for users of Project data in the Dataverse?
The Project Team Member role is customizable and can be used to manage the access rights of users. Learn how
to customize roles here.
How can I use Power BI with Project for the web?
You can use the Project for the Web Power BI content pack to create reports on Project for the Web data. Users
will need the appropriate license to be able to view these reports. Refer to other guidance in this FAQ, as well as
in the Microsoft Project service description.
Can I build apps or reports that include local custom fields?
No. Local custom fields are stored in a binary format within Project tables in Dataverse. These fields are not
available for reporting.
Can I remove a resource from the Project Team Dataverse table?
You can manage the team from within Project. But, you cannot manage resources directly in the table in
Dataverse.
Can I open the Project tables in Excel and edit them using the Dynamics widget?
You can open the Dataverse tables in Excel. However, fields included in Project cannot be directly written to.
Netiher can you create new rows in many of the tables. However, custom columns that you have added to the
tables can be directly edited within Excel.
Can I deploy to a Dataverse environment where I have other Dynamics 365 applications?
Project can be deployed to Dataverse environments that have the “Enable D365 Apps” toggle disabled. This
means Project for the web cannot be deployed in environments that contains applications such as Dynamics
365 Sales or Project Operations. Learn more about deploying Project for the web here.
Licensing
Can I build a standalone Power App and include Project tables in it?
Yes, you can. All users of this Power App will need a Project Plan 3 license as well as a Power Apps license.
Is Power BI included?
The Project for the Web Power BI content pack is free to download. However, users will need a Project Plan 3
license as well as a Power BI license to build or view reports.
Can embedded canvas apps in model-driven apps be used with a Project Plan license?
No. Users will need a separate Power Apps license to embed canvas apps into the Project Power App.
There are several additional tables included in the Project solution that aren't visible in the Power App, can I
use them?.
You can use many of the tables in the Project Solution to customize the look and feel of Project for your users.
These additional tables are:
msdyn_projectchange
msdyn_projectprogram
msdyn_projectrequest
msdyn_projectrisk
msdyn_projectissue
msdyn_projectstatusreport
How many Dataverse environments can I provision with a Project license?
The number of environments you can provision depends on the number of licenses you have. At the minimum,
you need one Project license to deploy Project in the Default Environment, and at least five Project licenses to
deploy to Production environments. Additional environments can be provisioned depending upon the amount
of Dataverse database storage you have. Details about the storage included with Project licenses are in the
Microsoft Project service description.
Create and apply work calendars in Project for the
web
Project for the web is built on the Microsoft Power Platform, and some aspects of resource setup for Project for
the web is done in Dynamics 365, including how to create a work hours template and apply it to resources.
Before you can create project schedules, you need to set up a project calendar that defines the number of
working hours to accommodate per day in the schedule and any business closures. You do this with a work
hours template, which contains details about work hours per day, days off, and any other business closures.
NOTE
Project for the web comes with a default work template that is automatically applied to users that you assign to tasks. It
specifies work hours of 9AM through 5PM from Monday through Friday. You only need to create a new work hours
template if this one does not suit your needs.
You associate a work template to the project calendar to apply the schedule for the project.
There are two ways you can create a work hours template:
Create a work hours template from the Resource page
Create a new work hours template from the Calendar Template page
NOTE
All work hours templates are based on resource calendars. Before creating a project calendar, you'll need to create a
resource with the working hours you want for your project.
Both methods are done on the PowerApps Project Resources page in Dynamics 365. To go there, do the
following:
1. While logged into Office 365, open a browser window and go to https://make.powerapps.com .
2. On the PowerApps page, select Apps .
3. On the Apps page, in the Org Apps tab, select Project .
4. On the Project page, in the left pane, select Resources .
Create a work hours template from the Resource Page

1. On the Resources page, select the resource you want to base your work hours on.
2. Click Save Calendar As , enter a name for the work hours template, and then click Save .
3. When you’re done changing options, click Save and Close .
Create a new work hours template from the Calendar Templates page
1. On the Resources page, click the Projects menu on the bottom of the left pane, and then select Settings .
2. On the Project Settings Parameters page, click Calendar Templates .
3. On the Active Work Hour Templates page, click New .
4. ON the New Work Templates page, give it a name.
5. In the Template Resource field, type the name of a resource to base the work hours on.
6. Click Save and Close .
7. Your new work hours template will display on the Active Work Hour Templates page.
Apply a calendar to a resource

Once you’ve created a work hours template, you can assign it to resources so their calendars reflect the working
hours specified in the template.
1. On the Resources page, select the resources that you want to apply set the calendar for. You can select more
than one resource.
2. Click Set Calendar .
3. In the Work Template window, click in the Work Template box to see the work templates that are
available, and then select the one you want to apply.
4. Click Apply .
Apply a calendar to a project

You can also choose to apply a calendar directly to a project in Project for the web. All work hours done on tasks
for the project will need to be done in the times and dates specified by the selected calendar.
1. In your project, click the project name to see the Project details pane.
2. In Project details, click the Calendar drop-down menu and select the calendar you want to apply to the
project.
NOTE
If you do not see the Calendar field in Project details, this means that there is only one calendar available to choose from
(for example, the default work template), so there is no option to select a different one until a new one is created.
See Also
Add non-user resources in Project for the web
Project for the web is built on the Microsoft Power Platform, and some aspects of resource setup for Project for
the web is done in Dynamics 365, such as how to add resources that are not users in your organization (for
example, contacts or equipment) and making them available to assign to tasks.
While users in Azure Active Directory (AAD) are available to assign to project tasks in Project for the web, you
need to manually add non-user resources.
NOTE
Guest users accounts in AAD are not supported to be available to directly assign to tasks in Project for the web.
Types of non-user resources

Some of the more commonly used non-user resources you will be able to add include:
Name Description
Contact or Account The resource is not directly a part of your organization, but
needs to be scheduled. A common example is
subcontractors.
Equipment The resource is a piece of equipment, tool, or machine that

must be scheduled.
NOTE
You will only be able to assign user, contact, account, or equipment resource types to project tasks in Project for the web.
For more information about non-user resources, see Set up a bookable resource.
Create a non-user resource

You first need to go to the Dynamics 365 Project Resources page:
1. While logged into Office 365, open a browser window and go to https://make.powerapps.com .
2. On the PowerApps page, select Apps .
3. On the Apps page, in the Org Apps tab, select Project .
4. On the Project page, in the left pane, select Resources .
When you get to the resources page, do the following:
1. On the Resources page, click New .
2. On the New Bookable Resource page, click in the Resource Type field, and select the resource type you
need to create.
3. Provide the information needed for the resource type you selected.
4. In the Name field, type the name your want to give the resource.
5. When you’re done, click Save and Close .
The new resource will display in the Bookable Resources page and can be assigned to tasks in Project for the
web.
See Also
Set up a bookable resource
Overview of Universal Resource Scheduling in
Project for the web
The Universal Resource Scheduling option in the Resource Scheduling app enables booking of resources
to projects that helps ensure that resources are not overloaded with too much work from too many projects.
Prerequisites
Before you can use the Universal Resource Scheduling option, ensure you have:
Project for the web. For information on specific licensing needs, see service description.
User credentials with the necessary permissions.
Book a resource to a project

The process of booking a resource to a project comprises the following tasks:
Create a resource requirement
Schedule the booking requirement
Create a resource requirement
IMPORTANT
Before you create a resource requirement, ensure you devise a project schedule that clearly presents your resource needs.
1. Launch the Resource Scheduling app.
NOTE
To find Resource Scheduling app, launch https://make.powerapps.com. In the top-right corner, ensure that the
desired environment is listed. The desired environment is referred to one in which you can create the chosen
resource requirement.
2. Select Apps in the left navigation pane.

3. Select Resource Scheduling .
4. In the left navigation pane, select Resource Requirements .
5. Select New in the toolbar on top of the screen. The New Resource Requirement screen appears.
6. Use the tooltips to fill in the required information. For more information, see Allocation Method.
7. Select Save .
Schedule the booking requirement
You can schedule a booking requirement in the following ways:
Select an unscheduled booking and find available resources
Drag an unscheduled booking requirement from the List view to the Schedule Board
Select an unscheduled booking and find available resources
1. From the Resource Scheduling home screen, select Schedule Board .
2. From theBooking Requirement list, select on an unscheduled booking.
3. From the list of resources on the Schedule Board, select Find availability . This option enables you to find
the list of resources that are available and those resources that fit your requirement from the list.
NOTE
When you use the Find availability option, you are presented with a list of options related to the chosen
booking requirement. If the options are not displayed, try adjusting the filters.
4. When you find an apt available time slot for your booking requirement, right-click on it and choose Book
Here . Alternatively, you can drag unscheduled booking requirement to an available resource/time slot on the
Schedule Board.
Drag an unscheduled booking requirement from the List view to the Schedule Board
1. From the Resource Scheduling home screen, select Schedule Board .
2. Select an unscheduled booking requirement from the booking requirement list at the bottom of the screen.
3. Drag the unscheduled booking requirement to an available resource/time slot on the Schedule Board.
If the resource was soft booked or proposed, the resources availability won’t be affected. Find more information
here. The project manager can accept a resource booking proposal or change a booking status through the
Bookings table at Resource Scheduling > Bookings .
Once the resource is booked to the project, the resource shows up in the resource list and can be assigned to
tasks. To ensure the project manager doesn’t use the resource more than its booking limit, we recommend you
create a report to review the booking versus total assignments.
Update your environment

Before you can use Bookings with Project for the web, we recommend some updates to the Project Power App.
To make these updates in the environment, you need Environment Maker role. If you want to be able to search
for resources based off skills or roles, you will need to show these fields on the resource form so the
information can be entered.
See this article for more information on how to set up skills and proficiency models although the experience
within Project for the web will be a bit different. Once you have created skills and ensured the proficiency model
meets your needs, you need to update your resources with the skills they have. Therefore, when trying to find a
resource that meets a requirement, you can ensure you are staffing the correct person for the work.
You can also use roles to help further define your resource needs. Roles can be defined through the Settings
option in the Resource Scheduling . You can use roles in addition to skills (for example, have a developer role
and then skills based off more specific coding needs) or just use roles or skills for resource searching. Once roles
are defined, you will then need to update resources similar to skills.
1. Go to https://make.powerapps.com.
2. Ensure that you have set the precise environment in which you want to make edits, and that which is
assigned to a project.
3. In the left navigation pane, select Apps .
4. Select the radio button of the project that you want to edit, and select Edit .
NOTE
See these documents for more information on working with Power App model-driven apps. This article just covers
the basic changes needed for bookings. We do recommend putting these changes in a new layer.
5. Select Forms in the Bookable Resource row. This action sets the right pane to Bookable Resource and
results in display of the forms.
6. Select the pencil icon that is at the right of Information . This action results in a pop up of the Power Apps
form editor.
7. In the tree view, scroll to Project Ser vice and unhide it.
NOTE
You can also rename the section, if you wish.
8. Make more changes of choice to the form.

9. Select Save in the top-right corner.
10. Select Publish in the top-right corner.
11. Select X on the top-right corner to exit the window.
It is also recommended to turn on the Team tab, too, for projects. This action enables your project managers to
understand their resource needs and compare those needs to the bookings so that they can stay within their
resource budgets.
1. Execute Steps 1-4 from the previous section.
2. Select Forms in the Project row. This action sets the right pane to Project and results in the display of the
forms.
3. Select the pencil icon to the right of Information . This action results in a pop up of the Power Apps form
editor.
4. In the tree view, scroll to Team and unhide it.
NOTE
If you are using the Project Accelerator, the Team view has already been un-hidden and is called Resources .

7. Select X on the top-right corner to exit the window.
8. Select Views in the Project Team Members row.
9. Select the pencil icon to the right of Team Members (or whatever view you want to edit).
10. Select Column Attributes Primar y Entity .
11. Drag the columns that you want to add to the table. We recommend the Hard Booked Hours column but
you may also want to add the Soft Booked Hours column.
Update permissions/privileges
You will need to update permissions for people who need to use the Schedule Board. For an overview of how
permissions work and how to update them, see Security roles and privileges article.
To create a resource requirement, a user may need the following privileges:
IMPORTANT
The exact needs depend on which fields you decide to use around resource requests and on your processes. A user may
also need additional privileges if you have edited other security roles.
Custom Entities
Requirement characteristic
Requirement Group
Requirement Organization Unit
Requirement Relationship
Requirement Resource Category
Requirement Resource Preference
Requirement Status
Resource Request
Resource Requirement
Resource Requirement Detail
To accept a booking proposal, the user will additionally need:
Service
Booking Status
To use the Schedule Board and manage resource properties, the user will additionally need to have the
Environment maker role in addition to the following roles:
Service
Bookable Resource Booking
Bookable Resource Booking Header
Bookable Resource Category
Bookable Resource Category Association
Bookable Resource
Bookable Resource Characteristic
Bookable Resource Group
Booking Status
Custom Entities
Booking Alert Status
Booking Change
Booking Rule
Booking Setup Metadata
Fulfillment Preference
Schedule Board Setting
System User Scheduler Setting
Project for the Web Security Roles
Project for the web includes several security roles that enable users to work with Project. Some of these security
roles can also be customized by Administrators to control access of data. For more information, see Security
roles and privileges.
Project Common and Project User roles need to be assigned to each user to create/manage projects within a
non-default environment. These roles are needed in addition to roles required to login and access a Dataverse
environment. For more information, see Security roles and privileges.
Microsoft Project (also maybe shown as Microsoft Por tfolios ) is an application user that is provisioned in
the environments that is used by Project for the web to interact with Dataverse. The Microsoft Project
application user must be assigned to the following roles for the service to function correctly:
Portfolio User (deprecated)
Project Common
Project System
Roadmap System (Default Dataverse organization only)
Roadmap user (Default Dataverse organization only)
Behavior with AAD Groups

When a project is shared with an AAD Office Group, the Microsoft Project Application user will:
1. Create a Team that is backed by the AAD Group (if a team with the AAD group doesn’t already exists). The
name of the team will be the same as the AAD Office group when possible.
NOTE
Changes to the name of the O365 group will not update the name of the Dataverse team.
2. The team is given the following security roles:

Project Team Member
Project Common
NOTE
In the Default org, the team was given Project User role for older project.
3. Ownership of the project and related tables is changed from the current owning user to the newly created
team. Project for the web only supports adding more security roles to the Microsoft Project Application user.
Other changes/modification are not supported and can cause the service not to function. The Project
Common role can modify to support least privilege and customization.
Project Common
Can be customized and used to support extensibility, see Behavior with AAD Groups to understand how this
permission is assigned to AAD Groups.
Default org: Users are automatically given this role
Non-default: Administrators need to assign to users to support the creation of projects when the
environment has been customized.
The AAD Office Group team created at the project-sharing stage is given this role so that members have
enough permissions to log into and interact with the environment.
Portfolio User
Deprecated as of 0.8.7.59
Internal use by Project for the web. Provides user scoped permissions to create, read, update, and delete
portfolio and related entities.
Users should not be assigned this role.
Project System
Internal use by Project for the web
Provides all organization scoped permissions to create, read, update, and delete project and related entities.
Project Team Member

Provides user scoped permissions to read, update, and delete project and related entities.
The AAD Office Group team created at the project-sharing stage is given this role so that member can
interact with the project.
Project User
Provides user scoped permissions to create, read, update, and delete project and related entities.
Default org: Users are automatically given this role
Non-default: Administrators need to assign to users to support the creation of projects.
Roadmap System
Internal use by Project for the web. Provides all organization scoped permissions to create, read, update, and
delete portfolio and related entities.
Exists in the default organization only
Roadmap User
Provides user scoped permissions to create, read, update, and delete portfolio and related entities.
Exists in the default organization only
Users in the default organization are automatically given this role.
Access a project in Project for the web after its
Office 365 group has been deleted
If the Office 365 group that is associated with your project has been deleted, users in the group will not be able
to access the project. However, there are ways for you to regain access.
The group owner can restore the Office 365 group.
An admin can reassign the project to a user who can then choose or create a new group.
The option you should choose depends on how long ago the group was deleted.
Restore the Office 365 group

If a group that you own has been deleted, it will be retained for 30 days by default. This 30-day period is
considered a "soft-delete" because you can still restore the deleted group. After 30 days, the group will be
permanently deleted and cannot be restored.
If you are the owner of an Office 365 group, you can restore the group yourself by following these steps.
1. On the Deleted groups page , select the Manage groups option under the Groups node, and then choose
Deleted .
2. Click on the Restore tab next to the group you want to restore.
After you've restored the group, members of the group should be able to access the associated project in Project
for the web.
NOTE
To learn more about deleting an Office 365 group, see Restore a deleted Office 365 Group
Reassign the project

If the Office 365 group has been deleted for longer than 30 days, it is not restorable and an admin in your
tenant will need to reassigning the project to either the user who needs to access it or someone who can add a
new Office 365 group in Project for the web.
The admin will need to:
1. Find the project through the Advanced Find search function in the Dynamics 365 Admin Center.
2. Assign the project to the user that needs to access it.
Find the project in Advanced Find search
Use Dynamics 365 Advanced Find search to look for the project you need.
1. In the Dynamics 365 Administration Center, select the default instance, and then click Open .
2. On the PowerApps Settings page, select Dynamics 365 Custom .
3. On the Projects page, click the filter icon in the menu bar and then select Advance Find .
4. In Advanced Find, in the Look for menu, select Projects . In the Use Saved View menu, select All
projects .
5. Click Select , and from the menu, select Name . From the next menu, select Equals , and then in the Enter
text box type the name of the project you are looking for.
6. Click Results to run the query. The project you are looking for should display in the Projects tab.
Reassign the project to a new user
After locating the project through Advanced Find, the admin can now reassign the project to a user.
To reassign a project to a user:
1. Select the checkbox next to the project name.
2. In the ribbon, click Assign Projects .
3. On the Assign Project screen, click in the Assign to box to change it to User or team .
4. Click in the User or team box, and then click the magnifying glass icon. Then scroll to the bottom of the
results and click on Look up more records .
5. On the Lookup Record screen, select User in the Look for menu, select the user from the user list, and
then click Add .
The user that you added will now be able to access the project in Project for the web. The user can also choose
to associate a new Office 365 group with the project and add users to it if others also need to access the project.
See Also
Share a project in Project for the web
This article describes how a Microsoft 365 tenant admin can export a specific user’s data from Project for the
web. The admin can then choose to view the user’s data and decide what data they want to make available to
the user.
Project for the web data is stored in Dataverse in Microsoft PowerApps. This article describes how you can:
View a specific user’s Project for the web data by using the Advanced Find function in Dynamics 365.
Use a PowerShell script to export data about specific projects that your user was a part of.
Requirements
You will need the following in order to look for data on a specific user through the Advanced Find search feature:
You need the Azure Active Directory Object ID (AAD ID) of the user. You can find it in the Azure Active
Directory Admin Center.
You need to be a global admin in your Microsoft 365 tenant. You need this to access the Dynamics 365
Admin Center.
If you also want to export and view information on specific projects:
You need to be a tenant admin.
You need to have a Project Plan 1, Project Plan 3, or Project Plan 5 license.
You need the Project Online Desktop Client if you want to export your user’s projects. If you do not have one
available, you can sign up for a trial.
Methods for finding your user's data

Depending on the type of user data you need to find, there are two paths you can take in searching for and
exporting your user's data.
Find data about your user's project and roadmap objects in Dataverse - Use the Advanced Find
feature in the Dynamics 365 Admin Center to find all the user's data that is contained in Dataverse (for
example, objects related to their projects and roadmaps).
Find data about specific projects that your user was associated with - Use the project export
PowerShell script to get details about specific projects the user was associated with.
Find user data in Dataverse with the Advanced Find search feature
Project for the web user information that resides in Dataverse - such as roadmap and project objects and
properties - are located in specific Dynamics 365 solutions. The Advanced Find search feature in the Dynamics
365 admin center can query across entities in these solutions to find the information you need.
Understand Project for the web Dataverse data and where it resides
When looking for a specific user's Project for the web data in Dynamics 365 Dataverse, it is located in these five
Dynamics 365 solutions:
NAME DISP L AY N A M E
PortfolioService Portfolio Service
msdyn_ProjectServiceCore Project
MicrosoftDynamicsScheduling Universal Resource Scheduling
msdynce_SchedulingPatch Scheduling Patch
mydynce_Scheduling Scheduling
You can look specifically at any of these Dynamics 365 solutions to get an idea of the entities that exist for it.
Understanding the entities that exist for a specific solution can help you with understanding what to look for in
your query.
To view entities for a Dynamics 365 solution:
1. In the Microsoft 365 admin center, under Admin centers , click Dynamics 365 .
3. On the Dynamics 365 Settings page, click the Settings menu, and in the Customization section, select
Solutions .
4. On the All Solutions page, click on the Display Name of the solution that you are interested in.
5. On the solution information page, expand Entities to view them.

6. Under each entity, you can select specific objects to get more details about its properties.
Use Advanced Find to search for user data

Use Dynamics 365 Advanced Find search to look for Project for the web data for your user. Advanced Find will
search across all solutions in your Dataverse instance. You can then download the results directly to an Excel
spreadsheet and determine what to provide to your user.
2. On the Dynamics 365 Settings page, click the Settings menu, and in the Customization section, select
Solutions .
3. Click the Advance Find button.
4. In Advanced Find, in the Look for menu, select the objects that you want to search for, such as your
user's projects or roadmaps.
For example, if you want to view all roadmaps your user was a part of, select Roadmaps .
5. To begin building your query, click Select , and then select the fields you need to start searching for
projects or roadmaps your user was a part of. You will need the users AAD ID or account name.
For example:
To find all roadmaps owned by the user, select the Owner field, and then select Equals, and then
enter the account name for the user.
To find all roadmaps created by the user, select the Created By field, and then select Equals, and
then enter the account name for the user.
6. When you are done with selecting your search criteria, in the ribbon, select Edit Columns .
7. On the Edit columns page, select Add columns , and then select the columns you want to include in the
query. When done, click OK .
8. Click Results to run your query.
9. After you receive your results, you can export them to Excel. To do this, click Expor t , and then select
Static Worksheet .
You can then review the results to determine what data you'd like to provide to the user.
Use the export script to see details on specific projects

If you need to look for more details that are contained in specific projects that the user was associated with, you
can use the ExportProjectContent PowerShell script to get more information on each project. With the script, you
can get the following files for a specific project:
Project files (.MPP) for the project.
An XML file that contains project details and settings.
Get the Project IDs of the projects you are interested in
Before you run the script, you need to the Project IDs of the projects you are interested in.
Assuming you've used Advanced Find search to query for the user's projects and have downloaded the them to
an Excel file, the Project ID column is the first column in the Excel spreadsheet, but it is hidden by default.
Unhiding the first column can be a bit tricky, so if you need help, see Unhide the first row or column in a
worksheet.
After you unhide the columns in the spreadsheet, look for the name of the project, and then look for the
corresponding value in the Project column to find the Project ID for the project.
Run the Export script

Now that you have the Project IDs of the projects you are interested in looking at, use the
Expor tProjectContent Windows PowerShell function to get more information. The ExportProjectUserContent
function is included in the ProjectExport Windows PowerShell module.
Download the Project Export Windows PowerShell module and first unblock the zip file and then unzip the files.
NOTE
After you unzip the script, run the following in Windows PowerShell to import the modules:
Import-Module -Name ./projectexport
To run the ExportProjectContent function:

1. In Windows PowerShell, where you have imported the module, run the following:
ExportProjectContent -ProjectId (ProjectID of the project) -OutputDirectory (Location to put files) -
InstanceId "(Dataverse instance name)"
You will need to configure the following parameters when running the script:
PA RA M ET ER DESC RIP T IO N
ProjectId GUID of the project within Dataverse. You learned how

to find this in the previous section.
OutputDirectory Location where the export files are put.
InstanceId The identifier of the Dynamics 365 instance you are

using.
To find your Instance ID:

a. In the Dynamics 365 Administration Center, select the default instance, and then click Open .
b. On the PowerApps setting page, look at the first part of the URL to determine your Instance ID value. In
the graphic below, the Instance ID value would be https://orgde6d15d8.crm.dynamics.com .
As an example of how to run the script, if the Project ID of the project is dd065460-02b8-e911-a989-
000d3a170e10, you want the output files to go to C:\User1Project1, and the instance name of the
Dataverse org is https://orgde6d15d8.crm.dynamics.com , you would run the script like this:
ExportProjectContent -ProjectID dd065460-02b8-e911-a989-000d3a170e10 -OutputDirectory
C:\User1Project1 -InstanceId https://orgde6d15d8.crm.dynamics.com "
2. When the script completes, go to the OutputDirectory location you specified to find the .XML and .MPP
files for the project.
3. If you have multiple projects, run the script again for each project, using it’s corresponding ProjectID
value.
Both the .XML and .MPP files that are created will be prefixed with the project’s Project ID. For example, if the
Project ID value is dd065460-02b8-e911-a989-000d3a170e10, the file names for the exported data will be:
dd065460-02b8-e911-a989-000d3a170e10.XML
dd065460-02b8-e911-a989-000d3a170e10.MPP
Note that you may receive multiple versions of your .MPP file, known as snapshots. These are versions of your
project file prior to changes being made to it. Snapshot files will include a timestamp to let you know when they
were taken. One thing to note is that the current version of the file is the one with the earliest timestamp -
which would be the project creation date.
All snapshots currently stored for the project are exported. Snapshots can be periodically cleared out depending
on how active the project is.
View data contained in the project file (.MPP)
Use Project Online Desktop Client to open and view the project file to find information that you might want to
provide the user.
Project Online Desktop client is available through either the Project Plan 3 and Project Plan 5 licenses. If you
don't have a subscription, you can sign up for a trial.
NOTE
You will only be able to view the project file. You will not be able to edit the .MPP file in any way. You cannot export the
.MPP file from Project for the web and import it into Project Online (PWA).
View data contained in the project XML file
The XML file contains a number of properties pertaining to the specific project. You can see the Project XML
Interchange Schema Reference to understand the XML data contained in this file.
See Also
Create, edit, or save an Advanced Find search
Export user data from Project Online
To delete user data from Project for the web, you need the user's Azure AD Object ID. You can get this by
checking the user's profile properties in Azure Active Directory or by using Get-AzureADUser.
To find a user's Azure AD Object ID in the Azure Active Directory Admin Center:
1. In the Azure Active Directory Admin Center, click on Users to see a list of all users in your organization.
2. Click on the name of the user.
3. On the user profile page, in the Identity section, you can find the user's Azure AD Object ID value in the
Object ID field.
To find and delete a user's roadmaps

2. In the Dynamics 365 Administraton Center, select the default instance, and then click Open .
3. On the PowerApps page, click the Settings icon in the menu bar, and select Advanced Settings .
4. On the Dynamics 365 Settings Business Management page, click the filter icon and then click
Advanced Find .
5. From the Look for menu, choose Roadmaps .
6. Click Edit Columns
7. Click Add Columns .
8. Choose the columns below that you want to search on. Be sure to include Office 365 Group AAD ID .
DISP L AY N A M E DESC RIP T IO N
Name Name of the roadmap.
Order Hint Ordering of the roadmap rows within a roadmap.
Owner AAD ID ID of the user in AAD who owns the roadmap.
Parent Roadmap ID of the parent roadmap.
Creator AAD ID ID of the user in AAD who created the roadmap.
Office 365 Group AAD ID ID of the roadmap's Office 365 group in AAD.
Roadmap Unique identifier of a roadmap.

DISP L AY N A M E DESC RIP T IO N
Roadmap Type The type of roadmap record.
9. Click OK , and then click OK again.

10. In the Fields list, choose Owner AAD Id and type in the user's Azure AD Object ID.
11. Click Results .
12. Click the name of the roadmap you want to delete.
13. Click Delete .
To make changes to a user's roadmap

From your Advanced Find search results, make note of the Office 365 Group AAD ID for any roadmap that you
want to make changes to. You must join this group as an owner in order to make updates to the roadmap.
To add yourself as a group owner, use Add-AzureADGroupOwner:
Add-AzureADGroupOwner -ObjectId <GroupID> -RefObjectId <YourAADObjectID>
For example,
Add-AzureADGroupOwner -ObjectId "62438306-7c37-4638-a72d-0ee8d9217680" -RefObjectId "0a1068c0-dbb6-4537-9db3-
b48f3e31dd76"
Once you are an owner for the groups, you can open the roadmaps from Project Home and make edits directly.
Roadmap must be enabled to do this.)
For roadmaps not associated to an Office 365 group
If your user's roadmap is not associated to an Office 365 group, and you want to be able to make edits to it, you
need add a group that you own to the roadmap.
This first requires you to create an Office 365 Group and get the Office 365 Group AAD id value for it. After you
do this, do the following:
1. In the Advanced Find search results, click the name of the roadmap to open it in Dynamics 365.
2. In the Roadmap Information page in Dynamics 365, click the menu item with three dots, and in the menu
select Flow , and then select Form Editor .
3. In the Form Editor, select Office 365 Group AAD id from the Unused Fields list, and drag and drop it to the
General section of the form, under Owner.
4. Click Save and then Publish .
5. After the change in completed, on the Roadmap Information page, you will see the Office 365 Group AAD id
field display. Enter the Office 365 Group AAD ID value of the group you own into the field box.
You are now the owner of the Office 365 Group for the roadmap and can edit it.
To find a user's projects

3. Click Advanced Find .
4. From the Look for menu, choose Projects .
5. To begin building your query, click Select , and then select the fields you need to start searching for
projects your user was a part of. You will need the users AAD ID or account name. For example:
To find all projects owned by the user, select the Owner field, and then select Equals, and then enter the
account name for the user.
To find all projects created by the user, select the Created By field, and then select Equals, and then
enter the account name for the user.
6. When you are done with selecting your search criteria, in the ribbon, select Edit Columns .
7. On the Edit columns page, select Add columns , and then select the columns you want to include in the
query. When done, click OK .
8. Click Results to run your query.
To delete or edit a project
To delete or edit a users project, do the following:
1. From the Advanced Find search results list, note the project you want to delete or update.
2. On the PowerApps admin page, click the drop-down menu and select Project .
3. On the Project page, in the System Views menu, select All Projects .
4. Click on the project you are interested in deleted or redacting.
5. On the project page, you can choose to:
Click Delete to delete the project.
Click Tasks to update the the project's tasks.
See Also
Create, edit, or save an Advanced Find search
Delete user data from Project Online
Handling data for Project
This article gives you an overview of how data is handled for two Project services: Project for the web and
Project Online.
Project Online is built on SharePoint Online and its data is stored in Office 365 (specifically in SharePoint
Online).
Project for the web is built on the Microsoft Power Platform. Project for the web data is stored in Dataverse.
NOTE
Project for the web data also includes data from its Roadmap feature.
Data retention
Since Project for the web data is stored in CDS, data retention policies differ from Project Online (whose data is
stored in Office 365). When your Project Online subscription ends, your data is retained for 90 days before it is
automatically deleted (in accordance to Office 365 data retention policies). However, if you use Project for the
web (which is included in Project Plan 1, Project Plan 3, and Project Plan 5 licenses), that data is not
automatically deleted 90 days after your subscription ends.
You can remove all Project for the web or Roadmap data by removing the entire solution from from Microsoft
365.
Where is my data located

You can look for the location of where your Project for the web and Project Online data is stored by seeing
Explore where Office 365 stores your customer data.
Project for the web and Dataverse
When Project for the web is first used in your Microsoft 365 tenant, a default Dataverse instance is provided to
your tenant. Project for the web data (such as projects or roadmaps) is stored in solutions in the default instance.
Admins can find the name and details of their default Dataverse instance in the PowerApps admin center
(admin.powerapps.com).
Deleting user data

If you need to delete Project for the web data (for example, you need to delete data for a specific user) an admin
can choose to manually delete it.
Similarly, an admin can also manually delete Project Online data (for example, user data or user identifying data)
if needed.
Turn off Project for the web

An admin can choose to either turn off Project for the web to your organization or choose to turn off Project for
the web to specific users in their organization.
NOTE
When you turn off Project for the web to individual users in your tenant, you will also turn off the Roadmap feature for
those users.
Turn off Roadmap

Although Roadmap is a Project for the web feature, it is possible that some organizations may want to use
Roadmap, but may want their users to access Project for the web at a later time.
The Turn Roadmap on for your organization control on the Project Settings page allows you to turn
Roadmap on or off in your organization.
Turn off Project Online

An admin may want certain users to have access to Project for the web and the Roadmap feature, and not
Project Online. To do this, an admin would need to turn off the Project Online service for the user through their
assigned Project Plan 3 or Project Plan 5 license.
See Also
Project for web get started guide for admins
Remove Project for the web or Roadmap from
Microsoft 365
You can turn Project for the web or Roadmap off in the Microsoft 365 admin center. This setting prevents your
users from using them, but will not remove any user data that currently exists.
NOTE
It may take a few minutes for functionality to be disabled while the setting synchronizes across your tenant.
To turn off Project for the web:

1. In the Microsoft 365 admin center, under Settings , click Org settings .
2. Click Project .
3. Uncheck Turn on Project for the web .
4. Click Save .
NOTE
Although this setting currently displays in your Project settings, it will not be enabled until a later date (see your Message
Center). You can still turn off Project for the web for individual users.
To turn off Roadmap:

1. In the Microsoft 365 admin center, under Settings , click Org settings .
2. Click Project .
3. Uncheck Turn on Roadmap for your organization .
4. Click Save .
If your Project Online subscription ends, most of the associated data is deleted in conformance with the Data
retention, deletion, and destruction in Microsoft 365. Unlike other Project Online data, Project for the web and
Roadmap data isn’t automatically deleted when your Project Online subscription ends.
Remove Project for the web and Roadmap data

You can remove all Project for the web and Roadmap data by removing the entire solution from Microsoft 365.
This removal deletes all of the existing projects, roadmaps, and associated user data.
To remove Roadmap: (Only applies to the default organization as Roadmap can only be installed on the
default organization)
1. In the Microsoft 365 App Launcher, click Power Apps (or as an alternative, you can go to
https://make.powerapps.com/).
2. Ensure that the default organization is selected at the top of the page; if not, change it to the default
organization. (As noted above, Roadmap can only be installed on the default organization; as such, it is the
only organization where you can remove the roadmap from.)
3. Click on the settings icon on the top right of the page and go to Advanced Settings .
4. On the Settings menu, under Customization , click Solutions .
5. Select the Por tfolioSer vice solution, and then click Delete .
6. Select the Por tfolioSer vice_Anchor solution, and then click Delete .
7. Select any solutions with a naming format of Por tfolioSer vice_Patch_(number) , (for example,
PortfolioService_Patch_1 or PortfolioService_Patch_2), and then click Delete .
NOTE
Removing the Roadmap solution does not affect any of the projects or tasks that the roadmaps are connected to.
To remove Project for the web:

1. In the Microsoft 365 App Launcher, click Power Apps or you can browse directly to it by going to:
https://make.powerapps.com/.
2. Ensure that the correct organization where you want to remove Project for the web is displayed at the top of
the page. In most cases, it will be the default organization if you have an out-of-box installation.
3. Click on the settings icon on the top right of the page and go to Advanced Settings .
4. On the Settings menu, under Customization , click Solutions .
5. Select the msdyn_ProjectSer viceCore solution, and then click Delete .
6. Select the msdyn_ProjectSer viceCore_Anchor solution, and then click Delete .
7. Select the MicrosoftDynamicsScheduling solution, and then click Delete .
8. Select any solutions with a naming format of msdyn_ProjectSer viceCore_Patch_(number) , (for example,
msdyn_ProjectServiceCore_Patch_1 or msdyn_ProjectServiceCore_Patch_2), and then click Delete .
See Also
Project Service Core solution version history
Introduction
This article lists all of the updates that have been made to Project Service Core solution in Microsoft Dynamics
365 to date, along with other information pertinent to those updates. This solution is used by the Project for the
Web application that is available in Microsoft Project.
Upgrade Information
If you want to upgrade your solution within Dynamics 365 when a newer version is available, please see KB
#3192042.
Version history
VERSIO N REL EA SE DAT E UP DAT E DESC RIP T IO N
1.0.7.94 February 2, 2021 Items resolved in this version:
- Bug: Copy Project intermittently fails
- Bug: Block installation on orgs of

type (Teams)
Additional performance improvements

and bug fixes
1.0.6.154 January 12, 2021 Items resolved in this version:
- Bug: Breaking change by renaming

web resource
- Bug: Update web resources in base

solution
- Bug: Named orgs need default

PostImport configuration parameters
- Bug: Rename Common Data Service

User to Project Common
- Bug: Named orgs toolbar updates
- Feature: Add customizable entities to

app module
Additional improvements in
performance and bug fixes
1.0.4.71 November 7, 2020 Items resolved in this version:
- Bug: Manual deployment fails with

post-import error
- Bug: User timezone related

notification is not localized
- Bug: Updated localization translation
- Bug: Missing validation on Project

Start Date
- Feature: Added support for Project

Operations
Additional improvements in
performance and bug fixes
1.0.1.605 April 3, 2020 Improvements in installation of the

solution to address instances where
the default team has been modified.
Additional bug fixes and performance
improvements
1.0.1.427 January 2020 Several bug fixes and performance

improvements
1.0.1.211 November 2019 Several bug fixes and performance

improvements
Roadmap's Portfolio Service solution version history
Introduction
This article lists all of the updates that have been made to Roadmap's Portfolio Service solution in Microsoft
Dynamics 365 to date, along with other information pertinent to those updates. This solution is used by the
Roadmap feature available in the Project service.
Upgrade Information
If you want to upgrade your solution within Dynamics 365 when a newer version is available, please see KB
#3192042.
Version history
0.8.7.40 October 2020 Plugins added to support Url updates

in ConnectionSettings entity to
support SharePoint site rename and
Microsoft 365 tenant rename.
Plugins and roles added to support
Roadmap entities being owned by
Microsoft 365 groups in the
PowerApps Platform.
0.8.6.0 September 2019 Allow changing Roadmap item types

(From KeyDate to Phase or vice versa).

Project For The Web Admin Help

Uploaded by

Copyright:

Available Formats

Project For The Web Admin Help

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project For The Web Admin Help

Uploaded by

Copyright:

Available Formats

Contents

Get started with What is Project Project for the

Project Project for the Project for the

Learn more about Project for the web

Turn off Project for the web for specific users

Help your users

Reporting information on Project for the web data

Resource setup in PowerApps

Searching for user data for Project for the web

Provisioning a new environment

Project is supported in the following types of environments:

Learn more about creating and managing environments.

Learn more about using the PPAC to deploy applications.

Configuring Roles and Security

Creating and managing projects in non-Default environments

Deploying an environment to a different Geography

Dynamics Provision 39e6ea5b-4aa4-4df2-808b-b6b5fb8ada6f

Common Data Service 00000007-0000-0000-c000-000000000000

Microsoft Flow 7df0a125-d3be-4c96-aa54-591f83ff541c

Microsoft PowerApps 475226c6-020e-4fb2-8a90-7a972cbfc1d4

Dynamics CRM Online Administration 637fcc9f-4a9b-4aaa-8713-a2a3cfda1505

Project Online f53895d3-095d-408f-8e93-8f94b391404e

Verifying status of Enterprise applications

6. Click Proper ties on the left pane.

7. Ensure that Enabled for users to sign-in is set to Yes .

$ProjectRequiredApps = Get-AzureADServicePrincipal -Filter "

$ProjectRequiredApps | Select DisplayName, AppID, ObjectID, AccountEnabled, AppRoleAssignmentRequired,

Foreach ($App in $ProjectRequiredApps) #Remove from hashtable if app exist.

#Check that AppRoleAssignmentRequired for all required apps is set to False

Change your organization’s scheduling mode

Enable project managers to override default scheduling mode

IN T H IS TA SK IF Y O U REVISE UN IT S IF Y O UR REVISE DURAT IO N IF Y O U REVISE EF F O RT

Fixed units task Duration is recalculated Effort is recalculated Duration is recalculated

To turn on or off Project for the web:

Project for the web is not turned on for your organization

To turn off Project for the web for a user:

3. Look for the accountSKUid values that contain PROJECTPREMIUM or PROJECTPROFESSIONAL .

$LicenseOptionsPremium = New-MsolLicenseOptions -AccountSkuId "M365x115998:PROJECTPREMIUM" -DisabledPlans

$LicenseOptionsProfessional = New-MsolLicenseOptions -AccountSkuId "M365x115998:PROJECTPROFESSIONAL" -

ForEach ($UPN in $UPNList)

Turn Roadmap on or off

# Get all Power Platform DLP policies (Data Policies)

# Set desired DLP policy to be modified

# Verify DLP policy settings

Roadmap is not turned on for your organization

Turn Project Online off

Key Project apps

Project for the web Available Available Available

Roadmap Read-Only Available Available

Project Online Team member access Available Available

Project Online Desktop Not Available Available Available

Project for the web

Project Online Desktop Client

Maximum total tasks for a project 500

Maximum total duration for a project 3650 days (10 years)

Maximum total resources for a project 150

Maximum total links (successor only) for a project 600

Maximum total custom fields for a project 10

Maximum hierarchy level 10 levels