<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Elliott Fields Jr.</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/elliottf/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/elliottf/feed.xml</link>
    <description />
    <lastBuildDate>Wed, 17 Apr 2019 03:25:24 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Killer Home Lab Series - Update</title>
      <link>https://docs.microsoft.com/archive/blogs/elliottf/killer-home-lab-series-update</link>
      <pubDate>Sat, 05 Aug 2017 02:27:53 GMT</pubDate>
      <dc:creator><![CDATA[ELLIOTTF - Elliott Fields Jr]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/elliottf/?p=7045</guid>
      <description><![CDATA[In order to produce more timely and requested articles I have decided to move my blog to a free...]]></description>
      <content:encoded><![CDATA[In order to produce more timely and requested articles I have decided to move my blog to a free personal site that will allow membership based security in order to reduce SPAM.  Please provide and email in the comments to gain access.

Thanks,

Elliott]]></content:encoded>
    </item>
    <item>
      <title>Domain Joining Servers to Azure AD Domain Services (Office 365 Tenant)</title>
      <link>https://docs.microsoft.com/archive/blogs/elliottf/domain-joining-servers-to-azure-ad-domain-services-office-365-tenant</link>
      <pubDate>Tue, 28 Feb 2017 00:45:44 GMT</pubDate>
      <dc:creator><![CDATA[ELLIOTTF - Elliott Fields Jr]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/elliottf/?p=6285</guid>
      <description><![CDATA[Office 365 offers 2 well known options for logging onto your workstation using your Office 365...]]></description>
      <content:encoded><![CDATA[Office 365 offers 2 well known options for logging onto your workstation using your Office 365 credentials. These options are Workplace Join and Azure AD Join. Workplace join is mostly used for devices such as Windows Phone, IOS or Andriod devices while Azure AD Join is used more for Windows 10 Workstations. These options are great for workstations and devices, but what about your servers. Supposed you don’t want to manage domain controllers within your Azure Subscription but would like a common logon account across all of your Servers. Azure AD Domain Services allows you to Domain-Join Windows Servers by provisioning a set of restricted Domain Controllers and exposing IP’s on a defined Azure Virtual Network allowing machines on that Virtual Network to Domain Join your Office 365 Tenant. Many admins don’t realize that Office 365 sits on an Azure AD Domain. In this blog I will walk you through:
<ul>
 	<li>Enabling Azure AD Domain Services for your Office 365 Tenant</li>
 	<li>Provisioning and Domain Joining 2 Azure VM’s running Windows Server 2012 R2</li>
</ul>
&nbsp;

We will start by accessing our Office 365 Tenant’s Azure backend. In order to do this we will need to add an Azure Subscription to our Office 365 account. Following the steps below, lets log into our Office 365 Subscription and Add and Azure Subscription to it:

1.  Navigate to <a href="https://portal.office365.com/">https://portal.office365.com</a> and login with your Office 365 Admin Account.

2.  Once logged in navigate to <a href="https://account.windowszure.com/">https://portal.azure.com</a>.

3.  At the <strong>Azure Portal </strong>screen click on the <strong>Billing icon </strong> on the left-side of the screen then click <strong>New subscription</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription1b.png"><img width="909" height="872" class="alignnone size-full wp-image-6315" alt="azuresubscription1b" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription1b.png" /></a><a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription1a.png"></a>

4.  At the <strong>Add subscription </strong>screen click on <strong>Pay-As-You-Go</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription2.png"><img width="901" height="410" class="alignnone size-full wp-image-6325" alt="azuresubscription2" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription2.png" /></a>

5.  At the <strong>About you </strong>enter your information as shown below:

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription3.png"><img width="743" height="535" class="alignnone size-full wp-image-6335" alt="azuresubscription3" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription3.png" /></a>

6.  At the <strong>Identity verification by phone</strong><strong> </strong>enter phone number and click <strong>Call me</strong> as shown below:

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription4.png"><img width="768" height="174" class="alignnone size-full wp-image-6336" alt="azuresubscription4" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription4.png" /></a>

7.  Once you receive the call listen for the <strong>6-Digit Code </strong>and then enter it as shown below and click on <strong>Verify code</strong> as shown below:

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription5.png"><img width="771" height="201" class="alignnone size-full wp-image-6345" alt="azuresubscription5" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription5.png" /></a>

8.  At the <strong>Payment information</strong> screen enter your <strong>Credit Card </strong>information as shown below then click <strong>Next</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription6.png"><img width="691" height="587" class="alignnone size-full wp-image-6355" alt="azuresubscription6" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription6.png" /></a>

9.  At the <strong>Agreement </strong>screen select <strong>I agree </strong>then click <strong>Purchase</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription7.png"><img width="669" height="180" class="alignnone size-full wp-image-6365" alt="azuresubscription7" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription7.png" /></a>asdf

10.  At the <strong>Welcome to Microsoft Azure</strong> screen click on <strong>Get Started with your Azure subscription</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription8.png"><img width="547" height="441" class="alignnone size-full wp-image-6375" alt="azuresubscription8" src="https://msdnshared.blob.core.windows.net/media/2017/02/AzureSubscription8.png" /></a>

Now that we have Added an Azure Subscription to our Office 365 account, we will need enable Azure AD Domain Services in order to join our Server to our Azure AD Domain (Office 365 Tenant).  Azure AD Domain Services is currently only available using the Classic Azure Portal, however we would like to use the New Azure Portal to build out our VM's.  In order to make this happen we will be using a Azure Networking feature called VNet Peering.  VNet peering allows you to link not only Azure Networks using the same Deployment Models, but also between different Deployment Models  (Resource Manager or Classic) as long as they are deployed in the same Region (Ex:  East US, West US, etc.)  VNet peering will allow us to enable Azure AD Domain Services under the Classic Portal which will be linked by VNets to our New Azure Portal where our Servers will be deployed.  Follow the steps below to create and peer our Networks as well as Enable Azure AD Domain Services:

1.  Navigate to <strong>https://manage.windowsazure.com</strong>.

2.  In the Left-Pane click on <strong>NETWORKS </strong>then click on <strong>CREATE A VIRTUAL NETWORK</strong>

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription8.png"><img width="895" height="585" class="alignnone size-full wp-image-6385" alt="azuresubscription8" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription8.png" /></a>

3.  At the <strong>Virtual Network Details </strong>screen enter <strong>ClassicVNet1 </strong>for the <strong>Name</strong>, select <strong>East US </strong>for the <strong>Location</strong> then click <strong>Next</strong>.

!!!Note:  You can select any location that supports Azure AD Domain Services with the Classic Portal as long as you use the same location when creating the Virtual Network within the New Portal in the following steps.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription9.png"><img width="901" height="641" class="alignnone size-full wp-image-6395" alt="azuresubscription9" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription9.png" /></a>

4.  AT the <strong>DNS Servers and </strong><strong>VPN Connectivity </strong>screen click <strong>Next</strong>.

5.  At the <b>Virtual Network Address Spaces</b> screen enter the following then click <b>Complete</b>:
<ul>
 	<li><span>STARTING IP:                                     10.5.0.0</span></li>
 	<li><span>CIDR (ADDRESS COUNT):              /16 (65536)</span></li>
</ul>
<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription10a.png"><img width="895" height="633" class="alignnone size-full wp-image-6595" alt="azuresubscription10a" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription10a.png" /></a><a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription10.png"></a>

Now that we have created our Classic Deployment Model VNet, we can enable our Azure AD Domain Services and link it to this VNet following the steps below:

1.  In the Left-Pane click on <strong>ACTIVE DIRECTORY </strong>then click on your <strong>Office 365 Tenant Name </strong>as shown below:

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription11.png"><img width="687" height="575" class="alignnone size-full wp-image-6415" alt="azuresubscription11" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription11.png" /></a>

2.  At the <strong>Tenant</strong> screen click on <strong>CONFIGURE</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription12.png"><img width="904" height="357" class="alignnone size-full wp-image-6425" alt="azuresubscription12" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription12.png" /></a>

3.  On the <strong>CONFIGURE </strong>screen scroll down to <strong>domain services</strong> and click <strong>Yes </strong><strong></strong>for the <strong>ENABLE DOMAIN SERVICES FOR THIS DIRECTORY </strong>and make sure your <strong>Office 365 Tenant Name</strong> and <strong>ClassicVNet1</strong> are selected then click <strong>Save</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription13.png"><img width="954" height="536" class="alignnone size-full wp-image-6435" alt="azuresubscription13" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription13.png" /></a>

4.  Once setup is complete click <strong>OK</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14.png"><img width="1162" height="119" class="alignnone size-full wp-image-6437" alt="azuresubscription14" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14.png" /></a>

5.  Under <strong>domain services</strong> make a note of the IP(s) created for <strong>Azure AD Domain Services</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14a.png"><img width="722" height="438" class="alignnone size-full wp-image-6505" alt="azuresubscription14a" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14a.png" /></a>

Now that we have Azure AD Domain Services enabled we will need to Enable NTLM and Kerberos credential hash generation before we can Join our VM using our Azure AD Credentials.  Follow the steps below to Enable NTLM and Kerberos credential hash generation for your Azure AD Credentials:

1.  Navigate to <strong>https://myapps.microsoft.com</strong>

2.  In the Top-Right Corner click on your account and select <strong>Profile</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14b.png"><img width="1197" height="312" class="alignnone size-full wp-image-6555" alt="azuresubscription14b" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14b.png" /></a>

3.  Under <strong>Manage Account </strong>click on <strong>Change password</strong>.

4.  At the <strong>Change password </strong>screen enter you Old and New Password then click <strong>Submit</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14d.png"><img width="322" height="388" class="alignnone size-full wp-image-6575" alt="azuresubscription14d" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription14d.png" /></a>

&nbsp;

head over to the New Azure Portal to create our Virtual Network within the Resource Manager Deployment Model which will be used to allow our Azure VM to communicate with Azure AD Domain Services.  Follow the steps below to create and link this Virtual Network:

1.  Navigate to <strong>https://portal.azure.com</strong>

2.  In the Left-Pane click <strong>+ | Networking | Virtual network</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal4a1.png"><img width="674" height="278" class="alignnone size-full wp-image-4106" alt="newazureportal4a" src="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal4a1.png" /></a><a href="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal4a.png"></a>

2.  At the <strong>Virtual network</strong> screen click <strong>Create</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal5a.png"><img width="386" height="401" class="alignnone wp-image-3945" alt="newazureportal5a" src="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal5a.png" /></a>

3.  At the <strong>Create virtual network</strong> screen enter the details shown below then click <strong>Create</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription15.png"><img width="330" height="634" class="alignnone size-full wp-image-6445" alt="azuresubscription15" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription15.png" /></a>

4.  In the Left-Pane click on <strong>Virtual Networks</strong> then in the Right-Pane click on <strong>RMVNet1</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription16.png"><img width="517" height="475" class="alignnone size-full wp-image-6455" alt="azuresubscription16" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription16.png" /></a>

5.  Under <strong>RMVnet1 </strong>click on <strong>Peerings </strong>then click <strong>Add</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription17.png"><img width="401" height="481" class="alignnone size-full wp-image-6465" alt="azuresubscription17" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription17.png" /></a>

6.  At the <strong>Add peering </strong>screen enter the information as shown below then click <strong>OK</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription18.png"><img width="519" height="593" class="alignnone size-full wp-image-6475" alt="azuresubscription18" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription18.png" /></a>

7.  Confirm that the <strong>Peering </strong><strong></strong><strong>Status </strong>shows as <strong>Connected</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription19.png"><img width="509" height="100" class="alignnone size-full wp-image-6485" alt="azuresubscription19" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription19.png" /></a>

<span>Azure VM’s get their DNS Servers defined in two possible ways.  The first which is the default is via DHCP.  The second and the option we will be using is by a Custom IP (Virtual Network or Network Interface).  Since all of our VM’s will share the same Virtual Network, it makes more sense to create the DNS Server at this level. Follow the steps below to define the Azure AD Domain Services IP (192.168.20.4 as notated in the above steps) as the RMVNet1 Virtual Network’s DNS Server.</span>

<span>      1.  In the Left-Pane click on <strong>Resource Groups</strong> then select <strong>Default-Networking</strong>.</span>

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription21.png"><img width="388" height="274" class="alignnone size-full wp-image-6515" alt="azuresubscription21" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription21.png" /></a>

2.  Under the <strong>Default-Networking</strong><strong> </strong>Resource Group click on the <strong>RMVNet1</strong><strong> </strong>Virtual Network<strong>.</strong>

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription22.png"><img width="749" height="595" class="alignnone size-full wp-image-6525" alt="azuresubscription22" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription22.png" /></a>

3.  Under the <strong>RMVNet1 </strong>Virtual Network click on <strong>DNS servers</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription23.png"><img width="757" height="597" class="alignnone size-full wp-image-6535" alt="azuresubscription23" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription23.png" /></a>

4.  At the <strong>RMVNet1</strong><strong> – DNS servers </strong>screen select <strong>Custom</strong>, enter <b>192.168.20.4</b> then click <strong>Save</strong>.

Now that we have connected our Virtual Networks we will be creating our Azure VM.  Follow the steps below to create an Azure VM:

<span>1.  In the Left-Pane click <strong>+ | Compute</strong> <strong>| Windows Server 2012 R2 Datacenter</strong>. </span>

<a href="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal18.png"><img width="517" height="595" class="alignnone size-full wp-image-4115" alt="newazureportal18" src="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal18.png" /></a>

2.  At the <strong>Windows Server 2012 R2 Datacenter</strong> screen click <strong>Create</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal19.png"><img width="425" height="607" class="alignnone size-full wp-image-4125" alt="newazureportal19" src="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal19.png" /></a>

3.  At the <strong>Basics</strong> screen enter the following then click <strong>OK</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription20.png"><img width="553" height="593" class="alignnone size-full wp-image-6495" alt="azuresubscription20" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription20.png" /></a>

<span><strong>***Note:  The virtual machine name will need to be unique for your lab since it’s a hostname within eastus.cloudapp.azure.com.  So KHL-DC is no longer available.</strong> </span>

<strong>4.  At the Choose a size</strong> screen select <strong>DS1_V2 Standard</strong> VM (Best Bang for Buck) then click <strong>Select</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal21.png"><img width="667" height="605" class="alignnone size-full wp-image-4145" alt="newazureportal21" src="https://msdnshared.blob.core.windows.net/media/2016/12/NewAzurePortal21.png" /></a>

6.  At the <strong>Settings </strong>screen accept the defaults then click <strong>OK</strong>.

7.  At the <strong>Summary </strong>screen review your settings then click <strong>OK</strong>.

&nbsp;

Now we will need <span>to connect to our Azure VM (TENANT-WEB) via remote desktop.  To do this follow the steps below:</span>

<span>1.  In the Left-Pane click on <strong>Resource Groups</strong> then select <strong>Default-Networking</strong>.</span>

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription21.png"><img width="388" height="274" class="alignnone size-full wp-image-6515" alt="azuresubscription21" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription21.png" /></a>

2.  Under the <strong>Default-Networking</strong><strong> </strong>Resource Group click on the <strong>TENANT-WEB</strong><strong>.</strong>

3.  Under <strong>TENANT-WEB </strong>click on <strong>Connect</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription24.png"><img width="619" height="65" class="alignnone size-full wp-image-6545" alt="azuresubscription24" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription24.png" /></a>

4.  At the <strong>pop-up </strong>click <strong>Open</strong>.

5.  At the <b>Remote Desktop Connection</b> pop-up click <b>Connect</b>.

6.  At the <b>Windows Security </b>screen enter your credentials.

7.  At the <b>Untrusted Certificate </b>pop-up click <b>Yes</b>.

8.  Once logged in right-click on the Windows Logo and click on <strong>System</strong>.

9.  Under <strong>Computer name, domain and workgroup settings</strong> click on <strong>Change settings</strong>.

10.  At the pop-up screen click on <strong>Change</strong>.

11.  Under <strong>Member of </strong>select <strong>Domain:</strong> then enter <strong>office365tenant.onmicrosoft</strong><strong>.com</strong> and click <strong>OK</strong>.

12.  At the <strong>Computer Name/Domain Changes </strong>pop-up enter your <strong>Domain Admin and Password </strong>in the following format then click <strong>OK:</strong>

office365tenant\Office365-admin

13.  At the <strong>Computer Name/Domain Changes</strong> pop-up click <strong>OK</strong>, <strong>OK</strong>, then <strong>Close</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription25.png"><img width="389" height="172" class="alignnone size-full wp-image-6585" alt="azuresubscription25" src="https://msdnshared.blob.core.windows.net/media/2017/02/azuresubscription25.png" /></a>

14.  Click <strong>Restart Now</strong>.

Once the server has restarted we will re-connect using our local server credentials initially.  This is because by default only Local Administrators are authorized to log on via Remote Desktop.  Use the steps below to add your Azure AD credentials (OFFICE365TENANT\Office365-admin) as a Local Administrator or TENANT-WEB:

1.  Once logged onto <strong>TENANT-WEB</strong> with our <strong>Tenant-Admin </strong>local account right-click on the <strong>Windows Logo </strong>and select <strong>Computer Management</strong>.

2.  In the Left-Pane expand <strong>System Tools | Local Users and Groups </strong>then select <strong>Groups</strong>.

3.  In the Right-Pane double-click <strong>Administrators</strong>.

4.  At the <strong>Administrators Properties </strong>window click <strong>Add </strong><strong>then</strong> enter <strong>Office365-Admin</strong> and click <strong>OK</strong>.

5.  At the <strong>Windows Security </strong>pop-up enter you <strong>Azure AD Credentials </strong>then click <strong>OK, OK.</strong>

6.  Log off of <strong>TENANT-WEB</strong>.

Now that we have added our <strong>Azure Ad Credentials </strong>as a Local Administrator of our Server we should be authorized to connect via Remote Desktop using these credentials.  Once logged in to the server with our Azure AD Credentials we have successfully confirmed our Azure AD Domain Services are working.  To take it one step further, lets take a look at our Active Directory Structure.  In order to do this we will need to load our RSAT (Remote Server Administration Tools) using the steps below:

1.  From the taskbar click on <strong>Server Manager</strong>.

2.  Under the <strong>Configure this local server</strong> section click on <strong>Add roles and features</strong>.

3.  At the <strong>Before you begin </strong>screen click <strong>Next</strong>.

4.  At the <strong>Select installation type</strong> screen click <strong>Next</strong>.

5.  At the <strong>Select destination server</strong> screen click <strong>Next</strong>.

6.  At the <strong>Select server roles</strong> screen click <strong>N</strong><strong>ext</strong>.

7.  At the <strong>Select features </strong>screen select <strong>Remote Server Administration Tools</strong><strong> </strong>then at the <strong>Add Roles and Features Wizard </strong>pop-up click on <strong>Add Features</strong>

8.  Expand <strong>Remote Server Administration Tools | Role Administration Tools </strong>and select <strong>DNS Server Tools </strong>then <strong>Next</strong>.

9.  At the <strong>Web Server Role (IIS)</strong> screen click <strong>Next</strong>.

10.  At the <strong>Select role services </strong>screen click <strong>Next</strong>.

11.  At the <strong>Confirmation </strong>screen click <strong>Install</strong>.

12.  When setup is complete click on <strong>Close</strong>.

&nbsp;

Let's launch <strong>Active Directory Users and Computers </strong>to take a look at our newly created credentials.  Within <strong>Server Manager </strong>in the Top-Right corner click on <strong>Tools</strong><strong> </strong>then select <strong>Active Directory Users and Computers</strong>.

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC1.png"><img width="364" height="430" class="alignnone size-full wp-image-6605" alt="aduc1" src="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC1.png" /></a>

As you can see below we are now looking at our Azure Active Directory instance within the traditional Active Directory User and Computers (ADUC) Toolset:

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC2.png"><img width="759" height="537" class="alignnone size-full wp-image-6615" alt="aduc2" src="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC2.png" /></a>

The two Organizational Units that we are concerned with are the <strong>AADDC Computers</strong> and <strong>AADDC Users</strong>.  <strong>AADDC Computers</strong> will contain any Azure AD Domain Services Joined Servers/Workstations.  As shown below we should see our test VM TENANT-WEB that was joined earlier in the article:

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC3.png"><img width="753" height="536" class="alignnone size-full wp-image-6625" alt="aduc3" src="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC3.png" /></a>

AADDC Users actually contains all of your Office 365 accounts as shown below:

<a href="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC4.png"><img width="899" height="537" class="alignnone size-full wp-image-6635" alt="aduc4" src="https://msdnshared.blob.core.windows.net/media/2017/02/ADUC4.png" /></a>

This completes this article now that we have successfully proven that we can Domain-Join our Azure IAAS VM to our Office 365 Tenant in addition to gaining Administrative Access via ADUC to our Azure AD which our Office 365 Subscription rides on.  Hopefully you enjoyed this article.

-Elliott

&nbsp;]]></content:encoded>
    </item>
    <item>
      <title>Home Lab Secrets:  Using RemoteApps</title>
      <link>https://docs.microsoft.com/archive/blogs/elliottf/home-lab-secrets-using-remoteapps</link>
      <pubDate>Wed, 27 Jan 2016 18:58:00 GMT</pubDate>
      <dc:creator><![CDATA[ELLIOTTF - Elliott Fields Jr]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/elliottf/2016/01/27/home-lab-secrets-using-remoteapps/</guid>
      <description><![CDATA[One cool feature with Windows 2012 R2 is the Remote Desktop Gateway feature. RD Gateway uses the...]]></description>
      <content:encoded><![CDATA[<p align="LEFT" dir="LTR">One cool feature with Windows 2012 R2 is the Remote Desktop Gateway feature. RD Gateway uses the Remote Desktop Protocol (RDP) over HTTPS to establish a secure, encrypted connection between remote users on the Internet and internal network resources. RD Gateway is&nbsp;a well know feature, but another feature which is&nbsp;just as cool is RemoteApps. This feature can&nbsp;&nbsp;leverage&nbsp;the RD Gateway&nbsp;technology to allow sessions for applications instead of desktop. This allows you to launch RDP (.rdp) files that launch your requested application directly instead of running a full desktop. A little known secret is the fact that this technology can be leveraged on any of the following operating systems which include workstations, without having a RemoteApp Server!!!</p>
<ul>
<li>Windows 2012/2012 R2</li>
<li>Windows 2008/2008 R2</li>
<li>Windows 8.1/10</li>
</ul>
<p align="LEFT" dir="LTR">The first thing we need to do is logon to the workstation or server that has the Application that we would like to launch. For the purposes of this lab I will be using the following test machines.</p>
<p align="LEFT" dir="LTR"></p>
<ul>
<li>RemoteApp81 (Windows 8.1 Workstation running Word 2013)</li>
<li>MSCORP-WPJ (Windows 10 Workstation running Word 2016)</li>
</ul>
<p align="LEFT" dir="LTR"></p>
<p>Log onto <b>MSCORP-WPJ </b>and open the registry by using <b>regedit.</b></p>
<p><b><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/regedit.jpg"><img alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/regedit.jpg" border="0" /></a><br /></b></p>
<p></p>
<p>As shown in the Image below navigate to the following registry key:</p>
<p>HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList</p>
<p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/TSAppAllowList.jpg"><img alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/TSAppAllowList.jpg" border="0" /></a></p>
<p align="LEFT" dir="LTR"></p>
<p align="LEFT" dir="LTR">Change the <b>fDisabledAllowList</b> value from a <b>0</b> to a <b>1</b>.</p>
<p align="LEFT" dir="LTR"></p>
<p>Now we need to Log Off of <b>MSCORP-WPJ</b>.</p>
<p align="LEFT" dir="LTR">***Note: Workstation1 must be logged off in order for Workstation2 to stream it&rsquo;s applications. If someone is logged on when this application is launched remotely they will need to consent to the remote connection in order to allow the application to launch.</p>
<p align="LEFT" dir="LTR"></p>
<p align="LEFT" dir="LTR">Now its team to head over to <b>RemoteApp81</b> and create our .rdp file which will launch our application directly. Follow the steps below to create this .rdp file:</p>
<p>Log onto <b>RemoteApp81</b>.</p>
<p></p>
<p>Launch the <b>Remote Desktop Connection</b> by running <b>mstsc</b>.</p>
<p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/mstsc.jpg"><img alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/mstsc.jpg" border="0" /></a></p>
<p align="LEFT" dir="LTR"></p>
<p align="LEFT" dir="LTR"></p>
<p align="LEFT" dir="LTR">At the <b>Remote Desktop Connection </b>windows enter <b>MSCORP-WPJ</b> under <b>Computer:</b></p>
<p></p>
<p>Click on the <b>Show Options</b> then click on the <b>Save As</b> button.</p>
<p></p>
<p>At the <b>Save As </b>pop-up enter <b>MSCORP-WPJ</b> then click <b>Save</b>.</p>
<p></p>
<p>Use <b>Notepad </b>to open the <b>MSCORP-WPJ.rdp </b>file.</p>
<p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/Edit-RDP.jpg"><img alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/Edit-RDP.jpg" border="0" /></a></p>
<p align="LEFT" dir="LTR"></p>
<p>Change the following values within <b>MSCORP-WPJ.rdp</b>:</p>
<ul>
<li>Remoteapplicationmode:i:1</li>
<li>Alternate shell:s:rdpinit.exe</li>
</ul>
<p></p>
<p align="LEFT" dir="LTR">Now add the following line and save the .rdp file:</p>
<ul>
<li>Remoteapplicationprogram:s:winword.exe</li>
</ul>
<p align="LEFT" dir="LTR"></p>
<p>Double-click the <b>MSCORP-WPJ.rdp</b>.</p>
<p></p>
<p>At the <b>RemoteApp</b> pop-up click <b>Connect</b>.</p>
<p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/RemoteApp.jpg"><img alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/RemoteApp.jpg" border="0" /></a></p>
<p align="LEFT" dir="LTR"></p>
<p align="LEFT" dir="LTR">At the <b>Windows Security </b>pop-up enter your <b>User Credentials</b>.</p>
<p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/Windows-Security.jpg"><img alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/Windows-Security.jpg" border="0" /></a></p>
<p align="LEFT" dir="LTR"></p>
<p align="LEFT" dir="LTR">At the <b>Certificate Mismatch Warning</b> click <b>Yes</b>.</p>
<p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/Certificate-Mismatch.jpg"><img alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/68/Certificate-Mismatch.jpg" border="0" /></a></p>
<p align="LEFT" dir="LTR"></p>
<p align="LEFT" dir="LTR">Congratulations you are now successfully streaming Word 2016 from the remote workstation using RemoteApp. Another secret is the use of Internet Explorer on the remote machine. When IE is launched as the RemoteApp. You can then navigate thru the remote computer&rsquo;s file system and launch most applications.</p>]]></content:encoded>
    </item>
    <item>
      <title>Assigning Static IP’s to Azure VM’s</title>
      <link>https://docs.microsoft.com/archive/blogs/elliottf/assigning-static-ips-to-azure-vms</link>
      <pubDate>Fri, 12 Jun 2015 12:22:00 GMT</pubDate>
      <dc:creator><![CDATA[ELLIOTTF - Elliott Fields Jr]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/elliottf/2015/06/12/assigning-static-ips-to-azure-vms/</guid>
      <description><![CDATA[One of the challenges of deploying an VM within Azure is the fact that it’s IP Address is DHCP...]]></description>
      <content:encoded><![CDATA[<span style="font-family: Calibri;font-size: medium">One of the challenges of deploying an VM within Azure is the fact that it’s IP Address is DHCP issued.  Obviously this can be an issue for VM’s that hold Services that require a static IP address (Domain Controller, DNS Server, Exchange Server, etc.)  Although setting an Azure VM’s IP Address to to Static is not supported, we can set it to use a DHCP reservation.  This reservation will ensure that the VM always get the same IP Address.  This can be accomplished by using the Azure Preview Portal.  The steps for this are listed below:</span>

<span style="font-family: Calibri;font-size: medium"> </span>

<span style="font-family: Calibri;font-size: medium">Warning:  The steps below will result in a New Network Adapter being provisioned for the VM and therefore will cause downtime.  Only perform this operation during a planned maintenance window or within a lab environment.
</span>
<ol>
 	<li>Navigate to <strong>portal.azure.com</strong></li>
 	<li>In the <strong>Left-Pane</strong> select <strong>Browse</strong>.</li>
 	<li>Scroll down and select <strong>Virtual machines</strong>.</li>
 	<li>In the <strong>Middle-Pane</strong> select the <strong>Virtual Machine</strong> that you will be assigning the Static IP to.</li>
 	<li>In the <strong>Virtual Machine – Pane</strong> select <strong>Settings</strong>.</li>
 	<li>Under the <strong>Settings – Pane</strong> select <strong>IP addresses</strong>.</li>
 	<li>Under the <strong>IP addresses – Pane</strong> under the <strong>Private IP address</strong> section select <strong>Static</strong> for <strong>IP address assignment</strong>, then under <strong>IP address</strong> enter the Static IP Address that you would like to use.</li>
 	<li>Click on the <strong>Save</strong> button at the top of the <strong>IP addresses – Pane</strong> then Click <strong>Yes</strong> to Confirm.</li>
</ol>
<span style="font-family: Calibri;font-size: medium">Once these steps have been completed the IP of the VM will stay the same throughout it’s life, unless you manually change it.  This will also keep the IP Address reserved for Shutdown (Deallocated) VM’s as well.</span>

<span style="font-family: Calibri;font-size: medium">Enjoy!!!</span>

<span style="font-family: Calibri;font-size: medium">-Elliott</span>]]></content:encoded>
    </item>
    <item>
      <title>Using Smartcards/CACs to Manage Windows Azure via Powershell</title>
      <link>https://docs.microsoft.com/archive/blogs/elliottf/using-smartcardscacs-to-manage-windows-azure-via-powershell</link>
      <pubDate>Mon, 01 Jun 2015 19:02:00 GMT</pubDate>
      <dc:creator><![CDATA[ELLIOTTF - Elliott Fields Jr]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/elliottf/2015/06/01/using-smartcardscacs-to-manage-windows-azure-via-powershell/</guid>
      <description><![CDATA[Even though Windows Azure VM&#039;s can be managed from either the Azure Portal or Microsoft Azure...]]></description>
      <content:encoded><![CDATA[<p><span style="font-family:Calibri;font-size:medium">Even though Windows Azure VM&#039;s can be managed from either the Azure Portal or Microsoft Azure PowerShell, some tasks can only be performed using Microsoft Azure PowerShell.&nbsp; In order to Manage windows Azure using PowerShell you must first prepare your workstation by completing the following:</span></p>
<ul>
<li>
<p>Installing Microsoft Azure PowerShell</p>
</li>
<li>
<p>Importing the Azure Subscription Publish Settings File</p>
</li>
<li>
<p>Adding Azure Account</p>
</li>
</ul>
<p><span style="font-family:Calibri;font-size:medium">These steps are pretty straight forward, however you organization might require CAC/Smartcard authentication to Corporate resources so the following steps can be performed to utilize an existing Smartcard to authenticate to Windows Azure PowerShell.</span></p>
<p><b><i><span style="font-family:Calibri;font-size:medium">&nbsp;</span></i></b></p>
<p><b><i><span style="font-family:Calibri;font-size:medium">Installing Microsoft Azure PowerShell</span></i></b></p>
<p><span style="font-family:Calibri;font-size:medium">The easiest method for installing Microsoft Azure PowerShell is using the <b>Microsoft Web Platform Installer</b>.&nbsp; This installing will also install requirements like <b>Microsoft .NET Framework 4.5</b>.&nbsp; It can be downloaded from the following Link:</span></p>
<p><a href="https://go.microsoft.com/fwlink/p/?linkid=320376&amp;clcid=0x409"><span style="color:#0563c1;font-family:Calibri;font-size:medium">https://go.microsoft.com/fwlink/p/?linkid=320376&amp;clcid=0x409</span></a></p>
<p><span style="font-family:Calibri;font-size:medium">&nbsp;</span></p>
<ol>
<li>
<p>When prompted execute the <b>WindowsAzurePowerShell.3f.3f.3fnew.exe</b> click <b>Run</b>.</p>
</li>
<li>
<p>At the <b>Web Platform Installer 5.0 </b>click <b>Install</b>.</p>
</li>
<li>
<p>At the next pop-up select <b>I Accept</b>.</p>
</li>
<li>
<p>At the next screen click <b>Finish</b>, then <b>Exit</b>.</p>
</li>
</ol>
<p><b><i><span style="font-family:Calibri;font-size:medium">Managing Management Certificates</span></i></b></p>
<p><span style="font-family:Calibri;font-size:medium">Microsoft Azure is a Subscription based service.&nbsp; In order to Manage your subscription using a Smartcard, the Public Key of the Certificate must be uploaded using the Azure Portal.&nbsp; The first step in this process is extracting the Public Key from your Smartcard.</span></p>
<p><i><span style="font-family:Calibri;font-size:medium">Extracting the Public Key</span></i></p>
<ol>
<li>
<p>Navigate to Start | Run.</p>
</li>
<li>
<p>In the Open: section enter mmc then click OK.</p>
</li>
<li>
<p>At the MMC navigate to File | Add/Remove Snap-in.</p>
</li>
<li>
<p>In the Left-Column select Certificates then click Add.</p>
</li>
<li>
<p>At the Certificates snap-in pop-up windows select My user account then click Finish then OK.</p>
</li>
<li>
<p>Insert your Smartcard into the Smartcard Reader.</p>
</li>
<li>
<p>In the Left-Column expand Certificates &ndash; Current User | Personal and right-click Certificates and select Refresh.&nbsp; (At this point your Smartcard Certificates should be visible)</p>
</li>
<li>
<p>In the Right-Column right-click the Certificate being exported and select All Tasks | Export.</p>
</li>
<li>
<p>At the Welcome to the Certificate Export Wizard select Next.</p>
</li>
<li>
<p>At the Export Private Key screen click Next.</p>
</li>
<li>
<p>At the Export File make sure <b>Base-64 encoded X.509 (.CER)</b> is selected then click Next.</p>
</li>
<li>
<p>At the File to Export screen enter C:\Smartcard.cer under File name: then click Next then Finish.</p>
</li>
</ol>
<p><i><span style="font-family:Calibri;font-size:medium">Uploading the Certificate</span></i></p>
<p><span style="font-family:Calibri;font-size:medium">Once we have successfully exported the Public Key of our Smartcard we need to upload it to the Azure Portal for usage with our Subscription.&nbsp; This can be accomplished by completing the following steps:</span></p>
<ol>
<li>
<p>Navigate to the Azure Portal and Login</p>
<p>&nbsp;</p>
<p><a href="https://manage.windowsazure.com/"><span style="color:#0563c1">https://manage.windowsazure.com</span></a></p>
<p>&nbsp;</p>
</li>
<li>
<p>At the <b>Microsoft Azure</b> screen enter your logon account then click <b>Continue</b>.</p>
</li>
<li>
<p>At the next screen select <b>Microsoft account</b>.</p>
</li>
<li>
<p>At the <b>Sign in</b> screen enter your password then click <b>Sign in</b>.</p>
</li>
<li>
<p>In the Left-Column scroll down and select <b>SETTINGS</b>.</p>
</li>
<li>
<p>Under the Middle-Column under Settings select <b>MANAGEMENT CERTIFICATES</b> then on the bottom toolbar click <b>UPLOAD</b>.</p>
</li>
<li>
<p>At the <b>Upload a management certificate</b> pop-up click <b>FILE</b> then navigate to <b>C:\Smartcard.cer</b> then click <b>Open</b> and click on the <b>OK Checkbox</b>.</p>
<p>(Note:&nbsp; Stay logged in to the Portal.&nbsp; This will prevent you from having to re-enter your credentials for the next step.)</p>
</li>
</ol>
<p><i><span style="font-family:Calibri;font-size:medium">&nbsp;</span></i></p>
<p><i><span style="font-family:Calibri;font-size:medium">Downloading the Azure Publish Settings File</span></i></p>
<p><span style="font-family:Calibri;font-size:medium">The Azure Publish Settings File contains the following information about your Subscription:</span></p>
<ul>
<li>
<p>ServiceManagementURL</p>
</li>
<li>
<p>ID</p>
</li>
<li>
<p>Name</p>
</li>
<li>
<p>All Management Certificates Uploaded in the Azure Portal</p>
</li>
</ul>
<p><span style="font-family:Calibri;font-size:medium">The Azure Publish Settings file can be downloaded by using the following steps:</span></p>
<ol>
<li>
<p>Launch Microsoft Azure Powershell.</p>
</li>
<li>
<p>At the prompt, enter the following command:</p>
<p>&nbsp;</p>
<p>Get-AzurePublishSettingsFile</p>
<p>&nbsp;</p>
</li>
<li>
<p>At the <b>File Download</b> select the <b>Save </b>pull-down menu and then select <b>Save as</b>.</p>
</li>
<li>
<p>At the <b>Save As</b> pop-up enter a name for the file then click <b>Save</b> (Subscription.publishsettings)</p>
</li>
</ol>
<p><span style="font-family:Calibri;font-size:medium">&nbsp;</span></p>
<p><i><span style="font-family:Calibri;font-size:medium">Modifying the Azure Publishing File</span></i></p>
<p><span style="font-family:Calibri;font-size:medium">By default the <b>Azure Publishing File </b>contains the Public Key for the default Management Certificate created with the Azure Subscription.&nbsp; The steps below can be used to modify the Azure Publishing File to utilize your Smart Card Certificate Public Key:</span></p>
<ol>
<li>
<p>Navigate to the location that you saved your Public Key (C:\Smartcard.cer).</p>
</li>
<li>
<p>Right-click the <b>c:\Smartcard.cer</b> and select <b>Open with,</b> then select <b>Notepad</b>.</p>
</li>
<li>
<p>Select and Copy the Public Key of your certificatesection between the <b>-----BEGIN CERTIFICATE----- </b>&nbsp;and <b>----- END CERTIFICATE -----</b></p>
</li>
<li>
<p>Navigate to the location that you saved the AzurePublishSettingsFile.</p>
</li>
<li>
<p>Right-click the AzurePublishSettingsFile and select <b>Open with</b> then select <b>Notepad</b>.</p>
</li>
<li>
<p>Locate the <b>ManageCertificate=</b> section and paste your copied Public Key then Save the File.</p>
</li>
</ol>
<p><span style="font-family:Calibri;font-size:medium">&nbsp;</span></p>
<p><i><span style="font-family:Calibri;font-size:medium">Connecting to and Manage your Azure Publish Subscription</span></i></p>
<p><span style="font-family:Calibri;font-size:medium">Now that we have successfully uploaded our Management Certificate and downloaded our Azure Publish Settings File, we can now successfully connect to our Azure Subscription using the following steps:</span></p>
<ol>
<li>
<p>Launch Microsoft Azure Powershell.</p>
</li>
<li>
<p>At the prompt, enter the following command:</p>
<p>&nbsp;</p>
<p>Import-AzurePublishSettingsFile &ndash;PublishSetingsFile MySubscription.publishsettings</p>
<p>&nbsp;</p>
</li>
<li>
<p>Test your newly Imported Certificate by issuing the command below:</p>
<p>&nbsp;</p>
<p>Get-AzureVM</p>
<p>&nbsp;</p>
</li>
</ol>
<p><span style="font-size:medium"><span style="font-family:Calibri">If everything is configured correctly a list of all of your Azure VM&rsquo;s will be returned. </span>J</span></p>
<p><span style="font-family:Calibri;font-size:medium">&nbsp;</span></p>
<p><span style="font-family:Calibri;font-size:medium">Enjoy</span></p>
<p><span style="font-family:Calibri;font-size:medium">-Elliott</span></p>
<p><span style="font-family:Calibri;font-size:medium">&nbsp;</span></p>
<p></p>]]></content:encoded>
    </item>
  </channel>
</rss>