Scott S

My feedback

  1. 155 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Scott S commented  · 
  2. 9,063 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1131 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    Scott S supported this idea  · 
  3. 154 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    59 comments  ·  Public » Guest Access  ·  Flag idea as inappropriate…  ·  Admin →
    needs your feedback  ·  Warren responded

    If anyone is still hitting this issue, please respond in the comments section of this topic and let me know!

    Thanks!
    -Warren

    An error occurred while saving the comment
    Scott S commented  · 

    We are currently struggling with this issue as well because we have collaborators who work for other organizations in Azure AD that do not yet provision a Teams license to their staff. The most effective workaround I've found for a bulk invite is using PowerShell to do the guest account invitation. In that invitation, the key piece of information is the -InviteRedirectURL parameter. To retrieve the correct value you must right-click on the Team you are inviting your guests to and select "Get Link". That value is what you use to populate the -InviteRedirectUrl value.

    NOTE: While it is possible to programmatically add Guest (or User) accounts to a Group/Team using Add-AzureADGroupMember, there can be a long synchronization delay. I strongly recommend you directly add Guests through the "Manage Team" interface while logged into the Team as an Owner to avoid permissions problems from guests who redeem invitations prior to completion of back-end sync processes. Failure to follow this advice will result in Guests experiencing permission errors when they redeem their invitations and are redirected to the Teams URL.

    Example:
    #Login via the GUI after running the Connect-AzureAD command. You may need to join the Guest Inviter role if your organization has locked down guest invitations.
    Connect-AzureAD
    #The example assumes you have a CSV file including header fields called "Name" and "InvitedUserEmailAddress". The Name field is what becomes the display name for the Guest account in Azure AD. Change the path to where your CSV file is located.

    $invitations = import-csv C:\Temp\bulkguestinvite.csv

    $messageInfo = New-Object Microsoft.Open.MSGraph.Model.InvitedUserMessageInfo

    $messageInfo.customizedMessageBody = "You are receiving this email invitation at the request of blah blah blah support info etc."

    foreach ($email in $invitations)
    {New-AzureADMSInvitation `
    -InvitedUserEmailAddress $email.InvitedUserEmailAddress `
    -InvitedUserDisplayName $email.Name `
    -InviteRedirectUrl https://teams.microsoft.com/l/team/19:cd67dcf34917739afdac98f58be6e8d4%40thread.skype/conversations?tenantId=12345679-45644-44e6-bc28-236b1dadd334 `
    -InvitedUserMessageInfo $messageInfo `
    -SendInvitationMessage $true
    }

Feedback and Knowledge Base