Share
Report
19Hello Dynamics people,
our team have been tasked with finding a more efficient way for our service desk to handle Dynamics team membership, as well as permissions and access to shared views/dashboards.
The obvious solution, that appears to work up to a point, is as follows:
- Create a security group in Local AD (We are tied to local AD at the moment)
- Locate the Object ID once this synchronises to Azure AD
- Create a Team in Dynamics as type AAD Security Group - link this via the Object ID obtained in the above step
- Assign the new Team relevant security roles
This works really well on the face of it - the user/s are added into the AD group, in time it synchronises through, and as long as they have a licence they are then able to access the environment, and any views/dashboards that are shared with the dynamics team.
The massive blocker we seem to have hit, is that Office Group, or Security Group teams do not get created with a default queue, AND you cannot create one.
These teams will all, without exception, require a queue.
Does anyone know differently?
Frustratingly it seems like even though the above solution will be a timesaver of sorts, there will effectively need to be two teams, one a normal team with a queue attached, and one a security group with views/dashboards/attached & security roles attached.
Is it possible you could add the security team as a member of the 2nd team - I think this is likely not a possibility sadly.
It's rather frustrating, as it is on the brink of being a really efficient, and perfect way of managing access, and pretty much every major aspect of dynamics for our users, but seems to be let down by the fact that the queue is not an option.
I'm assuming this must be a fairly frequent route that people go down, so would be keen to hear if I am hopefully very wrong, or if anyone has found a way around it, or to achieve similar functionality.
Thanks
Dan
All responses (
Answers (
