This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 67%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Hello there,
We have been observing that some of of the MailUniversalSecurityGroup's name is is showing as GUID or string in Exchange online when created in AD and synced to O365. The name attribute is correctly updated in AD on MailUniversalSecurityGroup .
The MailUniversalSecurityGroup is synced from AD to O365. When run Get-Recipient, the output is like
Name RecipientType
---- -------------
61fcb56f-61d3-420a-a7cf-ca378aedb9f4 MailUniversalSecurityGroup
This causes an issue when we add this group to give Send As access to the members on a shared mailbox.
Kindly share some thought on how to fix it.
This is expected, see:
https://techcommunity.microsoft.com/t5/exchange-team-blog/change-in-naming-convention-of-user-s-name-parameter/ba-p/3284733
Why does it cause issues with SendAs?
Thanks for the article. Its clear why we the object id in the name in EXO not the actual name setup from AD.
No idea why this cause access to Send ad but the send As is not working with all the groups which show the EDOID instead of the actual name in EXO.
Interestingly, mailbox full access is working for the members of the group but not the send as.
How are you applying send as? I havent seen any issues
1- Creating a security group in AD with email address.
3- Add the members in the group in AD
2- Adding the group in the Send As delegation on the shared mailbox once its synced in EXO. There is no Exchange on-premise.
it doesnt let you add it? or it fails when sending an email?
It does allow to add from GUI and PS both but the delegation does not work. Plz check below. removed the actual GUID of the group in trustee.
Trustee AccessControlType AccessRights Inherited
-------- ----------------- ------------ ---------
GUID Allow {SendAs} False
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 62%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
We have the same issue on our Hybrid exchange set up.
When creating a new shared mailbox and assigned a security group, the Send As delegate shows as the GUID rather than the name of the sec group.
We have recently noticed as well, that when creating Distribution Groups as Rooms they also show as GUIDs in the name.
Whether there exists hybrid for your organization?
Send as permission is complex in hybrid: Mailbox permissions and capabilities NOT supported in hybrid environments
You need to set permission from both Exchange on-premises and Exchange online.
If there doesn't exist hybrid in your organization, could you tell us how you create this distribution group and which error when you set send as permission for shared mailbox?
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
There is no Exchange on-premises. The groups is created in AD with an email address and synced to Azure AD/Exchange online. The error is the generic one that you don't have access to send email.
Here is the test in my lab, check whether it is same as yours:
I check with the Exchange online created mailbox first to make sure Send As permission works for this shared mailbox.
Then check the User A, it can also send as the shared mailbox.
I check on the group, it shows as the same format as yours:
Have a check whether any step different with yours.
Hi KyleXu-MSFT,
This is exactly what we are following. The send As delegation works fine when the user is directly added to the mailbox however when we add a member to the group and the group is given the delegation, it does not work.
I want to confirm with you how the mailbox included in the distribution group is created?
If create the AD account in local AD and add it to this group. Then assign license on the Office 365 admin center to enable mailbox for this account.
Try to send emails to this group, check whether this mailbox could receive.
Is the shared mailbox hidden? It wont work if so.
Does it work from OWA?
What is the NDR if any when it fails?
Uploaded the NDR
HiddenFromAddressListsEnabled : False
Can this affect the send as access ?
AccountDisabled : True
If the shared mbx account is disabled that is by design. Does it work from OWA?
If not, can you remove and re-add the group send as perms from the shrd mbx
We tried removing and adding the permission multiple times from both GUI and PS. This is not working from OWA either.