3 results found
Not planned as MSFT doesnt have API’s for us to build this integration. Would request all customers to provide feedback to your respective MSFT reps
An error occurred while saving the commentAnonymous commented
It would also be helpful to enforce such requirements on folders shared with you/the company by external organizations as well. Currently my work account had folders shared with us from other external companies (our customers) which have files in them with question marks and colons in the name, but since myself/my company were not provided high enough permissions, we are unable to edit the file names and have to just live with the constant notifications from box for these folders/files unless we contact our customer and ask them to change their file names which is not practical.
If something could be worked into the feature to where you could specify that certain characters are limited, AND enforce the same on folders shared with users in your organization. I know that might not be enforceable, but maybe at least have emails sent to folder owners if the shared folders contain unsupported characters by the organization that they shared with.