Dynamic Distribution Group with no Disabled Accounts
Hi I'm trying to build a few Dynamic Distribution Lists in Exchange Online and want to only include Active Users (i.e., users that are marked "Active" in Azure AD). I've tried using the UserAccountControl attribute (-eq 514 or -ne 514 - both are returning the same results, which is strange), but it still includes user accounts that are disabled. This is how my recipient filter looks like: RecipientType -eq 'UserMailbox' -and UserAccountControl -ne 514 What's the best way to achieve this in Exchange Online? Thanks Taranjeet Singh
Able to Sign in with a Distribution List – How is this Possible?
Hi everyone, I've come across an unusual issue and I'm hoping someone here might have an explanation for it. Normally, it's not possible to sign in with a Distribution List (DL) since it doesn't function as a regular user account. However, I noticed that with a specific email address, I am actually redirected to the login page instead of receiving an error message. To verify, I tested another distribution list within the same environment, and as expected, I was unable to sign in. This makes me wonder why this particular DL behaves differently. Does anyone know under what circumstances signing in with a distribution list might be possible?Office 365 Message Attribution
When a message arrives at Office 365, one of the first things we need to do is figure out which organization it belongs to. At first, this sounds simple – just look at the recipient, right? Well, it is more complicated than that, because of Hybrid and complex routing scenarios.Improving Security - Together
For many years, client apps have used Basic Authentication to connect to servers, services and endpoints. It is enabled by default on most servers and services and it’s super simple to set up. Simplicity isn’t at all bad in itself, but Basic Authentication makes it easier for attackers to capture user’s credentials and so we’re taking steps to improve data security in Exchange Online.Disabling Legacy Authentication in Exchange Server 2019
Legacy authentication methods are less secure, are vulnerable to interception and are susceptible to brute-force and password spray attacks. Use Authentication Policies in your Exchange Hybrid environment to disable legacy authentication requestsFolderId's not unique without factoring in case-sensitivity, PowerShell issues...
Hello, I like using Get-/Set-/Add-/Remove-MailboxFolderPermission cmdlets. One of my favorites. There are times when there are special characters in the folder names, so I use the FolderId instead. For example: Add-MailboxFolderPermission -Identity "User1:LgAAAAC5KVkA/5dLTL13II/kvsaqAWCosJLoiFIBRbYcQ3Ny3l9TAAAAfag/AAAB" -User "User2" -AccessRights FolderVisible,ReadItems This has been fantastic to save the day in those cases. My latest issue though is that there turn out to be many duplicate FolderId's if we disregard case-sensitivity. If I import a CSV which has UN-tampered FolderId's (case-preserved and confirmed) with Import-Csv, and then to this: Add-MailboxFolderPermission "User1:$($csv[0].FolderId)" -User "User2" -AccessRights FolderVisible, ReadItems ... the actual folder to be updated with this new permission entry (ACE) may be the one I intended, or it may be one of the other folders with a matching FolderId (ignoring case-sensitivity). What I've found is that it is possible but difficult to bounce back from that problem state. You need to report all permissions before and after and verify the differences are only the intended changes. Super tedious, effectively a dangerous exercise overall. I don't see any alternative solutions for this problem. MFCMAPI I think, as well as Outlook/OWA, are definite workarounds. Wondering if there is anything in-built with the *-MailboxFolderPermission / *-MailboxFolderStatistics cmdlets that can help PowerShell here?Support of DANE and DNSSEC in Office 365 Exchange Online
Microsoft is committed to providing world-class email security solutions and the support for the latest Internet standards in order to provide advanced email protection for our customers. Today we are announcing that Exchange Online will be adding support for two new Internet standards specific to SMTP traffic.
