Skip to main content

Joining Windows 10 to Azure AD Domain

As of October 2016 to join Windows 10 computers to Azure AD Domain service requires these steps:


  • When completed the IP address will be populated
  • Go back to the VNET configuration and add a DNS server with the IP (10.0.0.4 in this case)
  • Create the "AAD DC Administrator" administrators group (again in Directory -> Group). Members of this group are granted administrative privileges on machines that are domain-joined to the Azure AD Domain Services managed domain.
  • Add to the group your users who are supposed to have the administrative access
  • on a Windows 10 computer go to Settings -> Accounts (this is true for Windows 10 version  1607)
  • then select 'Access work or school' and click on Connect
  • On the next screen click on "Join this device to Azure Active Directory"

  • Enter your email address (from Azure AD user) and password

  • Click 'Sign In" 

  • and then 'Join"
  • and you're done!

Now to connect to the VM running Windows 10 a couple of changes required.
  • Disable 'Network Level Authentication' on the Windows 10 computer (clear the checkbox below)
  • In the RDP file add these two lines

                             enablecredsspsupport:i:0

             authentication level:i:2


  • Now log into the Windows 10 VM with Azure credentials using this format
AzureAD\<your email address>


                                  




If you have Office 365 subscription when you can access it without being prompted for credentials (true SSO experience)





Comments

  1. Dagar Magar3 December 2020 at 19:20

    As I website owner I think the subject material here is real wonderful, appreciate windows 10 activator for your efforts.

    ReplyDelete

Post a Comment

Popular posts from this blog

Create 3-Node Windows 2012 Multi-subnet Cluster

Environment There are two Data centers connected via a WAN link. Two Windows 2012 Servers (called SQLDEV1 and SQLDEV2) are located in the Primary Data Center (on the IP subnet 192.168.79.0/24) and the third server is placed in the Secondary Data Center with the 192.168.69.0/24 subnet. We’ll be creating a three-node Windows cluster with no shared storage on the multi subnet network with a file share witness at the Primary Data Center. We’ll be using a file share witness to protect from the cluster failure in a situation when the network between the Data Centers is unavailable and one of the servers in the Primary Data Center is also down (or being rebooted). The final state will look like depicted above: -           Two Virtual IP’s will be assigned (192.168.76.218 and 192.168.69.134) to the cluster -           The servers at the Primary Data Center will have a vote (Vote=1) and the server at the Secondary Data Center will have no vote (Vote=0). The file share witness al
2 comments
Read more

Generate Calendar Table in Power BI with Fiscal Year Attributes

In Power BI go to Get Data --> Blank Query and paste into the Function windows the text below. This function takes as parameters: - StartYear (e.g., 2012) - EndYear (e.g., 2018) -FiscalYearStartMonth (e.g., 4) And it will generate a calendar table for dates from Jan-1-<StartYear> till Dec-31-<EndYear> and columns for Fiscal Year, Fiscal Month, Fiscal Quarter, Fiscal Year Day where the Fiscal year begins on FiscalYearStartMonth = (StartYear as number, EndYear as number, FiscalYearStartMonth as number)=> let     //Capture the date range from the parameters     StartDate = #date(StartYear, 1, 1),     EndDate = #date(EndYear, 12, 31), //Get the number of dates that will be required for the table     GetDateCount = Duration.Days(EndDate - StartDate)+1, //Take the count of dates and turn it into a list of dates     GetDateList = List.Dates(StartDate, GetDateCount,     #duration(1,0,0,0)), //Convert the list into a table     DateListToTable
2 comments
Read more