iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Use Intune’s Windows device-restriction setting Allow full screen mode to control whether Microsoft Edge can enter full-screen mode. Set it to Yes to permit full screen, or No to prevent users, apps, and extensions from entering it.
This browser permission is separate from configuring Windows as a kiosk. A disabled full-screen policy also prevents command-line launching of Edge kiosk mode, so signage and other kiosk deployments need an additional design check.
Identify the policy before changing it
In Intune, the setting is shown as Allow full screen mode. Microsoft Edge’s underlying mandatory browser policy is named FullscreenAllowed. The two names describe the same control: Intune supplies the administrative setting, while Edge applies the browser policy.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11| Intune choice | Edge policy state | Effect on Edge | Kiosk consequence |
|---|---|---|---|
| Yes | Enabled | Users, applications and extensions with the required permissions can enter full-screen mode. Edge hides its browser interface and displays only web content. | Does not, by itself, create a kiosk. It leaves the fullscreen capability available for a kiosk configuration that needs it. |
| No | Disabled | Users, applications and extensions cannot enter full-screen mode. | Command-line launching of Edge in kiosk mode is unavailable. Validate this impact before assigning the setting to signage or other kiosk devices. |
| Not configured | Not configured | The policy reference treats this like the enabled/default state: fullscreen remains available where the caller has permission. | No explicit Intune block is applied, but kiosk behavior is still controlled by the separate kiosk and Edge configuration. |
Technical policy details
FullscreenAllowed is a Boolean mandatory policy for Windows and is documented for Microsoft Edge version 77 and later. The policy reference identifies the Group Policy location as Administrative Templates/Microsoft Edge and the registry location as SOFTWAREPoliciesMicrosoftEdge, using the FullscreenAllowed value with type REG_DWORD. Those details help when diagnosing policy precedence; an Intune administrator should configure the Intune profile rather than manually editing the registry.
#1 Best Overall
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
The policy reference lists dynamic policy refresh as supported. That means Edge can receive a refreshed administrative value without waiting for a new browser build, but it does not promise a universal delivery time for every device. Confirm the assignment and the resulting behavior on representative endpoints.
What enabling or disabling full screen changes
When the setting is allowed, Edge can transition into its full-screen presentation so that the browser chrome is hidden and the web page is the visible content. The permission applies beyond a person pressing a browser control: applications and extensions can also request full screen when their own permissions allow it.
When the setting is blocked, the browser policy denies those requests. This is a browser capability restriction, not a general Windows display policy. It does not configure an account, lock a device to one application, or define which website should open. Those are separate controls.
Configure the setting in Microsoft Intune
Microsoft’s documentation establishes the setting and the separation between device restrictions, Edge browser settings and kiosk profiles, but administrative-center labels can change between tenants. Use the following procedure as a configuration sequence rather than relying on a fixed portal screenshot.
- Work in a Windows device-configuration profile. Create or edit the Windows device-restriction profile that will govern the target devices. Do not look for this control in a mobile-device profile; the Edge policy is documented for Windows.
- Locate “Allow full screen mode.” Use the profile’s settings search or the Edge-related browser restrictions area to find that exact friendly name. Confirm that the setting maps to the Microsoft Edge policy
FullscreenAllowed. - Choose the required value. Select Yes when approved websites, applications or extensions must be able to use Edge full screen. Select No when the organization must keep the Edge interface available and prevent fullscreen requests.
- Review the assignment scope. Assign the profile to the device groups that should receive the policy. If a device is used as a kiosk, include the same device population in the related kiosk and Edge-specific profiles, as Microsoft’s kiosk guidance recommends.
- Save and deploy. Complete the profile assignment and watch the device-configuration status. A successful assignment indicates that Intune accepted the profile; it does not, by itself, prove that Edge on every endpoint has refreshed and enforced the value.
- Allow the endpoint to synchronize. Use your organization’s normal Intune sync process, then check the device’s policy status for errors, conflicts or a pending state. Dynamic refresh is supported by the Edge policy, but delivery and application still depend on the device being online and healthy.
- Test the user experience. On a pilot device, test a normal user attempt, an approved application or extension that requests full screen, and any kiosk workflow. Record the result before broad deployment.
Choose the right value for common scenarios
| Scenario | Recommended value | Reason |
|---|---|---|
| Managed desktops where employees use web applications that need an unobstructed presentation | Yes | Permits fullscreen requests while leaving other device restrictions unchanged. |
| Shared workstations where staff must always see the Edge interface | No | Blocks fullscreen requests from users, applications and extensions. |
| Digital signage using Edge kiosk mode | Validate first; usually keep fullscreen permitted | Disabling the policy removes command-line kiosk launching, which can prevent the intended startup method. |
| Public browsing kiosk | Decide separately from the kiosk profile | The kiosk experience and its browser restrictions are separate configuration tasks; fullscreen permission alone does not define public browsing. |
Fullscreen permission is not the same as Edge kiosk mode
A full-screen browser window and a Windows kiosk are different layers. FullscreenAllowed answers whether Edge is allowed to enter its fullscreen presentation. A kiosk profile determines how Windows signs in, restricts the shell and runs the assigned kiosk application. Edge-specific browser settings are configured separately.
Digital/Interactive Signage
Edge’s Digital/Interactive Signage experience is intended to display a specific site full screen. The cited Edge kiosk documentation describes this as a kiosk experience running in InPrivate mode. Because the startup flow commonly relies on launching Edge in kiosk mode, disabling FullscreenAllowed can make that command-line launch unavailable. Treat the policy as a dependency to validate, not as a substitute for the kiosk profile.
Rank #2
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
Public Browsing
Public Browsing provides a limited multi-tab experience rather than a single fixed signage page. It also runs in InPrivate mode under the documented Edge kiosk model. The browser experience, allowed navigation and Windows restrictions must be designed in the kiosk and Edge profiles; changing the fullscreen permission alone does not produce Public Browsing.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Profile assignment
Microsoft’s Intune kiosk guidance calls for a kiosk profile and a device-restrictions profile for the relevant Edge features and settings, assigned to the same devices. Keep those assignments aligned. If the kiosk profile targets one group while the Edge policy targets another, the device can receive only part of the intended configuration.
Microsoft also advises testing additional Edge policies so that a restriction does not interfere with kiosk functionality. Pilot the complete combination, including automatic sign-in, the target URL, navigation controls, printing or downloads if applicable, and the startup method used by the organization.
Platform and version boundaries
| Item | Documented scope | Administrative implication |
|---|---|---|
FullscreenAllowed |
Windows; Microsoft Edge 77 and later | Use a Windows Edge policy profile. The reference lists macOS, Android and iOS as unsupported for this policy. |
| Edge kiosk experiences | Microsoft Edge 87 and later; available in the Stable Channel according to the kiosk documentation | Confirm the installed Edge version before depending on kiosk-specific behavior. |
| Intune Windows kiosk configuration | The current reference includes Windows 10, but Windows 10 reached end of support on October 14, 2025. | Check your organization’s operating-system lifecycle and current Intune eligibility. Functionality on an out-of-support platform is not guaranteed. |
The platform limitation matters when a single policy is assigned to mixed operating systems. A configuration intended for Windows Edge should not be treated as a cross-platform control for mobile or macOS Edge clients.
Verify that the policy reached the endpoint
Use a small pilot group before assigning the setting broadly. Verification should establish both administrative delivery and browser behavior.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- Confirm assignment: Check that the device is a member of the intended group and that the profile reports a successful state rather than pending, error or conflict.
- Check for competing configuration: Review other Intune profiles, legacy Group Policy objects and security baselines that may also define Edge policies. The effective value must be understood before interpreting a test result.
- Test both states: On a permitted device, verify that an approved fullscreen request works. On a blocked device, verify that the same type of request is denied.
- Test the actual account and application: Fullscreen requests can come from users, applications or extensions. A result from one account or site may not represent every caller.
- Record kiosk behavior separately: If the device is a kiosk, test its complete startup path after changing the value. A normal desktop test cannot prove that a command-line kiosk launch will work.
Troubleshoot common results
The setting does not appear in the profile
Check that you are editing a Windows device-restriction profile and searching for the friendly name Allow full screen mode. The underlying Edge policy is Windows-specific and documented from Edge 77 onward. A macOS, Android or iOS profile will not provide this control.
Rank #3
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Fullscreen still works after selecting No
First confirm that the target device received the assignment and has no profile error or conflict. Then verify that you tested the same device and account covered by the assignment. Allow time for synchronization and retest. If a legacy Group Policy or another management system also configures Edge, determine which effective policy is winning rather than assuming the Intune value is the only input.
Fullscreen is blocked when it should be allowed
Check whether another profile sets the policy to No, whether the device is outside the intended assignment, and whether the application or extension has the permissions it needs. The Intune value of Yes permits fullscreen; it does not grant permissions that the requesting application does not possess.
Edge kiosk no longer starts
Review whether FullscreenAllowed was disabled. Microsoft states that disabling it makes command-line launching of Edge in kiosk mode unavailable. Restore an allowed value if the kiosk startup method requires that command, then verify the separate Windows kiosk profile and Edge settings on the same device group.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe device is running Windows 10
Windows 10 reached end of support on October 14, 2025. Although the Intune reference still lists it as an allowed version, Microsoft does not guarantee that every eligible feature will continue to behave uniformly. Confirm your support plan and test the exact Windows and Edge builds used in production.
Operational recommendations
- Use Yes when fullscreen is a documented application requirement, not merely because a kiosk is planned.
- Use No when preventing concealment of the browser interface is a deliberate user-experience or control requirement.
- Keep the fullscreen decision separate from kiosk design. A kiosk profile, an Edge configuration and the fullscreen permission solve different problems.
- Assign related profiles to the same device population and pilot them together.
- Document the Edge version, Windows edition, assignment group and test result for each kiosk rollout, especially on Windows 10 devices.
- Re-test after changing other Edge policies, because Microsoft cautions that additional restrictions can affect kiosk functionality.
Practical decision
For ordinary Windows Edge management, set Allow full screen mode to Yes to preserve fullscreen capability or No to block it. For a kiosk, make that choice only after confirming the kiosk startup method: a disabled FullscreenAllowed policy prevents command-line Edge kiosk launch, while the kiosk profile and Edge-specific settings must still be configured and assigned independently.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
