You will recognize these as file types for Microsoft Office apps. The following list includes the remaining file types that support native protection by the Azure Information Protection unified labeling client, and that can also be classified. If you have firewalls, web proxies, or security software that inspect and take action according to file name extensions, you might need to reconfigure these network devices and software to support these new file name extensions. When files are generically protected, the original file name extension is always changed to. These file types are identified separately because when they are natively protected, the original file name extension is changed, and these files become read-only. The following table lists a subset of file types that support native protection by the Azure Information Protection unified labeling client, and that can also be classified. Supported file types for classification and protection The protection can be applied automatically when a user selects a sensitivity label that an administrator has configured, or users can specify their own custom protection settings by using permission levels. For more information, see Change which file types to protect. However, you can change which file types are protected. You cannot change the default protection level that the Azure Information Protection unified labeling client or the scanner applies. rtf, and so on) that are not supported by native protection. However, usage rights are not enforced.ĭefault level of protection for the following file types: - Text and image files - Microsoft Office (Word, Excel, PowerPoint) files - Portable document format (.pdf) For more information, see the following section, Supported file types for classification and protection.ĭefault protection for all other file types (such as. Audit logging of authorized users opening and accessing files occurs. Usage rights and policy set by the content owner are displayed to inform authorized users of the intended usage policy. If authorization fails, the file does not open. Additionally, usage rights and policy that were set by the content owner when the files were protected are enforced when the content is rendered in either the Azure Information Protection viewer (for protected text and image files) or the associated application (for all other supported file types).įile protection is enforced in the following ways: - Before protected content is rendered, successful authentication must occur for people who are authorized to open the file and given access to it. pfile file type and authentication to verify if a user is authorized to open the file.įile protection is enforced in the following ways: - Before protected content is rendered, successful authentication must occur for those users who receive the file through email or are given access to it through file or share permissions. pdf files, and other application file types that support a Rights Management service, native protection provides a strong level of protection that includes both encryption and enforcement of rights (permissions).įor other supported file types, generic protection provides a level of protection that includes both file encapsulation using the. Type of protectionįor text, image, Microsoft Office (Word, Excel, PowerPoint) files. The Azure Information Protection unified labeling client supports protection at two different levels, as described in the following table. You could also apply just protection to these files, without classification. If the Confidential \ All Employees sensitivity label applies classification and protection: You could apply this label to a file named sales.pdf and a file named sales.txt. If the General sensitivity label applies classification and does not apply protection: You could apply the General label to a file named sales.pdf but you could not apply this label to a file named sales.txt. For these file types, see the Supported file types for classification and protection section. Other file types support classification when they are also protected.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |