policy
90 TopicsOfficial Download links for Microsoft Edge Stable Enterprise
I'm not 100% sure it's final but anyone who wishes/wants can test it. Microsoft Edge Stable Enterprise X64.msi http://go.microsoft.com/fwlink/?LinkID=2093437 X86.msi http://go.microsoft.com/fwlink/?LinkID=2093505 MicrosoftEdgePolicyTemplates.cab http://go.microsoft.com/fwlink/?LinkID=2099616 MicrosoftEdgeIntunePolicyTemplate.cab http://go.microsoft.com/fwlink/?LinkID=2099617 macOS.pkg http://go.microsoft.com/fwlink/?LinkID=2093438 Blocker Toolkit to disable automatic delivery of Microsoft Edge https://docs.microsoft.com/en-us/deployedge/microsoft-edge-blocker-toolkit87KViews3likes20Comments[UPDATED]: Microsoft UEFI Signing Requirements
To strengthen the Secure Boot ecosystem and streamline signing turnaround, Microsoft is introducing enhanced UEFI signing requirements for all third-party submissions requesting signatures with Microsoft UEFI CAs (2011 and 2023) or the new Option ROM CA. These updates emphasize security assurance and interoperability across UEFI-enabled devices. Key changes include: Mandatory security audits: Annual independent reviews via the OCP SAFE program, with immediate audits for vulnerabilities or major code changes. Subsystem-based packaging: EFI Applications and Option ROMs must be submitted separately for proper certificate alignment; mixed packaging will be rejected. Stricter code eligibility: Only production-quality binaries, free of GPLv3 licensing, free of known vulnerabilities, and free of malware-prone components will be signed. Enhanced security posture: Requirements for NX compatibility, memory safety, and SBOM inclusion in PE sections are now enforced. Special handling for SHIM and iPXE: SHIM submissions require review board approval or SAFE audits; iPXE submissions must meet additional security criteria.84KViews2likes5CommentsImportant change released for Guest Configuration audit policies
An important change has been released to policies in category Guest Configuration. The policy format has been updated to address customer feedback, to simplify the experience of auditing settings inside machines. Existing policies that were assigned prior to this release will continue to display accurate results and will not be deleted in the near future. For new policy assignments, only the updated definitions are available. In the new experience, a single initiative handles all prerequisite requirements. Once the prerequisites are completed, Audit policies may be added/removed without needing to run remediation tasks. Switching to the new experience requires assigning the new definitions.Configure Dial Out policies for all users
HI, Is there a way to configure a policy I can assign to users to block them from making international calls and limit them to domestic only. By default users seem to have international calling permission. I know I can go into each user one at a time and set this setting, but with hundreds of users this isn't a sensible approach. I want the default policy to be to block international, then a 2nd policy to Allow that I can apply to specific users. Thanks.26KViews0likes2CommentsEdge Stable 103.0.1264.37 breaks group policy management of the browser - Critical
Going from version 102.0.1245.44 (June 16) to 103.0.1264.37 (June 23), we started experiencing the following issue. Our AD Domain Joined machines running Edge and being managed via Group Policy, unload their policy set on every gpupdate (foreground or background). To reproduce this, just go to edge:\\policy and see your policies. Then, do a gpupdate and once it completes, visit that page again. It will show an empty set of policies (Although the policies are there in the registry). The only way to re-apply the policies is to: 1. Wait for the browser itself to do it (Reload Policy), could take any number of minutes 2. Click the Reload Policy button on Edge:\\policy This results in all Externsions being re-installed, the centralized boomarks re-applied etc and it is both a problem raised by our end users because they see their extensions being re-installed on every gpupdate and we no longer are sure that our endpoint browsers are managed.Solved24KViews3likes34CommentsFederated vs Trusted organizations in Meeting Policies
Hi Team gurus! I have been testing out the Microsoft Teams meeting policies for a client and I'm curious if anyone else is experiencing the same behavior in the Lobby option as I am: The global policy set in the Teams Admin Center is set to Automatically admit people who is a part of the organization or federated organization: However, when i choose the Meeting Options for the specific Teams meeting, the policy looks like this: In my test scenario, all authenticated organizations (in my example my other Microsoft account, that is not in any way federated with the tenant) can join by bypassing the Lobby function. When using my gmail account, the user shows up as a "Guest" and I'm told to enter my Display name when joining the meeting and then I'm placed in the lobby. Can anyone specify the difference between federated and trusted (unless federated actually means trusted as in my test case?), as I cannot find this in the Meeting Policy docs or anywhere else. Thanks in advance23KViews0likes7Comments