| Previous | Next |
| ERROR_CLOUD_FILE_ALREADY_CONNECTED | ERROR_CLOUD_FILE_INVALID_REQUEST |
ERROR_CLOUD_FILE_NOT_SUPPORTED
The request is valid in CFAPI but unsupported by this provider
ERROR_CLOUD_FILE_NOT_SUPPORTED is a provider capability result. It should be distinguished from ERROR_CLOUD_FILE_INVALID_REQUEST, where the requested state transition or parameters are invalid. A provider may intentionally omit an optional callback, policy, placeholder-management feature, or operation that its remote service cannot represent safely.
Capture the exact CFAPI function or callback type and the sync-root policies in force. Check whether the request depends on optional validation, streaming, auto-dehydration, hard-link support, or placeholder-management permissions. The correct response may be to disable the UI action for that provider or implement the missing capability; retries with unchanged capability and policy cannot make the operation supported.
What to inspect
- Log the operation type and provider capability or policy that rejected it.
- Compare behavior with the callback table and CF_SYNC_POLICIES used at registration.
- Return a stable unsupported result instead of partially changing placeholder state.
References
- Microsoft: optional and required CFAPI callbacks
- Microsoft: hydration, population, hard-link, and management policies
- Microsoft: Cloud Filter function catalog
Looking for a different code? Search another status or error code.