Office 365 Integration
B
Bastien M.
Would be great to Filter for Company or Department aswell. In our Setup we want to limit the Users from one Tenant to one Company so that our providers can´t see all Users in the Tenant.
m
mohammad zahir
Seeing all the shared mailboxes and external users really clutters up our asset list. Would be great to be able to filter.
B
Ben K.
Upvote for this one. The integration is so useful but fills Hudu with so much clutter.
Just listened users would be simplest.
Or the ability to put shared/external users into a different asset (so not under people like the actual users).
D
Doug Hall
My PSA has a CIPP / M365 integration. Works a treat. There must be a way! :)
R
Robbie H.
This is definitely needed. After reading this, I'm hesitant to even use the M365 integration. It would be very cluttered without this feature, and the other ideas mentioned by commenters.
K
Kai H.
I have just synced a client with ~80 staff, and the Office 365 integration has pulled in no less than 383 records into Hudu, 300 of which are external users that I really don't care about and do not need to have recorded in Hudu.
Some kind of filtering is really needed here - an option to not pull in external users and not pull in Shared Mailboxes would be amazing.
K
Katerina
Turning off external users would be great. Other low hanging fruit would be to pullover these possibly to different asset templates or at least the choice to filter them out.
- Licensed Users/Users with UserMailboxes
- Shared Mailboxes (These mailboxes are identifiable in the graph API)
- Office 365 Groups
Gary Herbstman
There are several fields like Department missing from the sync.
F
Francesco B.
To build on this. Having options like do not sync users if attribute equals null. Also being able to map Azure AD attributes to asset fields. I find certain fields like departments are not appearing.
S
Sage C.
please please!! easy solution is to turn off external user sync
Load More
→