User Profile
AnnTaeYoun
MVP
Joined 9 years ago
Since 2017 Microsoft MVP | M365 Exchange
User Widgets
Recent Discussions
Re: Creation of customrole that allows only creation of Mailenabled Security groups.
Thanks for answer HansYolo This is because only distribution groups are visible in ECP. New-DistributionGroup is designed to create distribution groups by default. Security groups are created based on New-DistributionGroup parameters. The order is as follows: New-DistributionGroup (Base) New-DistributionGroup -Type Security (Security Group) Therefore, it is impossible to restrict or expose only security groups through RBAC in the GUI.73Views1like0CommentsRe: Creation of customrole that allows only creation of Mailenabled Security groups.
HansYolo In Exchange, mail-enabled security groups and regular distribution groups are created through the same cmdlet (New-DistributionGroup), so limiting the creation to only security groups is not supported.80Views0likes2CommentsRe: Exchange Server 2019 SMTP Error: "Does not support secure connection" on Port 587 with SSL
PrabakaranNagarajan On Exchange Server 2019, SMTP port 587 does not support Implicit SSL (-usessl). Configure authenticated SMTP settings for POP3 and IMAP4 clients in Exchange Server67Views0likes0CommentsRe: Local domain mailbox migration error
StefanoC66 The domain.local format is not supported in the online environment. Only officially purchased domains are supported. You must add a public domain(UPN suffix) in the Active Directory Domains and Trusts console and then change all user accounts to the public domain(UPN suffix).98Views3likes0CommentsRe: Pointing MX and Autodiscover to 365
Curious_Kevin16 If you have an Exchange Server on-premises in a hybrid configuration, you can use Basic auth to authenticate with the Exchange Server on-premises or configure the Exchange Server on-premises with a Receive connector that Allow anonymous relay on Exchange servers. Exchange Online to retire Basic auth for Client Submission (SMTP AUTH)66Views0likes0CommentsRe: Implementing DKIM and BIMI with Exchange 2016
Hi pazzoide76 My first answer is: Actually, I will recommend change DKIM provider that support of it. My second answer is: That right! Your smarthost (mail delivery provider) must support BIMI implementation, and that provider must be responsible for DKIM signing.276Views0likes1CommentRe: HCW fails to detect an Exchange Server
Please run Windows PowerShell next command! $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://MYNEWEXCHANGESERVER01/PowerShell/ -Authentication Kerberos -Credential (Get-Credential) Import-PSSession $session256Views0likes4Comments
Recent Blog Articles
No content to show