This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 80%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECT%3C/text%3E%3C/svg%3E)
I would like to know the reg key or GPO in the admin templates to automatically enable inclusiveness settings in Office/Word in the Grammar & Refinements Proofing Tools (File > Options > Proofing > Writing Style > Grammar & Refinements > Settings > Inclusiveness). My team is looking to explore if it's technically feasible to make this a global setting under HKLM or if it needs to be enabled in HKCU. I was not able to find any specific articles or postings about this so any assistance would be appreciated. In addition to Windows clients, I would like to know how to enable this on Mac clients as well.
This is for M365 Apps for Enterprise x64 (v2002 and v2008) on the Windows side and for v16.46 on the Mac side.
Currently, I do not find any relevant documentation from Microsoft explain the related registry or group policies to enable these Inclusiveness options of writing style.
Besides, Inclusiveness options is not yet available in Word for Mac at present.
Thanks for your understanding.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEO%3C/text%3E%3C/svg%3E)
I had a ticket open with Microsoft, asking this same question. Their response... there is currently no GPO setting, but they are aware of the need for one. Premier support attempted to hack together a registry fix that I could deploy to all clients, but it was messy overall and inconsistent. So we opted not to use it in the end, and we'll wait for an actual GPO.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 28.999999999999996%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
Can you share what they provided
We never produced a solution, but these are the keys that Microsoft was testing/editing with me.
Computer\HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\Grammar\MSGrammar\8.0\2057
Computer\HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\Grammar\MSGrammar\8.0\1033
(These reg keys are being set when you enable inclusiveness options in Word)
Here are some tests we performed.
TEST 1
1. I started on a computer (VM) that has never had the inclusiveness settings enabled.
2. The Office version is on 2002 (12527.21330) Semi-Annual Channel Enterprise.
3. The registry entries were blank.
4. I enabled the three inclusiveness settings
5. The REG_BINARY data looks like this
a. Windows Registry Editor Version 5.00
b. [HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\Grammar\MSGrammar\8.0\1033]
c. "Word"=hex:00,db,87,98,01,00,00,00,fd,bc,60,aa,2f,75,8e,42,ab,6b,a0,77,09,65,\
d. 74,f6,03,00,00,00,d6,6c,11,dd,db,2a,e9,4b,80,9f,7b,8d,e7,ca,ce,91,01,00,00,\
e. 00,2a,bc,7b,e7,96,f8,12,40,a7,11,60,41,ea,1e,89,64,01,00,00,00,f1,53,73,f4,\
f. b7,e9,ff,4f,81,29,b6,d1,09,ec,e4,35,01,00,00,00
g. "WordPersonalizations"=hex:00,db,87,98,00,00,00,00
h. "WordDisabledPreviews"=hex:00,db,87,98,00,00,00,00
6. I removed the inclusiveness settings
7. Removing the settings did not remove the registry keys, they remained set.
TEST 2
1. I started on a computer (VM) that has never had the inclusiveness settings enabled.
2. The Office version is on 2011 (13426.20274) Current/Monthly Channel (I manually updated it for this test, because I know it adds additional inclusiveness options.)
3. The registry entries were blank.
4. I enabled the eight inclusiveness settings
5. The REG_BINARY data looks like this
a. Windows Registry Editor Version 5.00
b. [HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\Grammar\MSGrammar\8.0\1033]
c. "Word"=hex:00,db,87,98,01,00,00,00,fd,bc,60,aa,2f,75,8e,42,ab,6b,a0,77,09,65,\
d. 74,f6,08,00,00,00,af,88,22,93,f4,0a,f8,43,94,af,20,6e,06,e4,3f,ce,01,00,00,\
e. 00,75,d5,0b,6c,e0,55,5e,41,99,6e,4e,0f,00,8a,29,25,01,00,00,00,d6,6c,11,dd,\
f. db,2a,e9,4b,80,9f,7b,8d,e7,ca,ce,91,01,00,00,00,ca,6c,d6,6c,c2,c2,cf,48,83,\
g. 53,97,91,32,7a,ae,a1,01,00,00,00,d2,1a,41,5d,65,a9,01,4c,b4,25,ec,ce,2b,37,\
h. 4d,fa,01,00,00,00,2a,bc,7b,e7,96,f8,12,40,a7,11,60,41,ea,1e,89,64,01,00,00,\
i. 00,46,91,86,36,c3,3c,fd,40,ae,3c,bb,30,f6,98,83,35,01,00,00,00,3d,7e,ac,cb,\
j. 58,90,2c,44,9f,24,78,fe,16,40,69,b4,01,00,00,00
Thanks EricOhlin - it works for me. I exported the Reg Key and tested it with 3 different users on different VMs
Thanks EricOhlin - Seems to work for me - Now I must get a script to load the key for users on startup (for all users) or login
Powershell or Batch file?
Hey @Joseph Cann ,
It sounds like you're on the correct path. There are a number of methods you could deploy this. GPO, SCCM, Intune, Etc. , utilizing Powershell or Batch; whichever you're comfortable with.
A word of Caution, this is where we halted efforts (as a large enterprise with many different configurations); take note of line 2 in my code.
The Office version is on 2002 (12527.21330) Semi-Annual Channel Enterprise.
The Office version is on 2011 (13426.20274) Current/Monthly Channel
The versions of Office are different. Then take note of the ""Word"=hex:" values. The Hex values are different because each version of Office has slightly different options and features related to inclusiveness settings.
Questions to ask...
... you see where I'm going with this. I think this solution is only viable in the most specific of situations.
Cheers!