Set new tab page quick links
Verified with Microsoft Edge 152.0.4191.53 — updated on July 12, 2026
Supported on: Microsoft Edge version 79, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge - Default Settings (users can override)\Startup, home page and new tab page User Configuration\Administrative Templates\Microsoft Edge - Default Settings (users can override)\Startup, home page and new tab page Description
By default, Microsoft Edge displays quick links on the new tab page from user-added shortcuts and top sites based on browsing history. With this policy, you can configure up to three quick link tiles on the new tab page, expressed as a JSON object: [ { "url": "https://www.contoso.com", "title": "Contoso Portal", "pinned": true/false }, ... ] The 'url' field is required; 'title' and 'pinned' are optional. If 'title' isn't provided, the URL is used as the default title. If 'pinned' isn't provided, the default value is false. Microsoft Edge presents these tiles in the order listed, from left to right, with all pinned tiles displayed ahead of nonpinned tiles. If you set this policy as mandatory, the 'pinned' field is ignored and all tiles are pinned. The tiles can't be deleted by the user and always appear at the front of the quick links list. If you set this policy as recommended, pinned tiles remain in the list but the user has the ability to edit and delete them. Quick link tiles that aren't pinned behave like default top sites and are pushed off the list if other websites are visited more frequently. When applying nonpinned links via this policy to an existing browser profile, the links don't appear at all, depending on how they rank compared to the user's browsing history. Example value: [ { "pinned": true, "title": "Contoso Portal", "url": "https://contoso.com" }, { "title": "Fabrikam", "url": "https://fabrikam.com" } ]
Registry
Software\Policies\Microsoft\Edge\Recommended Software\Policies\Microsoft\Edge\Recommended Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
Applying both scopes creates an ambiguous configuration (computer takes precedence over user). Only do this intentionally.
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Set new tab page quick links
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 79, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\Recommended]
"NewTabPageManagedQuickLinks"=""More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Set new tab page quick links
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 79, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\Recommended'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NewTabPageManagedQuickLinks' -Value '' -Type StringIntune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune.Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Set new tab page quick links
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 79, Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Edge\Recommended' -Name 'NewTabPageManagedQuickLinks' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Set new tab page quick links
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 79, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\Recommended'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NewTabPageManagedQuickLinks' -Value '' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: Set new tab page quick links
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 79, Windows 7 or later
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: Set new tab page quick links
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 79, Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Edge\Recommended' -Name 'NewTabPageManagedQuickLinks' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Set new tab page quick links
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 79, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\Recommended'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NewTabPageManagedQuickLinks' -Value '' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.