Test Lab Guide: Creating a Windows Azure AD and Windows ...



Test Lab Guide: Creating a Windows Azure AD and Windows Server AD Environment using DirSync with Password SyncMicrosoft CorporationPublished: January 2014Author: Bill MathersAcknowledgementsSpecial thanks to the following people for reviewing and providing invaluable feedback for this document: AbstractThis document will assist IT professionals, administrators, architects, and developers with in creating a test lab that uses Windows Azure Active Directory and Windows Server AD.CopyrightThe information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS plying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred.? 2014 Microsoft Corporation. All rights reserved.Microsoft, Active Directory, Windows Azure, Forefront, MSDN, Outlook, SharePoint, SQL Server, Windows, Windows?PowerShell, and Windows?Server are trademarks of the Microsoft group of companies.The names of actual companies and products mentioned herein may be the trademarks of their respective owners.Contents TOC \o "1-5" \h Test Lab Guide: Creating a Windows Azure AD and Windows Server AD Environment using DirSync with Password Sync PAGEREF _Toc377126790 \h 4In This Guide PAGEREF _Toc377126791 \h 4Test Lab Overview PAGEREF _Toc377126792 \h 4Test Lab Guide Specific Requirements PAGEREF _Toc377126793 \h 5Steps for Creating a Windows Azure AD and Windows Server AD Environment Test Lab PAGEREF _Toc377126794 \h 5Test Lab Guide Specific Information and Instructions PAGEREF _Toc377126795 \h 6Step 1: Set Up the Configuring the Windows Server 2012 Base Configuration Test Lab for Public Cloud Technologies PAGEREF _Toc377126796 \h 6Step 2: Sign-up for a Windows Azure 30-Day Trial PAGEREF _Toc377126797 \h 7Sign-up for a Windows Azure 30-Day Free Trial PAGEREF _Toc377126798 \h 7Step 3: Create a Windows Azure AD Tenant PAGEREF _Toc377126799 \h 13Create a Windows Azure AD Tenant PAGEREF _Toc377126800 \h 13Step 4: Prepare the Windows Azure AD Tenant for Synchronization PAGEREF _Toc377126801 \h 14Verify your domain PAGEREF _Toc377126802 \h 15Set domain as Primary PAGEREF _Toc377126803 \h 18Create a global administrator account in our Windows Azure AD tenant. PAGEREF _Toc377126804 \h 19Active Windows Azure AD Tenant for Synchronization PAGEREF _Toc377126805 \h 28Step 5: Create Organizational Units and Test Users in Windows Server AD PAGEREF _Toc377126806 \h 29Create Organizational Units PAGEREF _Toc377126807 \h 29Create Test Users PAGEREF _Toc377126808 \h 30Step 6: Download and Install DirSync PAGEREF _Toc377126809 \h 31Install .NET 3.5 on DC1 PAGEREF _Toc377126810 \h 31Download and Install the Windows Azure Active Directory Synchronization Tool PAGEREF _Toc377126811 \h 32Configure the Windows Azure Active Directory Sync Tool PAGEREF _Toc377126812 \h 35Step 7: Configure DirSync to specific Organizational Units PAGEREF _Toc377126813 \h 41Create a service account to run the Active Directory Connector PAGEREF _Toc377126814 \h 41Configure Dirsync to Specific Organizational Units PAGEREF _Toc377126815 \h 42Step 8: Run DirSync and Verify Results PAGEREF _Toc377126816 \h 44Verify the User has been synchronized PAGEREF _Toc377126817 \h 45Verify the password has been synchronized. PAGEREF _Toc377126818 \h 45Summary PAGEREF _Toc377126819 \h 48Test Lab Guide: Creating a Windows Azure AD and Windows Server AD Environment using DirSync with Password SyncWindows Azure AD and Windows Server ADIn This GuideThis guide contains instructions for setting up a test lab based on the Test Lab Guide: Creating a Windows Azure AD and Windows Server AD Environment.A full copy of this document is available for offline viewing here.Test Lab OverviewIn this test lab, we move from the original base configuration to using the base configuration that is enabled for cloud related technologies. This means that the machines are no longer isolated from the internet and are able to communicate with cloud services such as Windows Azure. No additional servers or machines are required beyond those that are required for the base configuration outlined in step 1. However this guide does deviate some from that configuration so see the Test Lab Guide Specific Information and Instructions below.The following is an architectural diagram of this test lab guide.Test Lab Guide Specific RequirementsThere are no additional hardware requirements, There is one additional software requirement, that is for the DirSync tool. There are also few specific things that this test lab will require. The table below provides a list of these requirements.The following table provides a summary of the required items for this test lab guide.RequirementCommnetWindows Azure 30-day TrialWindows Azure Free TrialA Microsoft AccountMicrosoft accountA Mobile Phone that can receive text messagesRequired for Windows Azure verification.A valid Credit CardRequired for Windows Azure Free Trial.Windows Azure Active Directory Sync tool – 64 bitWindows Azure Active Directory Sync tool – 64 bitWindows Server 2012 R2 installation filesThis is required to install .NET 3.5 which is required by the DirSync tool.Steps for Creating a Windows Azure AD and Windows Server AD Environment Test LabThere are eight steps to follow when setting up the Creating a Windows Azure AD and Windows Server AD Environment Test Lab Guide.?Step 1: Set Up the Configuring the Windows Server 2012 Base Configuration Test Lab for Public Cloud Technologies - The Base Configuration is the core of all Test Lab Guide scenarios. This test lab guide has been modified so that the base configuration can be used with cloud technologies.?Step 2: Sign-up for a Windows Azure 30-Day Trial – In this step we sign up for our Windows Azure trial.?Step 3: Create a Windows Azure AD Tenant – In this step we create our Windows Azure Active Directory tenant.?Step 4: Prepare the Windows Azure AD Tenant for Synchronization – In this step we configure our tenant so that it can synchronize with our on-premise Active Directory.?Step 5: Create Organizational Units and Test Users in Windows Server AD – In this step, we create the on-premise AD structure that we are going to synchronize with our Windows Azure AD tenant.?Step 6: Download and Install DirSync – In this step we download, install, and do an initial configure of the software that will be used to synchronize our directories.?Step 7: Configure DirSync to specific Organizational Units – In this step, we customize the Windows Azure Active Directory Synchronization Tool to only synchronize certain users from our on-premise AD.?Step 8: Run DirSync and Verify Results – In this step we run the tool and verify the results.Test Lab Guide Specific Information and InstructionsThe following section is a list of additional information on configuring the test lab. It also includes items that may be omitted from the test lab guides that this test lab builds upon. This is to allow for quicker deployment.The following is a list of general information and instructions?When setting up the base configuration the domain that is used when installing Active Directory was instead of corp.. The reason is, is that we wanted to use a custom domain in Windows Azure AD instead of the domain that is initially created when you create an AD tenant. This will simulate what a corporation might need to do if they want to keep the domain they already own. For instance, if I have a company named Fabrikam and our domain name is and our email address is @, we would probably want to use as our AD tenant domain as oppose to @fabrikam..The corp. domain is owned by Microsoft but not by me the writer, so to facilitate writing of this guide, I purchased the domain . Otherwise I would have had to track down who owns corp., where it is registered, and if it could even be used as I verified these steps because it may already be associated with an Azure AD tenant. Also, this prevents us from having to do the additional step of adding and additional UPN to our users in our on-premise environment.?This entire test lab can be setup with just DC1. No other machines from the base configuration are required, however they will be used for test labs that build on this one.Step 1: Set Up the Configuring the Windows Server 2012 Base Configuration Test Lab for Public Cloud TechnologiesSet up the Base Configuration test lab based on the instructions in Configuring the Windows Server 2012 Base Configuration Test Lab for Public Cloud Technologies.Step 2: Sign-up for a Windows Azure 30-Day TrialThe first thing we are going to do after setting up the Base Configuration for Cloud Technologies is to sign-up for a Windows Azure 30 Free Trial. You will need a Microsoft account, a mobile phone and a credit card to complete this step. This is kind of a pain, but unfortunately there is no other way around it. Fortunately there are account limits automatically in place to prevent your trial account from being charged. I can attest that I have done this several times (no even as an employee I don’t get unlimited Azure accounts), and I have never been accidentally charged. Signing up for Azure involves the following:?Sign-up for a Windows Azure 30-Day Free TrialSign-up for a Windows Azure 30-Day Free TrialUse the following procedure to sign-up for a Windows Azure free trial.To Sign-up for a Windows Azure 30-Day Free Trial1.Open Internet Explorer and navigate to .2.At the very top, click Free Trial. This will take you to the free trial page.3.On the free trial page, click Try it now. You will be asked to sign-in with your Microsoft account.4.After signing in, you will see the sign-up page. Verify the information in section 1, About you5.In section 2, enter your mobile phone number and click Send Text Message. Wait for the message to be sent to your phone.6.Enter the code that was sent to your phone and click Verify Code.7.Next enter your valid credit card information in section 3.8.Read the Windows Azure Agreement, Offer Details, and Privacy Statement then place two checks in the boxes and click Sign Up. This will take you to a screen that provides a summary of your subscription. At the top click Portal.9.This will take you to the Windows Azure Portal. You will be presented with the Windows Azure Tour wizard. If you haven’t taken the tour before I recommend doing so, otherwise you can close it.Step 3: Create a Windows Azure AD TenantNow that we have a Windows Azure subscription, we are going to create a Windows Azure Active Directory Tenant. This will be the cloud directory that we synchronize our on-premise AD directory with. This step involves the following:?Create a Windows Azure AD TenantCreate a Windows Azure AD TenantUse the following procedure to sign-up for a Windows Azure free trial.To Create a Windows Azure AD Tenant1.If you are not already signed in to the Windows Azure Portal, do this first.2.In the Windows Azure Portal, on the left, scroll down and click Active Directory. This will take you to the active directory screen in the Windows Azure portal.3.4.At the bottom, click Add. This will bring up the Add directory screen.5.Ensure Create new directory is selected and then enter the Name, Domain Name, and select a country or region from the drop-down. For purposes of this test lab guide, the name of the directory used was Contoso, but the Domain Name was bmcontoso, which corresponds to the domain name I have registered with a domain registrar. Click the check mark.6.The directory should now be created.Step 4: Prepare the Windows Azure AD Tenant for SynchronizationNow that we have a tenant, we must prepare it in order to synchronize it with our on-premise Active Directory. This step involves the following:?Verify your domain?Set domain as Primary?Create a global administrator account in our Windows Azure AD tenant.?Active Windows Azure AD Tenant for SynchronizationVerify your domainWhen you create the Windows Azure AD tenant, a basic domain with is created. But if you want to use a domain that is associated with your Windows Server AD, you can add and use a custom domain. Because we have a custom domain and would like to use this in association with our Windows Azure AD tenant, the first thing we need to do is verify the domain. Use the following steps to verify your domain.To verify your domain1.If you are not already signed in to the Windows Azure Portal, do this first.2.In the Windows Azure Portal, on the left, scroll down and click Active Directory. This will take you to the active directory screen in the Windows Azure portal.3.On the right, click on our newly created tenant. This will bring up Contoso directory screen.4.At the top, click on Domains, this will bring up the domains screen.5.At the bottom, click Add. This will bring up the add domain wizard.6.Enter your domain name in the box and click add.Important Do not place a check in the single sign-on box. This TLG does not demonstrate single sign-on. This will be demonstrated in future TLGs.7.You should see a notice that the domain was successfully added. Click the right arrow. This will bring up a Verify the domain screen.8.Windows Azure AD uses a DNS record that you create at your domain name registrar to confirm that you own the domain. At this point, you need to add the value in the Destination or Points to Address to a DNS record at your domain name registrar. For example, if you use you would sign in there and add the DNS record to your domain. Use the steps outlined here to assist with this.9.This may take a little while but once it is verified you will see the status change to verified.Set domain as PrimaryNow that the domain has been verified, we need to set the domain as our primary domain. Use the following procedure to set our verified domain to the primary domain.To set domain as primary1.If you are not already signed in to the Windows Azure Portal, do this first.2.In the Windows Azure Portal, on the left, scroll down and click Active Directory. This will take you to the active directory screen in the Windows Azure portal.3.On the right, click on our newly created tenant. This will bring up Contoso directory screen.4.At the top, click on Domains, this will bring up the domains screen.5.At the bottom of the screen, click Change Primary. This will bring up a change primary screen.6.Make sure that your domain is selected under the New Primary Domain heading and click the check mark.7.Your domain should now be set as the primary domain.Create a global administrator account in our Windows Azure AD tenant.In order to synchronize with Windows Azure AD, the directory synchronization utility (DirSync) needs to know of an account with administrative privileges so that it can create, delete, and update users and groups. Use the following procedure to create a global administrator account in our new tenant.To Create a Windows Azure AD global administrator1.If you are not already signed in to the Windows Azure Portal, do this first.2.In the Windows Azure Portal, on the left, scroll down and click Active Directory. This will take you to the active directory screen in the Windows Azure portal.3.On the right, click on our newly created tenant. This will bring up Contoso directory screen.4.At the top, click on Users, this will bring up the users screen. There should be only one account in here, the Microsoft account you used to sign-up for your Azure subscription.5.At the bottom, click Add User. This will bring up the add user wizard.6.Enter a user name for the user and click the arrow.7.Enter the first name, last name, display name, and select global administrator from the drop-down. Click the right arrow.8.Click the create button to create the user and get a temporary password.9.This will create the account and assign it a temporary password. Use the icon next to the temporary password to copy it to the clipboard. 10.This will bring up a pop-up asking whether or not to allow Internet Explorer access to the clipboard. Click allow access. Click the check mark.11.Now, in the portal, at the top, click the user account you are logged in as and select sign out from the drop-down.12.This will sign you out and you will see a screen that says you have been signed out. Click Sign In Using Your Organizational Account.13.Now sign-in to the portal with the newly created administrator account using the password we copied to the clipboard. The Organizational Account consists of your user name, the @ symbol, and the primary domain name for your tenant. Example: Admin@.14.Once signed in, you will be prompted to change your password. Go ahead and set the password to one of your choosing. This password will be required again when we setup the DirSync tool. Click submit.15.Windows Azure will now attempt to log you on. You will see a screen that says you do not have a Windows Azure subscription associated with this account. This is correct as our subscription is associated with our Microsoft account. At this point, just close Internet Explorer because the password has been changed.Active Windows Azure AD Tenant for SynchronizationFinally, we need to flip the switch that allows us to synchronize with this directory in Windows Azure. Use the following procedure to activate this Windows Azure AD tenant.To Active Windows Azure AD Tenant for Synchronization1.If you are not already signed in to the Windows Azure Portal, do this first.2.In the Windows Azure Portal, on the left, scroll down and click Active Directory. This will take you to the active directory screen in the Windows Azure portal.3.On the right, click on our new tenant. This will bring up Contoso directory screen.4.At the top, click on Directory Integration, this will bring up the directory integration screen.5.In the middle of the screen, next to Directory Sync, change Deactivated to Activated. At the bottom, click Save.Step 5: Create Organizational Units and Test Users in Windows Server ADNow that we have Windows Azure AD set up, we need to create the Organizational Unit structure in our on-premise AD environment and populate the OU’s with a couple of users. This step consists of the following.?Create Organizational Units?Create Test UsersCreate Organizational UnitsUse the following procedure to create the organizational units.To create the Organizational Units1.On DC1, open Active Directory Users and Computers2.Right-click on (or the name of your forest) and select New and then select Organizational Unit.3.In the name box, enter bmcontoso_users and click Ok.4.Right-click on bmconto_users and select select New and then select Organizational Unit.5.In the name box, enter Engineering and click Ok.6.Right-click on bmconto_users and select select New and then select Organizational Unit.7.In the name box, enter Sales and click Ok.8.The OU structure should now look like the screenshot below.Create Test UsersNow we will create one user in each of the new OUs that we created. One in Engineering and one in Sales. Use the following procedure to create the Users.To create test users1.Right-click on Engineering and select select New and then select User.2.Enter the following and then click Next.?First Name: Britta?Last Name: Simon?Full Name Britta Simon?User logon name: bsimon3.Enter a password for the user, remove the check from User must change password at next logon and place a check in Password never expires.4.Click Finish.5.Right-click on Sales and select select New and then select User.6.Enter the following and then click Next.?First Name: Lola?Last Name: Jacobson?Full Name Lola Jacobson?User logon name: ljacobson7.Enter a password for the user, remove the check from User must change password at next logon and place a check in Password never expires.8.Click Finish.Step 6: Download and Install DirSyncNow that we have prepared Windows Azure AD and created our test OU structure and populated it with users, we can download and install the DirSync tool. However before doing this, we must install .NET 3.5 which is a requirement for using the tool. The following section consists of the following:?Install .NET 3.5 on DC1?Download and Install the Windows Azure Active Directory Synchronization Tool?Configure the Windows Azure Active Directory Sync ToolInstall .NET 3.5 on DC1The first thing we are going to do is install .NET 3.5 on DC1. Use the following procedure to install .NET 3.5.To install .NET 3.5 on DC11.On DC1, in Server Manager, click Add roles and features. This will start the Add Roles and Features Wizard.2.On the Before you begin screen, click Next.3.On the Select installation type screen, make sure Role-based or feature based-installation is selected and click Next.4.On the Server Selection screen, click Next.5.On the Server Roles screen, click Next.6.On the Features screen, place a check in .NET Framework 3.5 Features. Click Next.7.On the Confirmation screen, click Specify an alternate source path. This will bring up a pop-up asking for you to specify an alternative path. Enter the path to the Windows Server 2012 R2 binaries. For example, if I have the Windows Server 2012 R2 binaries on disk and my cd-rom drive is D: then the path would be D:\Sources\SxS\. This is the path on disk to where the .NET 3.5 binaries are. Then click OK.8.Click Install.9.Once the installation is complete, click Close.Download and Install the Windows Azure Active Directory Synchronization ToolNow we will download and install the Windows Azure Active Directory Synchronization Tool, also known as DirSync tool. Use the following procedure to download and install DirSync.1.You can download the DirSync tool from Windows Azure Active Directory Sync tool – 64 bit.2.Once the download is complete, navigate to the file that was downloaded and doubleclick on dirsync.exe. You may get a security warning asking if you want to run this file. Click Run.3.On the Welcome screen, click Next.4.On the License Terms screen, review the terms, click the I accept radio button, and then click Next.5.On the Select Folder Installation screen, accept the defaults and then click Next.6.It will now start installing the components. This may take awhile.7.Once that has completed, click Next.8.Remove the check from Start Configuration Wizard and click Finish.9.Now log off of DC1 and log back on. The reason for this is that the account you installed the DirSync tool with was added to newly created security groups and we want to refresh your security token.Warning This step is only required when installing the DirSync tool on a domain controller. If it is installed on a member server, you do not have to log off and then back on prior to running the configuration wizard.Configure the Windows Azure Active Directory Sync ToolNow, log back on to DC1 and we will begin with the intial configuration of the DirSync tool. This will be a simple configuration and the next step will walk us through the advanced configuration of scoping our OUs. Use the following procedure to run the DirSync Configuration Wizard.To configure the Windows Azure Active Directory Sync Tool1.On DC1, click the Windows Icon in the lower left corner, this will take you to the Start screen.2.On the Start Screen, use the down arrow at the bottom to show all of the Apps on DC13.Scroll over to Directory Sync Configuration under Windows Azure Active Directory and click on it, this will start the configuration wizard.4.On the Welcome screen, click Next.5.On the Windows Azure Active Directory Credentials screen, enter the username and password of the global administrator account we created earlier in this guide. Click Next.6.On the Active Directory Credentials screen, enter the username and password for Administrator. Click Next.7.On the Hybrid Deployment screen, place a check in Enable Hybrid Deployment and click Next.8.On the Password Synchronization screen, leave the defaults and click Next.9.This will begin the Configuration. Once the configuration is complete, click Next.10.On the Finished screen, take the check mark out of Synchronize your directories now and click Finish.Step 7: Configure DirSync to specific Organizational UnitsNow that we have installed and initially configured DirSync, we are going to do some advanced configuration so as to only synchronize certain OUs and not our entire on-premise Active Directory. This section consists of the following:?Create a service account to run the Active Directory Connector?Configure Dirsync to Specific Organizational UnitsCreate a service account to run the Active Directory ConnectorThe account used by the Active Directory Connecter is created by the DirSync tool during configuration. If we want to synchronize everything in our directory we can use this account, however because we want to scope this to only specific OUs, we need to create an account to run the Active Directory Connector. Some of you may ask why can’t we just change the password of the account that was created by DirSync. The reason is this can cause issues with the automatic synchronizations and this is an unsupported configuration. For purposes of this test lab, we will make the service account a member of domain admins. For information on restricting the connector with the least amount of privileges required, see the Forefront Identity Managerdocumentation. Use the procedure to create a service account.To create a service account1.In Active Directory Users and Computers, right-click on the Users OU and select New and then select User.2.Enter the following and then click Next.?First Name: AD Connector?Last Name: Account?Full Name AD Connector Account?User logon name: adconn3.Enter a password for the user, remove the check from User must change password at next logon and place a check in Password never expires.4.Click Finish.5.In the users OU, right-click on the new AD Connector Account and select properties.6.In the properties, at the top, click Member Of and click Add.7.In the Select Groups box, enter domain admins and click Check Names. This will resolve with an underline. Click Ok.8.Click Apply. Click Ok. Close Active Directory Users and Computers.Configure Dirsync to Specific Organizational UnitsUse the following procedure below to configure DirSync to only synchronize specific organizational units of your on-premise AD.To configure Dirsync to specific organizational units1.Navigate to C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell and double-click miisclient.exe.2.In the DirSync tool, double-click on the Active Directory Connector to bring up the Active Directory Connector properties again.3.Now, on the left, click Configure Directory Partitions. This will bring up the Configure Directory Partitions section.4.Click the Containers button. You will be prompted for the password for the MSOL_xxxxxxxxxxxx account. Remove this account and add the information for the new account we just created.5.Now the containers screen will come up. the easiest way to do this is to remove the check from the root, in this case, DC=bmcontoso,DC=com. This will remove all of the checks. Now place a check in just the bmcontoso_users container. This will check that container and all child containers. In our case, this includes the Engineering and Sales containers.6.Click Ok. Click Ok again. The Active Directory Connector properties should have closed and we have successfully set the scope. Now in the next section we will run synchs and verify our results.Step 8: Run DirSync and Verify ResultsNow it is time to verify the results are synchronized to Windows Azure AD. However this may take up to 3 hours. This is the automatic synchronization interval for the DirSync tool. Although the ability to run the connectors manually is available in the UI, this is not supported as this will interfere with the automatic schedule. This section consists of the following:?Verify the User has been synchronized?Verify the password has been synchronized.Verify the User has been synchronizedNow we will verify that the users have been synchronized. Use the following procedure to verify the user has been synchronized.To verify the User has been synchronized1.Open Internet Explorer and navigate to and log in with your Microsoft account.2.In the Windows Azure Portal, on the left, scroll down and click Active Directory. This will take you to the active directory screen in the Windows Azure portal.3.On the right, click on Contoso. This will bring up Contoso directory screen.4.At the top, click on Users, this will bring up the users screen. You should see our two new users.5.Verify the password has been synchronized.Now we will verify that the password has been synchronized. To do this we will log on to with Lola Jacobson’s account. This will show her the applications that she has access to and she will also be able to view attributes associated with her account. This site uses cloud authentication against your instance of Windows Azure AD.To verify the password has been synchronized.1.Sign out of Windows Azure and close any open browsers. Then re-open Internet Explorer and navigate to . 2.Log in as Lola Jacobson. You should see the applications screen similar to the one below.3.Now, at the top, click profile. You should see the attributes and have the ability to change your password.Warning The attributes actually will say N/A since we did not configure any of these.4.You can now close Internet Explorer.SummaryThis ends the Test Lab Guide: Creating a Windows Azure AD and Windows Server AD Environment. We have successfully synchronized our on-premise Active Directory with Windows Azure AD. This test lab guide will be used as the basis for additional test lab guides in the future that take advantage of using a Hybrid environment. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download