There is a limit of 50 keyword dictionary based sensitive information types that can be created per tenant. 1 MB of post compression limit means that all dictionaries combined across a tenant can have close to 1 million characters. The tenant limit is also 1 MB after compression. Keyword dictionaries provide simpler management of keywords and at a much larger scale, supporting up to 1 MB of terms (post compression) in the dictionary and support any language. Although you can create keyword lists in sensitive information types, keyword lists are limited in size and require modifying XML to create or edit them. Identifying sensitive items sometimes requires looking for keywords, particularly when identifying generic content (such as healthcare-related communication), or inappropriate or explicit language. I am unsure whether this resolves the original issue for this thread but I did not find this complete a description anywhere so hopefully it helps someone.Learn the basic steps to creating a keyword dictionary in the Office 365 Security & Compliance Center.ĭata loss prevention (DLP) can identify, monitor, and protect your sensitive items. The user ID is not available until the user signs on to their account once on the machine. This is by user/ID/account so there can be a new first dictionary, second, etc for a different user ID.Ĭomputer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities\xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_ADALĬomputer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities\xxxxxxxxxxxxxxxx_LiveId The second dictionary would start with a 2. The state determines if the dictionary is enabled The rest of the key name is the identity that you can find below in the registry. The first number is the first dictionary and will be default. "1_16_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_ADAL"="C:\\TEMP\\somecustom.dic"
If you have any feedback on our support, please click Regards,Ĭome back and mark the replies as answers if they help and unmark them if they provide no help. This method doesn't bring you to the direct solution but may be a way to find it. To the new Office install, check the registry settings under "HKCU\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Custom Dictionaries" to know what changes have been made to let it take effect. On the new Office, open Word -> FILE -> Options -> Proofing -> When correcting spelling in Microsoft Office programs -> Custom Dictionaries -> Click "Add" and browse to the dictionary file, open it.
If you've saved other custom dictionaries in different folders, copy them too. To transfer the custom dictionary, copy the custom dictionaries to your transfer location.
Us know how to modify the registry keys to accomplish the migration. Since I don't have the exactly same environment, I suggest you try to manually transfer the user's dictionary, after the dictionary is added to Office 365 Application, check what changes have been made in the Registry settings, maybe this can let If you add the registry items in the article to the above key once the users have migrated to office 365 it doesn't work.Īny advice about how we can get our custom dictionary deployed to all of these users without wiping out all of their custom dictionaries would be greatly appreciated. However after Office 365 it appears users are logging into Office applications with their Organisational account and we're seeing the following registry changes a nd the custom dictionaries are However we want to avoid clearing all of the values out of "HKCU\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Custom Dictionaries" because this will mean that any custom dictionaries our users have manually added will be lost.īelow is the result of GPP registry items we have in place to set custom dictionaries. If we clear all of the values out of "HKCU\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Custom Dictionaries" and then add the dictionaries in as per the below article's instructions Word will use our custom dictionaries.
We are currently in the process of migrating some of our user accounts to Office 365 during which we have discovered that once these account are migrated they are no longer using the organisations custom dictionary we deploy via group policy toĪll users.