Monitoring Benefit
The OneDrive section contains monitoring information for OneDrive Document Activity and OneDrive Folder Activity. Each shows the results of OneDrive synthetic transactions that simulate regular user activity — ENow performs the operation itself as the configured test user, rather than inferring health from a service status page.
Folder Activity covers the folder-level operations, where Document Activity covers operations on files. Both report a status and a latency for each transaction, so a test can pass and still tell you something useful by taking longer than it used to.
The transactions tested
| Transaction | What a failure usually means |
|---|---|
| Create a Folder | The most fundamental of the three. A failure here is normally authentication, permissions on the test user's OneDrive, or the service itself — and the other two will usually fail with it. |
| Rename a Folder | Write access is working but the update path is not. If Create passes and Rename fails, look at permissions and at any retention or locking policy applied to the test location. |
| Search for a Folder | Depends on the tenant search index, not just on OneDrive. See the note below — this one fails differently from the other two. |
Why "Search for a Folder" behaves differently
Create and Rename are direct operations: they either succeed or they do not. Search depends on Microsoft having indexed the folder, and indexing is asynchronous — it happens some time after the folder is created, and how long is not guaranteed.
The practical consequences:
- Search for a Folder can fail on its own while Create and Rename pass, and that is not necessarily a fault in OneDrive.
- It can fail intermittently, or fail from one probe location while passing from another, because each is searching at a slightly different moment.
- A newly configured test user is the most likely case of all — there is nothing indexed to find yet.
Treat a lone, intermittent Search failure as low priority. Treat Search failing consistently, or all three failing together, as a genuine finding.
Where the settings and thresholds are
Test user credentials — the same account used by Document Activity:
- For the Office-365 and ECLOUD-INTERNET tests, in the ENow Admin Console: Server > Tuning Policy > Settings > Office 365 > OneDrive > OneDrive User > Verify Credential.
- For the Remote Probe tests: Server > Tuning Policy > Settings > Probe Configuration > Configure Probes… > Default Office 365 Settings > OneDrive > Verify Credential.
Thresholds are configured in the Admin Console under Monitoring Policy > Thresholds, and are per-install. The latency indicators are evaluated against a configurable baseline rather than a fixed number, so confirm the values in force in your own console before treating a latency warning as unexpected.
How do we verify the monitoring test results?
- Test connectivity from the ENow web server. Open connectivity.office.com and follow the instructions to confirm the server can reach SharePoint Online, which is what backs OneDrive.
- Perform the same operation by hand. Sign in to OneDrive as the configured test user and create, rename and search for a folder. This is the most direct check available, and it separates a permissions problem on that account from a service problem.
- Compare the three probe contexts. The same transactions run from the ENow server, from ECLOUD-INTERNET and from any remote probes. A failure in one context and not the others points at that location's network path rather than at OneDrive.
Common warning or error results, and potential solutions
| Warning or Error | Potential solution |
|---|---|
| All three transactions failing | Start with the test user credentials, using Verify Credential at the console paths above. Expired passwords and Conditional Access changes are the usual causes — see Service Accounts: What Each ENow Component Needs, and Rotating Credentials and Conditional Access and ENow: Why Device-Based Policies Block Monitoring. |
| Only Search for a Folder failing | Usually search indexing rather than OneDrive. Confirm by searching for the folder by hand as the test user. If it is found manually, the index had simply not caught up when the check ran. |
| Create passes, Rename fails | Write access exists but modification is blocked. Check permissions on the test location and any retention or sensitivity policy applied to it. |
| Status green, latency raised | The operations are succeeding but slowly. Check the same transactions from a different probe location to establish whether it is network path or the service. |
| Failing from a remote probe only | Site-level networking. Check that location's egress, proxy and any TLS inspection, and confirm ENow's addresses are permitted — see Conditional Access and ENow: Why Device-Based Policies Block Monitoring and, for the addresses to trust, Network Requirements: Ports, Endpoints and Proxy Configuration. |
| A transaction is greyed out rather than red or green | The test did not run, rather than ran and failed. Confirm it is enabled and that the credentials for that context are configured. |
Further reading:
SharePoint and OneDrive diagnostics | Microsoft Learn
View Microsoft 365 service health | Microsoft Learn
Access denied or need permission error in SharePoint Online or OneDrive | Microsoft Learn
Comments
0 comments
Article is closed for comments.