Azure AD Connect: New version 1.1.561.0 available

A new version of Azure AD Connect is available since yesterday.

This release expands the scope of automatic upgrade to a wider scope, so there is an action needed if you don’t want that:

The scope expansion of the Automatic Upgrade feature affects customers with Azure AD Connect build 1.1.105.0 and after. If you do not want your Azure AD Connect server to be automatically upgraded, you must run following cmdlet on your Azure AD Connect server: 

Set-ADSyncAutoUpgrade -AutoUpgradeState disabled.

 

You can download the new version from HERE.

Read more of this post

Azure AD Connect: New version 1.1.557.0 available

Yesterday a new smaller version update was made available for download. It contains one fix and two improvements/features:

New build number is: 1.1.557.0

See Azure AD Connect: Version release history and download the bits from here.

Fixed issue

  • Fixed an issue with the Initialize-ADSyncDomainJoinedComputerSync cmdlet that caused the verified domain configured on the existing service connection point object to be changed even if it is still a valid domain. This issue occurs when your Azure AD tenant has more than one verified domains that can be used for configuring the service connection point.

New features and improvements

  • Password writeback is now available for preview with Microsoft Azure Government cloud and Microsoft Cloud Germany. For more information about Azure AD Connect support for the different service instances, refer to article Azure AD Connect: Special considerations for instances.
  • The Initialize-ADSyncDomainJoinedComputerSync cmdlet now has a new optional parameter named AzureADDomain. This parameter lets you specify which verified domain to be used for configuring the service connection point.

AADConnect 1.1 SyncScheduler Issue: DateTime Error and Scheduler not working

I recently installed Azure AD Connect 1.1 (Build 1.1.105.0) in my demolab.
I installed on a fresh Windows Server 2012 R2 with latest hotfixes and done the following:

  • Install AADC in Custom Setting Mode
  • Done all settings (which are not relevant to that issue)
  • Disabled direct start of Scheduler to modify sync rules
  • Re-Run AADC Wizard and activated the now internal Scheduler

But when checking SyncCycle within the Sync Service Manager I cloud not see any syncs.

Read more of this post

New Release: Azure AD Connect 1.1 is GA

A new release of Azure AD Connect is now GA, its version number is 1.1 or build 1.1.105.0.

Check the download page here and also the release version history here.
There is also a post on Alex Directoy Blog with some more details on the new features.

This are the new features and fixed issues in that release, as you can see it brings some new main features:

Read more of this post

Assign Azure/O365 licenses based on AD group membership

Hello,

just a short post today.

I thgought it might be a good idea to share more scripts in future, so here is the first one to assign Azure/O365 licenses based on AD group membership.
EMS/AADP and RMS licenses can also be assigned directly in Azure using group memberships but you still have to handle O365 licenses by your own with scripts.

So at some customers I have the reqirement to also manage O365 licenses after synchronizing objects with AADConnect, so I decided to manage all licenses with script.

This script still need some improvement in security (PW stored in file) but you can modify that like you want.
Also I do not cover License Option of O365 Licenses, instead the complete O365 features will be assigned.

Read more of this post

AADConnect: Updated build (1.0.8667) available

If you look at the current download page of Azure AD Connect (AADC) you will see there is a new build (Version 1.0.8667) available since 8/20/2015.

Azure AD Connect Download Page

You can get a list of improvements and fixes here:

Azure AD Connect: Version Release History

 

Using AADConnect to merge users originating in AzureAD

I shortly came into a situation with a customer who’s got to have OnPremise IT infrastructure for the first time. As a start-up they began with BYOD and some SaaS applications incl. a Hosted Exchange.

Since they are and will be heavily growing over the next few years they decided to plan and implement an IT infrastructure OnPremise with only a few components for security and client deployment including an Active Directory and combine that with Office365 and AzureAD for Mail and SaaS Application Management.

The migration from Hosted Exchange to O365 is already done, which leads into user account in Azure AD for all 250 users. I’ve implemented the Active Directory for them and now want to synchronize OnPrem AD Users with AzureAD.

But since all account are in Azure AD, I have to do an initial import of those accounts from Azure AD to OnPrem. And that’s where the issues began.

Read more of this post

%d bloggers like this: