Azure AD Group Sync
I love the fact that you have the Azure AD integration started and we would love to see you expand on that idea with Azure AD Group Sync capability. Thank you for all of your hard work and effort with Atera!
Hey all,
We're thrilled to announce we've added additional filtering to our Azure AD sync capability.
You will now be able to sync based on Groups and User Types (Members/Guests).
This will allow you to have a more focused and relevant importing process, saving you from importing irrelevant contacts from your instance.
You can read more about the new functionality here: https://support.atera.com/hc/en-us/articles/4409774509714-Azure-AD-Integration
Be sure to reach out to our support team for more inquiries.
We hope you enjoy this new release!
Yakov
-
Daryn Craine commented
Whilst it is great that groups show up I don't want to have to create a group or choose something that is 'as close to' but different for each customer. Surely 'Licensed Users' or even selecting license type should be an option here
-
Michael Barnes commented
Unfortunaltey this feature is useless without being able to filter which users get imported. Need to be able to select by group or by license type.
-
Servicedesk SCI commented
At this moment unusable because all objects are imported including service accounts, external accounts, etc
Please provide this ability asap -
Sam James commented
Urgh importing everything is not what we want! Let us set some high level filters first, groups, licensed, shared mailboxes etc.
I don't want guests. I want to be able to tick what I want to keep in sync and ignore the rest.
-
Chris Gavin commented
We would like to filter the AzureAD synchronisation to skip the following:
1. Unlicensed accounts
2. Groups
3. Guest accounts
We aren't using the synchronisation any more because of the time it takes to housekeep the contacts once in Atera -
Joseph Jones commented
@Product Team the article you linked to appears to be for tickets not Contacts.
There needs to be a way to do this, I just tried the sync and it brings down service accounts, old unlicensed users, etc. We either need to be able to specify only licensed users or have a way to hide the contacts.
-
Hannes Hörting commented
I have a tenant with several domains .. those domains are customers for my business and I need to split this.
It would be great, if we can filter by Email address. So Atera import just users, with the given domain from the customer domain in Atera.
All others should be not imported
-
Help Desk commented
Yep, definitely do not want to pull down every email address in a tenant as a contact because Teams, SharePoint sites, and shared email addresses like "hello@somecompany.com" get added as contacts.
-
Sandeep H - Cogenesis commented
We were supper excited when we heard this feature was coming. But after testing, we are not going to use it as everyone has flagged, nobody wants to import every possible user from Azure.
M365 is a collaboration platform and 1 tenant itself can have hundreds of external or guest users. There is no reason to pull all these contacts in the Atera. Even Microsoft AD Sync which sync on-prem users to M365 cloud, has filter and OU which is used to control users synced.
Hopefully product team understand the importance of this idea and will implement it soon. -
Eric Hester commented
This is very important. I have many clients with a lot of external contacts and it makes a real mess with it imports..
-
Anders Bjånesøy commented
Hi Atera! Your answer here about tags was meant for my other suggestion. Manual tags has nothing to do with this suggestion.
-
Lars Elgaard commented
It should be possible to select categories
- Licensed
- External
- Shared Mailbox
- Distribution Groups
Everything is too invasive -
Lars Elgaard commented
Sync of distribution groups would be great.
-
Chris Kellow commented
Yes limiting to specific security groups would be preferred
-
Michael Mathewson commented
Or at least let us review the contacts and select which ones we want to import.
-
Anders Bjånesøy commented
The new Azure AD contact sync is a great idea, but with one major flaw - External contacts in Azure AD should not be synced to Atera. Licensed users should be the only contacts synced down, as these are the only contacts worth creating in Atera. Please implement options to limit what's synced down.