In order to wire the functionality together there are the usual number of configuration steps to be completed.

ps1 doesn’t need to have any logic/script inside it. Even though we’re not doing password management on this MA, the PS MA requires a file for this field. Three items I had to work out that I’ll save you the pain of are Configuration tasks like adding additional attributes the User Object Class in the MIM Portal, updating MPR’s, flow rules, Workflows, Sets etc are assumed knowledge and if not is easily Bing’able for you to work it out. Søren’s documentation is pretty good but does assume you have a working knowledge of FIM/MIM and this blog post is no different. Getting Started with the Granfeldt PowerShell Management Agentįirst up, you can get it from here.

My Lync / Skype for Business PS MA is used in conjunction with an Active Directory MA and Declarative Rules in the MIM Portal. change mobility, federation, voice policies for users based on managed attributes, and de-provisioning). Understanding how this is done you can then easily then extend the functionality for lifecycle management (e.g. I’ll show you how to do the minimum of enabling a user. In this blog post I’ll document how you can enable an Active Directory User for Lync / Skype for Business utilising Søren Granfeldt’s extremely versatile PowerShell Management Agent. Whilst this functionally works the ability for end customers to maintain the implementation for changes is limited. calling PowerShell from within a Management Agent Extension to enable/disable/manage policies). Over the years I’ve accomplished lifecycle management for users in Lync via FIM using methods that aren’t strictly best practice / supported (e.g. However, a MA for Lync / Skype for Business isn’t one of them. Forefront / Microsoft Identity Manager contains numerous Management Agents (MA’s) out of the box.

Skype for business 2016 download