The Microsoft Project connector is a Palantir-provided driver for Microsoft Project.
To create a new Microsoft Project source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Microsoft Project-specific configuration and networking. For the complete property reference, see the official Microsoft Project driver documentation ↗.
| Capability | Status |
|---|---|
| Exploration | 🟢 Generally available |
| Batch syncs | 🟢 Generally available |
| Incremental | 🟢 Generally available |
| OAuth 2.0 authentication | 🟢 Generally available |
The properties below are mandatory or recommended.
| Property | Required? | Description | Default |
|---|---|---|---|
URL ↗ | Mandatory | URL to the MS Project Web App. For example, https://MyOrganization.sharepoint.com/sites/pwa/. | https://contoso.com/sites/pwa/ |
AuthScheme ↗ | Recommended | The scheme used for authentication. Accepted entries are SharePointOnlineCookies,OAuth,OKTA,ADFS,AzureAD and OneLogin. | SharePointOnlineCookies |
InitiateOAuth ↗ | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | REFRESH |
OAuthClientId ↗ | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
OAuthClientSecret ↗ | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
Password ↗ | Recommended | Specifies the password of the authenticating user account. | — |
Schema ↗ | Recommended | The type of schema to use: ODataV1 or ODataV2. | ODataV2 |
User ↗ | Recommended | Specifies the user ID of the authenticating Microsoft Project user account. | — |
The table below lists the domains that the source must be able to access to run.
For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead. The agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.
| Domain | Required |
|---|---|
| <URL> | Always |
| <SSOLoginURL> | If AuthScheme=ADFS, OKTA |
| login.microsoftonline.com | If AuthScheme=AzureAD, OAuth AND AzureEnvironment=GLOBAL (default) |
| login.chinacloudapi.cn | If AuthScheme=AzureAD, OAuth AND AzureEnvironment=CHINA |
| login.microsoftonline.us | If AuthScheme=AzureAD, OAuth AND AzureEnvironment=USGOVT or USGOVTDOD |
| <Subdomain>.onelogin.com | If AuthScheme=OneLogin, set in SSOProperties |
This connector supports OAuth 2.0 authentication. Follow the OAuth 2.0 guidance for Palantir-provided drivers to configure and authorize the connection.