Cloud Drive Mapper (CDM) Provider Monitoring Service
The CDM Provider Monitoring Service is an Azure-hosted cloud service that helps improve CDM performance and troubleshoot problems. It monitors the connection between CDM and the provider (for example, Microsoft 365) for signs of deterioration, such as throttling. By continuously collecting and analyzing telemetry data, the CDM Provider Monitoring Service can detect throttling early.
CDM is a standalone desktop client that operates independently. Each instance doesn't know whether other clients in your organization are experiencing throttling. As a result, without the telemetry data and this service, multiple CDM clients may continue to make API calls, which can increase throttling across your organization.
The CDM Provider Monitoring Service enables each client in your organization to send data to our centralized telemetry API. Currently, the IAM Cloud telemetry API only analyzes data for patterns that could indicate throttling. In a future update, if a problem is detected, it will instruct all clients in your organization to temporarily reduce background operations until the risk of throttling decreases, while ensuring that CDM remains fully functional for users.
Telemetry data is collected with a strong focus on privacy and includes no Personally Identifiable Information (PII) or business-sensitive data. Telemetry data is kept in your organization's Azure data centre region and retained for 30 days to provide historical context if we need to investigate an issue. After 30 days, all data is automatically deleted.
From 19 September 2025, CDM will start sending telemetry data to us by default. However, you can opt out of using this service at any time by contacting our customer support team.
Telemetry data
The CDM Provider Monitoring Service collects the following telemetry data:
| Data type |
Description |
|---|---|
| UserMachineDiscriminator |
The hashed combination of device ID and remote user object ID. A hash is a one-way encryption algorithm. We have no way of knowing the user or the device from this. |
| SessionId | A unique identifier for the CDM session provided by license validation during startup. |
| RequestCategory |
The category of the API request assigned by CDM. |
| BackendService | The service handling the API request, such as Microsoft Graph or SharePoint. |
| CategoryResourceId | A unique identifier for the remote resource CDM is accessing. This is in the form of an ID, we never know any URLs or exact names. |
| EndpointType | The type of endpoint CDM is accessing, such as DirectOneDriveEndpoint or DirectSharePointSiteEndpoint. |
| RemoteDriveId | A unique identifier for the remote drive. |
| BifrostDriveId | A unique identifier for the drive mapping in Bifrost. |
| RateLimiting | Information about the number of API requests CDM can make within a set time, the remaining requests, and when the rate limit resets. |
| RetryAfterInSeconds | Indicates how long in seconds CDM waits before making another API request. |
Request categories
CDM assigns the following categories to every API request to help identify patterns and potential optimization areas:
| Request category name |
Description |
|---|---|
| Unknown |
Uncategorized |
| Delta | Delta query operations |
| FileContentRead |
Read file content |
| FileContentWrite | Write file content |
| ListItems | List directory items |
| ItemMetadataRead | Read directory item metadata |
| ItemMetadataWrite | Write directory item metadata |
| NodeOperation | Operations on the node of the file system: Create, Rename, Delete, and GetNodeInfo |
| Security | Security operations |
| Canary | Verifies CDM can connect to Microsoft Graph |
