Outbound Anti‑Spam Policy “Include/Exclude” Please Correct
Proposed Feedback to Microsoft: Outbound Anti‑Spam Policy UI Behavior Is Misleading and Needs Clarification Title: Outbound Anti‑Spam Policy “Include/Exclude” UI is Misleading — Policy Applies Globally Unless Exclusions Are Defined Summary of the Issue The Outbound Anti‑Spam Policy interface in the Microsoft 365 Defender portal presents an Include and Exclude user scope model that strongly implies modern scoping behavior: Include = users the policy applies to Exclude = users the policy does not apply to However, this is not how the backend policy engine behaves. In reality: If the Exclude list is empty, the policy applies to all users unless they are explicitly excluded. This is the opposite of what the UI suggests, and it leads to unexpected and incorrect assumptions by administrators. Actual Behavior (Backend Logic) The outbound anti‑spam engine still uses legacy logic: A policy applies to a user unless the user is explicitly excluded Being “not included” does not prevent the policy from applying The highest‑priority policy that does not explicitly exclude a user is the one that applies This means: If the Exclude list is empty, the policy effectively becomes global. This is not communicated anywhere in the UI. Impact on Administrators This behavior leads to: Users unintentionally being governed by the wrong policy External forwarding being allowed for users who were never intended to be included Confusion when removing a user from the Include list does not remove them from the policy Misinterpretation of policy priority and scope Hours of troubleshooting because the UI does not reflect the actual evaluation logic This is especially problematic when configuring forwarding exceptions, where security expectations are high. Example Scenario Demonstrating the Problem Admin creates a Priority 1 policy allowing external forwarding for a small set of users. Admin adds those users to Include. Admin leaves Exclude empty, assuming the policy applies only to the included users. A user not in the Include list still has forwarding allowed because the policy applies globally unless excluded. Removing a user from Include does not remove them from the policy. The admin is misled because the UI suggests the opposite behavior. This is counterintuitive and contradicts the scoping model used in other Microsoft 365 policies. Requested Fix Add a warning or informational banner when the Exclude list is empty. Suggested wording: Warning: No users or groups are excluded. This policy will apply to all users unless they are explicitly excluded. Users not listed in “Include” may still be affected by this policy. This one clarification would prevent the majority of misconfigurations and support cases related to outbound forwarding exceptions. Why This Matters Outbound forwarding is a high‑risk vector for data exfiltration. Admins rely on the UI to understand policy scope. The current UI leads to incorrect assumptions and unintended exposure. A simple warning would align the UI with the actual behavior of the policy engine and prevent misconfigurations. End of Feedback As you may have noticed, the above response is based on questions and answers I got from Copilot. This is a valid improvement that needs to be made, but furthermore Microsoft is losing a great deal of information by not allowing a direct route from Copilot to the correct area of your company when a solution or a correction to a current method is discovered. Best regards, Gary Huber
Windows 11 25H2 – Update KB506881 causes unexpected reboots (no BSOD, silent restart)
Hey everyone, just wanted to report a serious issue I encountered with Windows 11 25H2 related to the update KB506881. After installing KB506881 my PC randomly rebooted without warning — no BSOD, no crash report, no error on screen. Only the event log showed “unexpected shutdown / Kernel-Power (Event ID 41)”. Removing the update completely solved the issue. Since uninstalling it, my system has been 100% stable with zero unexpected restarts. Reproducibility: Install KB506881 → system performs unexpected shutdowns / reboots Uninstall KB506881 → issue disappears immediately System details: Windows 11 25H2 (Build: 26200) AMD Ryzen 7800X3D (but issue seems unrelated to hardware) No BSOD / no memory dump / no bugcheck created Reliability Monitor only shows “Unexpected Shutdown” What I already did: Removed KB506881 manually → issue gone Blocked the update using PowerShell + scheduled task (hourly) to prevent Windows from reinstalling it Logs: Event Viewer → Windows Logs → System Shows: Kernel-Power 41 (unexpected shutdown) immediately after KB506881 installation. Has anyone else experienced unexpected reboots after KB506881? If yes, please comment so Microsoft can see how widespread this is. I also reported it via Microsoft Feedback Hub. Thanks!Teams: Translation of "More meet now options"
Hi The button to converting a chat into a Video or Audio call, is named "More meet now options" in English. But the Swedish translation is "Fler möte bu-alternativ". "Now" is translated to "bu". "Bu" is a very scary word for small children in Sweden, as "Boo" is in English. Please correct to "Fler möte nu-alternativ" or better only "Fler mötesalternativ". Regards, Anna-KarinTranslation of Block arrows in Swedish Power BI Desktop
Hi The alternative Block Arrows under the menu Insert >Shapes, is translated to Blockera pilar in Swedish version Power BI Desktop and that means Prevent Arrows, instead of Blockpliar. In other Microsoft program are Block Arrows translated to Blockpliar in Swedish. Please use it in Power BI Desktop to. Version: 2.148.1226.0 64-bit (oktober 2025) Regards Anna-Karin
Allow own editing after posting a new question into any of Community Lounge Discussion Boards
Right after posting my new question into one of Community Lounge Discussion Boards I noticed that it was no more possible to edit it again in case any correction might have been needed. While I noticed doing the same editing was indeed allowed after adding a reply to my own question, so basically I'm just asking for some more consistency... 😇 Many thanks in advance for your attention. Best Regards RobEdge randomly gets reset and logs me out of every site
Hello, I need help, since some month, Edge automatically randomly resets and logs me out of every site. This always happens when the PC starts up, I launch the browser and Edge has just reset itself and shows me the following screen It keeps my account synchronised, my passwords and my favourites, but I have to log in again on all the sites. Do you know what the problem is? Regards, Yves
Edge Workspaces sync BUGS
Hello First of all, I think that Workspaces in Edge is a very useful feature! Edge also has vertical tabs, which makes it the best tool for researchers using hundreds of tabs. I think other browsers can learn from this. With Workspaces, I can move windows I don’t currently use aside and open them again when needed without loading to RAM. Other browsers lack this feature, so I moved to Edge from Chrome. Edge is now my main tool for ongoing online research. However, after some months of use, I see that there are bugs that make me frustrated. With Workspaces, Edge is slow, it freezes, fails to synchronize, and reverts changes. 1. It does not update tabs and moves new tabs to the end. Let’s say that I have opened tabs: New Tab, facebook.com, A, B, C, D, E Later, I open links in new tabs from New Tab, Facebook, and A and leave them open. The tabs are: New Tab, msn.com/F, facebook.com, G, A, A2, B, C, D, E After some time, Workspaces synchronize, there is a short or longer Edge freeze. Then I see tabs are reorganized and F, G, H moved and changed addresses. The tabs are now: New Tab, facebook.com, A, B, C, D, E, New Tab, l.facebook.com/l.php?u=G, A2 It looks like Workspaces never update opened tabs when there was redirection through New Tab or l.facebook.com/l.php?u= or any other redirection on other websites. It only stores the first address it sees. When I refresh these tabs to see the description and go to the proper addresses, it still reverts it back! After I organize the order properly, it sometimes stays or is reverted back! This is frustrating when you need order and proper descriptions! 2. It is terribly slow, especially after opening another Workspace. I also encountered long freezes of Edge when opening another Workspace window or at random, probably when it synchronizes (a red dot appears next to the workspace name). Sometimes I have to wait 5 minutes, sometimes 15 minutes, sometimes I’m losing patience! I have plenty of PC power (12-core Ryzen 3900X, 32GB RAM, Samsung SSD 970 EVO Plus 1TB) and when I check Process Hacker, I see that Edge isn’t using 100% of CPU, but still is frozen. I noticed that when it’s frozen, there are around 200 disk writes, fast changing, 9MB/s total: C:\Users\me\AppData\Local\Microsoft\Edge\User Data\Default\Sync Data\LevelDB\256443.ldb ... ( edge_workspace_disk.xls ) When LevelDB writes stop, Edge is unfrozen. I’ve given msedge.exe processes high priority, but it doesn’t solve anything. I noticed this on previous versions starting from 122. I use Stable and Beta (to have two separate profiles) on PC and laptop. I waited hoping it will be solved, but nothing changed. It's possible that developers only tested Workspaces with a limited number of tabs and not with power users like myself, who manage 10 workspaces with 200-600 tabs in each. The consistent unreliability suggests there may be unresolved bugs present in each version. I examined the LOG.old file in the Sync Data>LevelDB folders of each browser and noticed that when a freeze occurs, there is a specific behavior logged: 2024/06/12-13:14:19.485 1a570 Generated table #365187@0: 40283 keys, 2109396 bytes 2024/06/12-13:14:19.485 1a570 Compacted 8@0 + 1@1 files => 2109396 bytes 2024/06/12-13:14:19.488 1a570 compacted to: files[ 4 6 7 0 0 0 0 ] 2024/06/12-13:14:19.489 1a570 Delete type=2 #365171 2024/06/12-13:14:19.489 1a570 Delete type=2 #365172 2024/06/12-13:14:19.489 1a570 Delete type=2 #365174 2024/06/12-13:14:19.489 1a570 Delete type=2 #365176 2024/06/12-13:14:19.489 1a570 Delete type=2 #365178 2024/06/12-13:14:19.489 1a570 Delete type=2 #365180 2024/06/12-13:14:19.489 1a570 Delete type=2 #365182 2024/06/12-13:14:19.489 1a570 Delete type=2 #365184 2024/06/12-13:14:19.489 1a570 Delete type=2 #365186 2024/06/12-13:14:19.491 179a0 Level-0 table #365197: started 2024/06/12-13:14:19.492 1a0a0 Current memtable full; waiting... 2024/06/12-13:14:19.500 179a0 Level-0 table #365197: 467718 bytes OK 2024/06/12-13:14:19.503 179a0 Delete type=0 #365194 2024/06/12-13:14:19.504 1a570 Level-0 table #365199: started 2024/06/12-13:14:19.505 1a0a0 Current memtable full; waiting... 2024/06/12-13:14:19.511 1a570 Level-0 table #365199: 467718 bytes OK 2024/06/12-13:14:19.514 1a570 Delete type=0 #365196 2024/06/12-13:14:19.515 179a0 Level-0 table #365201: started 2024/06/12-13:14:19.516 1a0a0 Current memtable full; waiting... 2024/06/12-13:14:19.524 179a0 Level-0 table #365201: 467718 bytes OK 2024/06/12-13:14:19.530 179a0 Delete type=0 #365198 2024/06/12-13:14:19.530 1a570 Level-0 table #365203: started 2024/06/12-13:14:19.531 1a0a0 Current memtable full; waiting... 2024/06/12-13:14:19.539 1a570 Level-0 table #365203: 467718 bytes OK 2024/06/12-13:14:19.542 1a570 Delete type=0 #365200 2024/06/12-13:14:19.542 179a0 Compacting 8@0 + 1@1 files 2024/06/12-13:14:19.556 179a0 Level-0 table #365206: started 2024/06/12-13:14:19.564 179a0 Level-0 table #365206: 467718 bytes OK 2024/06/12-13:14:19.568 179a0 Delete type=0 #365202 2024/06/12-13:14:19.572 179a0 Level-0 table #365208: started 2024/06/12-13:14:19.581 179a0 Level-0 table #365208: 467718 bytes OK 2024/06/12-13:14:19.584 179a0 Delete type=0 #365205 2024/06/12-13:14:19.588 179a0 Level-0 table #365210: started 2024/06/12-13:14:19.596 179a0 Level-0 table #365210: 467718 bytes OK 2024/06/12-13:14:19.600 179a0 Delete type=0 #365207 2024/06/12-13:14:19.604 179a0 Level-0 table #365212: started 2024/06/12-13:14:19.611 179a0 Level-0 table #365212: 467718 bytes OK 2024/06/12-13:14:19.615 179a0 Delete type=0 #365209 2024/06/12-13:14:19.620 1a0a0 Too many L0 files; waiting... 3. Workspaces sometimes stop syncing randomly and without notification. Occasionally, I notice a mismatch in the workspace between the PC and the laptop I use. If I close the workspace without checking, I will loose the tabs opened since the last sync! There's no notification, I must check if everything is synced or manually compare the opened tabs in the same workspace and then open them manually. After arranging them in the original order, I return to bug #1, which causes a mess when Edge moves tabs around. 4. Issues with Accessing Workspaces. This issue has occurred to me several times and is common among many users: "Error: Unable to load workspaces." Edge Workspaces error V114 - Microsoft Community Hub I tried many workarounds, sometimes they worked, yet they are not ideal and a definitive solution remains elusive. Now please tell me that Workspaces aren't still in beta phase. Workspaces are generally excellent tool, but in their current state of development, they are just a joke not worth the frustration and risk of data loss.[SEMI-CRITICAL] Outlook rules aren't working when email encoding system is different
(First, note that I am a Korean, and my report may use a different term for the system because it's tedious to figure out the original term for what I am using. I believe you know the vibe I am talking about.) I figured using different character encoding system may result in failing outlook rules working. Basically, it appears Outlook is using UTF-8 based, but sometimes emails from other organisations use different. Let me show 2 receiver cases: To: =?utf-8?B?7ZmN6ri464+Z?= <johndoe@secret.secret> To: =?ks_c_5601-1987?B?yKux5rW/?= <johndoe@secret.secret> This is what you can see from an email header, and left encoded characters are a name of a person, and obviously right bracket ones are their email. You can see it uses different encoding system. Both are encoded from "홍길동" (this is identical to a random guy name as much as how john doe is.) We can guess the name of this outlook user is obviously "홍길동" and their email address is johndoe@secret.secret When you choose a rule [When an email has my name], the rule system will only work to the first case, the UTF-8 encoded one. It appears the rule [When an email has my name] only checks if an email has "?utf-8?B?7ZmN6ri464+Z?", but doesn't check "?ks_c_5601-1987?B?yKux5rW/?". However, both cases should work because both are their name. The only solution for this is adjusting senders' email system to use UTF-8 only, but that is not possible. Thus it fails checking those conditions. I am pretty sure this is why people have been complaining outlook rules doesn't work for years. I want rules having more possible case checks... but I have no idea where I can suggest this.
