New Azure Group Based Licensing (V2) available as public preview

Just saw it in my demo tenant today that the new Azure Group Based Licensing (V2) is now available within the new Azure portal http://portal.azure.com under the Active Directory Node.

Until today, since all of you know, you could only assign EMS licenses by groups created in Azure or synchronized from an On-Premises directory. In addition, you could only assign the whole license/suite in one piece without the ability to disable sub plans, like RMS for example.

With the new group based licensing, you now can also assign other services license like Office 365 for example and are also be able to disable specific sub plans.

Here is how it looks like:

Navigate to the new portal (the artist formerly known as “the island”): http://portal.azure.com

Go to the Azure Active Directory Management (Preview):

01

You will see an overview of all your licenses and current assigned users and groups via the “All products” option:

02

03

Let us assign the Office 365 license by a group and disable some of the features:

Click “Licensed Group” and then “+ Assign”

04

Select a group created in Azure or synchronized from your On-Premises directory.

Click “assignment option (optional)”

05

Done, license assignment changes will now be scheduled and you can check the state of pending or active (should be active within one minute.)

06

You can have multiple groups with different sub plans disabled to reflect the licenses needed for different user type (Power Users, Limited Users or Guests)

There is also an audit log for all license assignment but with by early tests there is nothing logged, I assume because the necessary categories are missing until rollout of preview is complete.

 

Re-Awarded a 3rd time as an MVP

Just recieved my mail that I got the MVP award a 3rd time.

Still honored and proud to be part of the great community.

Lithnet FIM/MIM Synchronization Service PowerShell Module released

Ryan Newington (Developer of FIM/MIM Lithnet PS Module, new FIM/MIM Service Client and RestAPI) already anounced new PowerShell Cmdlets for the FIM/MIM Synchronization Service on the last MIM Team User Group Meeting.

You can now download that module on github.

See documentation on the modules and also the disclaimer.

Download the FIM/MIM Sync PowerShell Module.

Great job again Ryan.

Here is a list of modules included:

Read more of this post

Create PAM (Privileged Access Management) Mobile Apps with PowerApps

Maybe you already read my last blog post about using PowerApps for Microsoft Identity Manager where you find a definitions file for the Lithnet RestAPI for MIM to create a custom API for PowerApps. If not, please do so for some basic information’s.

I also will present the MIM and PAM PowerApps solution with some detailed information on the next MIM Team User Group meeting on June 15.

This time I give to all of you the swagger JSON definition file for the Privileged Access Management (PAM) RestAPI around with a demo PowerApp.

The swagger JSON and YAML files contains all the API calls that PAM provides, so you can do the following:

  • Get a list of all PAM roles you are a candidate for
  • Get the PAM role request history
  • Request a PAM role and also Cancel your request before TTL exceeds
  • Get a list of all PAM role requests you should approve
  • Approve of Reject a PAM role request

Since PowerApps is still a preview feature you might have some issues like I have, but I was able to test all scenarios mentioned above.
Read more of this post

MIMTeam User Group: MIM Handbook and upcomming MIM features

At the last MIM Team Usergroup meeting last week, David Steadman and Jeff Ingalls talked about their journey of writing the upcomming new MIM 2016 Handbook which is expected to be released in July.

Beside some very interesting facts on their experience and some funny things, there where one slide from David talking abount upcomming MIM 2016 CTP (preview) feature which fill then be comming to MIM GA some time in future.

Here is a screenshot of that slide:

MIMUpcommingCTPs

One of the most interesting facts I think is the support of Exchange Online for approvals, so you do not need to have your FIMService mailbox be onPremises, while you are maybe having already all other mailboxes migrated to O365.

Also all the feedback seems to be recognized by Microsoft so we can see their will be a PAM Single forest deployment scenario.

A lot of you I guess will also like the Cross Browser Support for MIM components lile SSPR and Portal.

So stay tuned for that and have a look to Microsoft Connect (Identity and AccessManagement Site) where those new CTPs will arrive.

 

Creating Mobile Apps for MIM with PowerApps and Lithnet RestAPI

I recently take a look into the Preview of Microsoft PowerApps and also Microsoft Flow. There are some really cool examples and templates for PowerApps and I also like that it is possible to create custom API connection for nearly every RestAPI.

When thinking on MIM we have that great Lithnet RestAPI from Ryan Newington and so a new project was born in my spare private time. Here are the results.

In order to create a connector in PowerApps for custom APIs we need a Swagger JSON definition file which describes the API (calls, parameters and so on). You can easily create such a definition file with the Swagger Editor in YAML. (Don’t worry, I’ve done this for you).

If you want to take a better look to the API definition file, go to http://editor.swagger.io and paste the YAML or JSON file of the Lithnet RestAPI into the editor. You will find both files at the end of the post.

These are the steps to setup the environment and create a simple PowerApp:

Install Lithnet Rest API:

First we assume you have a running MIM 2016 or FIM 2012 R2 installation. In that solution install the Lithnet FIM/MIM RestAPI according to the documentation: http://lithnetrmws.codeplex.com

Read more of this post

Authorize MIM Portal user image upload with Microsoft Cognitive Services

I saw these great videos from //build keynote some weeks ago about the Microsoft Cognitive Services and I was really impressed. I know these APIs like face, emotion, speech are designed for other purposes but I was thinking to myself on who to benefit from them for identity management.

So I remembered some time ago when talking about MIM Portal as a user self-service portal for personal data some customers find it is sometimes not a good idea if users can upload their own photos. The arguments where that photos cannot be validated in that way that it really belongs to that person. So people could upload for example funny pictures and avatars or even more bad images.

Sure, you can handle this by organizational policies, but I was thinking of a technical solution. At this point when thinking about Microsoft Cognitive Services the Face API came to my mind.

If you check the Face API it has methods for face detection in images and also face identification or verifying. You can also create person groups and persons with multiple faces saved in Azure if you want.

But for my little demo I only need the face detect and verify methods.

So here is how this demo works:

If people upload new images to MIM Portal, I trigger an authorization workflow and get the current and new photo with an MIMWAL update resource activity and pass that data to a PowerShell script which then calls the Face API.

The PowerShell Script uploads both images to Azure to do a face detection within the image and then returns a faceId for each of the pictures. Images are saved 24 hours Azure.
Read more of this post

%d bloggers like this: