Group Creation Behavior

VasilMichev 

I ran this:

New-DistributionGroup -Name "Project Aska" -PrimarySmtpAddress Project.Aska@office365itpros.com -DisplayName "Project Aska Team" -Alias Project.Aska Creating a new Remote PowerShell session using Modern Authentication for implicit remoting of "New-DistributionGroup" command ... New! Microsoft 365 Groups are the next generation of distribution lists.
Groups give teams shared tools for collaborating using email, files, a calendar, and more.
You can start right away using the New-UnifiedGroup cmdlet.

Name DisplayName GroupType PrimarySmtpAddress
---- ----------- --------- ------------------
Project Aska Project Aska Team Universal Project.Aska@office365itpros.com

Get-DistributionGroup Project.Aska | ft req*

RequireSenderAuthenticationEnabled
----------------------------------
True

RequireSenderAuthenticationEnabled is True, so external users can't send to this list. I then checked with EAC and found that the incorrect option appears to be selected:

But when I look at PowerShell again, I find that the property is updated. Something screwy is happening here.

Get-DistributionGroup Project.Aska | ft req*

RequireSenderAuthenticationEnabled
----------------------------------
False