0 votes

Hi, something has happened to our shared mailbox creation, on prem and syncing with o365 (we're a hybrid environment) the process works. With no issues.

When a new shared mailbox is created an access group is also created, the script works. It syncs to o365 and both the mailbox and group are created.

However we cannot add that group to the delegation for the mailbox as the error states the group is not in o365, but it quite clearly is.

Can anyone suggest how we investigate this? I'm assuming at the moment it's an Adaxes issue with accessing the o365 information.

by (490 points)
edited by
0

Hello,

Could you, please, specify what version of Adaxes you are currently using? For information on how to check it, have a look at the following help article: https://www.adaxes.com/help/CheckServiceVersion.

0

Hi,

2021.1

version 3.14.19312.0

Ta

1 Answer

0 votes
by (288k points)

Hello,

Thank you for specifying. It looks like the issue occurs due to the naming convention changes introduced by Microsoft. To remedy the issue, please, upgrade Adaxes to the latest build of version 2021.1 (3.14.20916.0). You can download it from here.

Upgrade Instructions

0

Hi,

We've updated to the latest version and after a few minutes it all seemed to work.

However when adding delegates to the mailboxes they do not show in Adaxes, but are clearly visible in O365. This seems to only be an issue with mail enabled security groups, when adding users it works as expected.

Version is now 3.15.20916.0 with no updates available

image.png

0

Hello,

Do we understand correctly that the delegates are cloud-only? Are you able to see them in Adaxes Administration console?

0

No, we run a hybrid environment.

All created onprem and synced to o365. The issue presents as an Adaxes display issue as the groups are added and visible in o365 as working.

But Adaxes just doesn't show them in the full access window.

0

Hello,

Thank you for the provided details. Unfortunately, this is an issue in Adaxes. We will fix it in one of the future releases. Sorry for the inconvenience.

Related questions

0 votes
1 answer

Maybe there is a better way to accomplish this, so I'm open to suggestion. We are in a hybrid setup between onprem and M365. When we create a new user, they are ... command in the previous step, right? If needed, I can provide the full script. Thanks!

asked Nov 2, 2023 by AndrewMeyer (20 points)
0 votes
1 answer

I've got the following script as part of a larger piece where param-members is an AD Object picker list seperated by a ' ; ' currently: New-DistributionGroup -Name ... or convert that to username but I'm struggling to achieve that with multiple Users selected

asked Jan 27, 2020 by richarddewis (260 points)
0 votes
1 answer

Rule-based membership fails for security enabled distribution group with error "The term 'Add-DistributionGroupMember' is not recognized as the name of a cmdlet, function, ... Exchange Online before running this PowerShell command. Here is rule based set up.

asked Mar 7, 2023 by KIT (960 points)
0 votes
1 answer

We are attempting to use the member property in a powershell script for all groups. We get this error message on certain groups that are used as "primary". If we set another ... just shows the single member in the group in which the group is not the primary.

asked Feb 19, 2020 by mark.it.admin (2.3k points)
0 votes
1 answer

I need to create a report of all enabled users in selected group or multiple groups. I am aware of the report named "Members of selected groups", but I don't know how to filter only enabled users. Is there a way to achieve this?

asked May 28 by gsoc.ssm (90 points)
3,536 questions
3,226 answers
8,218 comments
547,720 users