Forum Discussion

Robert Bollinger's avatar
Robert Bollinger
Iron Contributor
Apr 20, 2021

Group Creation Behavior

Hey Team, 

 

Quick question for you. When I use the portal or (new-distributiongroup) to create a new group, I am finding that the group as "Allow external senders" enabled be default. I can confirm that the option for "Allow people outside my org to send to this group is not selected" at creation time.

 

This occurs when using the admin center or the cmdlet. I swear that it worked differently last week. Any ideas on the behavior? 

 

Thanks, 

Robert 

11 Replies

  • Just tested in my tenant, PowerShell still uses a default value of True (external senders disabled) unless you specifically set it to False.

    [09:39:05][Login script]# New-UnifiedGroup newwwwww -DisplayName newwwwww

    Name DisplayName GroupType PrimarySmtpAddress
    ---- ----------- --------- ------------------
    newwwwww_5c60ee20-e3a7-40b6-b50f-95be93ceb0e7 newwwwww Universal newwwwww@michev.info


    [09:39:40][Login script]# Get-UnifiedGroup | ft Name,Require*

    Name RequireSenderAuthenticationEnabled
    ---- ----------------------------------
    newwwwww_5c60ee20-e3a7-40b6-b50f-95be93ceb0e7 True
    • TonyRedmond's avatar
      TonyRedmond
      MVP

      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

      • Robert Bollinger's avatar
        Robert Bollinger
        Brass Contributor

        TonyRedmond VasilMichev 

         

        Thank you so much for confirming what I was seeing. I thought for sure I had finally lost it. I have a ticket open with Microsoft support. I will keep you guys up date on my progress with Support. 

         

        Thanks, 

        Robert

    • Robert Bollinger's avatar
      Robert Bollinger
      Iron Contributor
      Hey Vasil,

      Thanks for the test. But this is for a standard distro group. not for unified groups/Microsoft 365 groups. Can you check using the regular new-distributiongroup cmdlets?

      thanks
      • VasilMichev's avatar
        VasilMichev
        MVP
        Oh sorry, that's what happens when I reply before getting my daily caffeine dose 🙂

        Same behavior though:

        [19:25:25][Login script]# New-DistributionGroup sdfghj
        Name DisplayName GroupType PrimarySmtpAddress
        ---- ----------- --------- ------------------
        sdfghj sdfghj Universal sdfghj@michev.onmicrosoft.com


        [19:25:31][Login script]# Get-DistributionGroup sdfghj | ft Name,Req*

        Name RequireSenderAuthenticationEnabled
        ---- ----------------------------------
        sdfghj True

Resources