| Previous | Next |
| FSRM_E_PROPERTY_MUST_APPLY_TO_FOLDERS | FSRM_E_PROPERTY_MUST_BE_GLOBAL |
FSRM_E_PROPERTY_MUST_BE_SECURE
FSRM_E_PROPERTY_MUST_BE_SECURE occurs when an authorization or protected-management feature is configured with an ordinary classification property. Secure properties are intended for scenarios where the metadata must participate in access policy without being freely modified like normal file classification data.
Use the correct security class of property
- Identify the feature requiring secure metadata, such as a Dynamic Access Control workflow.
- Select a resource property designed for secure use rather than converting an unrelated local property.
- Synchronize the definition and test that the target server supports secure properties.
Changing a flag solely to satisfy the API can alter who is allowed to write or trust the value. Treat secure property definitions as part of the authorization schema, review their allowed values and applicability, and migrate policy conditions deliberately. If the storage host cannot support secure properties, move the policy boundary instead of silently using an insecure substitute.
Dynamic Access Control · Automatic file classification · Create classification property
Looking for a different code? Search another status or error code.