Enable Microsoft Visual Basic for Applications project creation
| Registry value | createvbaprojects |
| Group Policy | Enable Microsoft Visual Basic for Applications project creation |
| German version | Projekterstellung mit Microsoft Visual Basic for Applications aktivieren |
| Intune settings catalog | Enable Microsoft Visual Basic for Applications project creation (User) |
| Scope | User · HKCU |
| ADMX | visio16.admx · L_EnableMicrosoftVisualBasicforApplicationsproject |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\visio\application | |
| createvbaprojects | Enabled = 1 · Disabled = 0 |
Not configured = the value does not exist – the application default applies and users may change the setting.
PowerShell
Check the current value (read-only)
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
$key = "$root\Software\policies\microsoft\office\16.0\visio\application"
foreach ($name in @('createvbaprojects')) {
try { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
catch { '{0}: not configured' -f $name }
}Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.
Enable
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
try {
$key = "$root\Software\policies\microsoft\office\16.0\visio\application"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'createvbaprojects' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null # Enabled
'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }Disable
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
try {
$key = "$root\Software\policies\microsoft\office\16.0\visio\application"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'createvbaprojects' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null # Disabled
'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }Reset to Not configured
# --- Settings --- $root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>' $key = "$root\Software\policies\microsoft\office\16.0\visio\application" Remove-ItemProperty -Path $key -Name 'createvbaprojects' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Enable Microsoft Visual Basic for Applications project creation (User)
Settings catalog → Add settings → search for the name above.
Intune Settings Catalog Viewer ↗
Alternative: custom profile (OMA-URI)
| OMA-URI | ./User/Vendor/MSFT/Policy/Config/visio16v2~Policy~L_MicrosoftVisio~L_VisioOptions~L_Security~L_MacroSecurity/L_EnableMicrosoftVisualBasicforApplicationsproject |
| Data type | String |
| Value | <enabled/> · <disabled/> |
Cloud Policy
Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Enable Microsoft Visual Basic for Applications project creation. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
Enables creations of VBA projects when you open (or create) a document that does not already contain a project. If you clear this check box, you will not be able to create a macro in a document that does not already contain a project.
Same category: Microsoft Visio 2016 › Visio Options › Security › Macro Security
- Load Microsoft Visual Basic for Applications projects from textloadvbaprojectsfromtext
All policies in this category · All 98 policies of visio16.admx