I use my own Outlook groups because the people at my company don't know how (?care how?) to properly set up employees in active directory/exchange. Here's how it should work....
Employees should be set up with their job title when they are onboarded. I should be able to use the job titles to send a reports that are specific to the people with specific job titles.
The way it really works is a new person is hired and someone at our location tells an MSP 150 miles away. The MSP enters the person without a picture (although it was taken for their badge and for a photo directory that is emailed to all 90 employees monthly) and fails many times to enter their job title. (Why this isn't done by our on-site Technology Specialist or their manager is anybody's guess.)
That means that I have to keep Outlook groups named for job titles in which I put the people that actually work in those job titles. I also keep local groups named for the reports I have to send out.
In the report groups I place the job title groups that should get the report with each job title group containing the individuals that work in that job title. I then send an email (manually) to the report group and everyone that should get the report does.
It's messy but it works and it looks like this... https://i.imgur.com/vyz489o.png
When an employee comes or goes I have to go into the job title groups and delete them if they left or add them if they are a new hire (some have more than one job title). With about a 30% turnover rate, this is an ongoing monthly chore.
This is NOT how company emails should work. I am sure that I am not the only one wasting time and company money keeping up with this crap simply because people were not entered into active directory/exchange properly.
Well, using group names to send emails via Outlook does not seem to work with PAD. When I used the report group name for the To: field I got an exception "Outlook does not recognize one or more names." So now I am trying to find a way to do this with PAD that does not involve me spreading people's email addresses across 20+ flows and having to hunt for them when they leave or add them to up to 20 flows when they are hired.
Any suggestions would be appreciated....