This is something I had wanted to do for a while. Finally did welcome Charles Joy, a Principal Program Manager on the Azure Stack team, back to the show and we discussed the recent release of Microsoft Azure Stack Technical Preview 1. It’s a fun episode. Enjoy it.
Microsoft Azure RemoteApp is a solution which can be rapidly deployed for anywhere accessing remote resources with a variety of devices including Windows, Mac OS X, iOS, or Android. A user will install a Microsoft Remote Desktop client on an Internet-connected laptop, tablet, or phone and access RemoteApp applications running in Microsoft Azure, as if they were running on the user’s local computer. Notice that the stand URL to acquire Microsoft Azure RemoteApp client is https://www.remoteapp.windowsazure.com/. A Microsoft Azure subscription can create up to five RemoteApp services. Here’s an introduction.
IT also has an option to deploy RemoteApp as a stand-alone cloud service with Microsoft pre-built application collections or integrated with on-premises RDS infrastructure by bringing your own RDSH. The former is quite easy to set up and what this blog post presents. While the latter is a hybrid deployment scenario bridging on-premises RDS infrastructure with RemoteApp service in the cloud. In this case, IT will need to create a virtual network with defined address spaces and establish VPN connectivity between on-premises network and Azure RemoteApp.
IT now has an option to enable users to access corporate applications from anywhere and on a variety of devices by employing Azure RemoteApp without the need to deploy on-premises infrastructure. Both the application deployment and the user access of Azure RemoteApp are provided as services, while RemoteApp applications are centralized, protected, and running in Microsoft Azure which can publish, scale, or unpublish corporate applications on demand, as business needs change.
Overall, RemoteApp is a cost-effective solution for today’s dynamic business environment and a best-fit for serving fluctuating workforce or fast-changing business requirements. To assess RemoteApp, a Microsoft Azure subscription is required.
Freely available is a 30-day trial subscription at http://aka.ms/R2 which is a Microsoft landing page for downloading evaluation copies of Windows Server and System Center products. There is also an option to deploy Windows Server 2012 R2 Datacenter on Microsoft Azure. This is the option to start a registration process for acquiring a Microsoft Azure 30-Day trial subscription.
To ensure identity, credit card information is required. However, prior to the expiration a trial subscriber will get email notification to op-in or op-out. It is a direct way to test Microsoft Azure in production, live and free.
As of June 2014, RemoteApp is still in preview and one will need to sign up the preview feature to make the RemoteApp option available, once approved. After logging into Microsoft Azure Management Portal, a subscriber can access preview offerings by clicking the View My Bill option of the dropdown menu form the subscriber ID on the upper right corner. And notice in general the approval process of activating a preview feature is not immediate and some may take up a few days.
Once approved, the feature becomes available from the left navigation pane.
Quick Create is to deploy RemoteApp as a Stand-Alone cloud service. A RemoteApp deployment may take about 30 minutes for Azure to complete. The process followed is to publish applications, configure user access, and installing the client. It is very straightforward. When entering a user or group that you want to grant access to for this service. Use the “user@domain” or “domain/user” format. The user must be either a Microsoft Account, or a user or group account homed in the Default Directory of Azure Active Directory.
Start with REMOTEAPP workspace by clicking +NEW.
Here, just click Quick Create, specify a name, a region, and an application collection.
Once created, click the name or arrow to display the dashboard.
Like other Azure offerings, by default Quick Start page is first shown. A Quick Start page usually presents essential information and is a great resource page.
As described in the Quick Start page, publishing RemoteApp programs, configuring user access and installing the RemoteApp client is the process to configure a RemoteApp service.
Click either one to display the application collections.
Identify applications to be published and save the settings.
When entering user information, use the “user@domain” or “domain/user” format. The user must be either a Microsoft Account, or a user or group account homed in the Default Directory of Azure Active Directory.
Pick an intended client. Here, I picked Windows x64 client.
Starts an installation of the RemoteApp client.
The RemoteApp tile is placed in APPS page, once the client installed.
Start configuring the user information.
Once authenticated, the published applications are displayed.
This is the About information.
Here’s Office Word coming up.
Can save a file to OneDrive or locations visible to local File Explorer.
My presentation on Deploying Windows 8.1 and Windows 7 in Microsoft Azure
This article provides a background of Microsoft Azure RemoteApp. A walk-through on how to deploy RemoteApp as a stand-alone cloud service is also available.
This is a combination of Remote Desktop and highly scalable Windows server-based applications hosted in Microsoft Azure. Company published applications are centrally managed and protected in Microsoft Azure. At the same time, employees can access authorized corporate applications from anywhere as if the applications are running locally on devices of their choices including Windows, Mac OS X, iOS, and Android.
To try Azure RemoteApp, first acquire a Microsoft Azure subscription from http://aka.ms/R2 by selecting Windows Server 2012 R2 Datacenter on Microsoft Azure from the dropdown list to kick off a registration process.
Today’s dynamic business environment and increasing user expectations demand always-on connectivity and accessibility to LOB applications with an individual’s preferred devices. The trend of BYOD signifies the business needs and personal work styles to be productive anytime anywhere with any device. 
Azure RemoteApp eliminates the physical aspects of an application infrastructure and converts a global application deployment into logical processes and operations carried out remotely on a proven and secure platform. It embraces IT industry’s BYOD initiative and realizes two key attributes, self-servicing and ubiquitous access, of cloud computing from a user’s point of view. With Azure RemoteApp, IT can scale and maintain applications very productively, and respond timely and even proactively to dynamic business needs without large capital requirements, without compromising security, without lowering user expectations.
Azure RemoteApp enables IT to centrally manage corporate applications and reduces the complexity and administrative overhead in deployment scenarios including:
With Azure RemoteApp, a company has an opportunity to pursue a hybrid application deployment solution by integrating on-premises infrastructure and Remote Desktop Session Hosts. Or deploy Azure RemoteApp using pre-built application collections for a stand-alone cloud service, essentially Microsoft Azure hosts and stores all data for programs in cloud. There are also options for IT to authenticate a user with existing corporate credentials or a Microsoft Account. Azure RemoteApp presents a strategic, high-speed, and reliable vehicle for IT to transition on-premises application deployment into a corporate SaaS model in Microsoft Azure.
Azure RemoteApp applications are neither sent to, nor stored on employee devices. Employees download and install Microsoft Remote Desktop clients on their Internet-connected devices like 
laptop, tablet, and phone to access applications via Microsoft Remote Desktop Protocol as if those applications were installing and running locally. The applications are centrally managed on Microsoft Azure, the same platform trusted and used by governments, financial services companies, and other large organizations dealing with sensitive information.
Instead of being presented to the user in the desktop of the Remote Desktop Session Host (RD Session Host) server, the RemoteApp program is integrated with the client’s desktop. A RemoteApp program runs in its own resizable window, can be dragged between multiple monitors, and has its own entry in the taskbar. If a user is running more than one RemoteApp program on the same RD Session Host server, the RemoteApp program will share the same Remote Desktop Services session.
One thing about cloud computing is that all deliveries must be right there and then. Instant gratification is essential in everything we do in cloud. And it is the same with assessing a new service like Azure RemoteApp. Go to this DIY Public Demos, experience it now, and realize that application deployment is never the same.
At TechEd 2014 North America, Microsoft has announced a large set of new innovations for IT Professionals & Enterprise developers to embrace a cloud culture in today’s mobile first, cloud first world. The following is a summary based on Brad Anderson’s keynote on May 5, 2014. I have highlighted my personal favorites.
We are announcing the general availability of the ExpressRoute service. AT&T and Equinix customers are able to use the ExpressRoute service at Silicon Valley, Washington, and London ExpressRoute locations. We are excited to announce a new partnership with TelecityGroup and SingTel which will expand ExpressRoute’s reach in Europe and APAC, and a new partnership with Zadara, which allows Azure customers to use Zadara storage via ExpressRoute in the U.S. ExpressRoute creates private, high-throughput connections between Azure datacenters and your existing infrastructure, whether it’s on-premises or in a colocation environment.
We are announcing the general availability of compute-intensive A8 and A9 instances for virtual machines. These instances provide faster processors, faster interconnectivity, more virtual cores for higher computing power, and larger amounts of memory. With these instances, customers can run compute-intensive and network-intensive applications such as high-performance cluster applications and applications that use modeling, simulation and analysis, and video encoding.
We are announcing the public preview of Azure Files. This new service enables virtual machines in an Azure datacenter to mount a shared file system using the SMB protocol. These VMs will then be able to access the file system using standard Windows file APIs (CreateFile, ReadFile, WriteFile, etc.). Many VMs (or platform-as-a-service roles) can attach to these file systems concurrently, so customers can share persistent data easily between various roles and instances.
We are announcing the general availability of Azure Import/Export service. By using Azure Import/Export, customers can move large amounts of data into and out of Azure Blobs much faster than is possible by downloading data from the internet. Transporting data from hard drives to Azure is easy when using the Microsoft high-speed, security-enabled internal network to transfer the data to our datacenter.
We are announcing the public preview of Microsoft Antimalware and partnerships with Trend Micro and Symantec. For Microsoft Antimalware, we are providing customers the choice on which anti-virus solution to use. One of those solutions is in partnership with Trend Micro. Specifically, deep integration for Trend’s Deep Security™ and SecureCloud™ products in the Azure platform. Additionally, Microsoft is also working to integrate PortalProtect™ with Azure. Another solution we are announcing is in partnership with Symantec. Symantec End Point Protection (SEP) is being supported on Azure. Through deep portal integration, customers have the ability to specify that they intend to use SEP within a VM.
We are announcing the public preview of Internal Load Balancing. This new service provides the ability to load balance Azure virtual machines with private IP addresses. The internally load balanced endpoint will be accessible only within a virtual network (if the VM is within a virtual network) or within a cloud service (if the VM isn’t within a virtual network). Internal Load Balancing is available in the standard tier of VMs at no additional cost.
We are announcing general availability of the two most requested virtual networking features: multiple site-to-site VPN and VNET-to-VNET connectivity. Virtual Network now supports more than one site-to-site VPN connection so customers can securely connect multiple on-premises locations with a virtual network (VNET) in Azure. VNET-to-VNET connectivity enables multiple virtual networks to be directly and securely connected with one another. We are enabling both cross-region VNET-to-VNET and in-region VNET-to-VNET connectivity.
We are announcing the IP Reservation for VIPs and public preview of Instance-level public IPs for virtual machines. For IP reservation, customers can now reserve public IP addresses and use them as virtual IP (VIP) addresses for their applications. This enables scenarios where applications need to have static public IP addresses or where applications need to be updated by swapping the reserved IP addresses. During preview, customers can obtain two public IP addresses per subscription at no additional charge. With Instance-level Public IPs for VMs, customers can now assign public IP addresses to their virtual machines, so they become directly addressable without having to map an endpoint. This feature will enable scenarios like running FTP servers in Azure and monitoring virtual machines directly using their IPs.
We are announcing new capabilities for Azure Hyper-V Recovery Manager that will be in public preview next month. Today, Windows Azure Hyper-V Recovery Manager provides a disaster recovery solution for customers which helps protect the availability of System Center private clouds. In June a public preview of new features will enable customers to replicate virtual machines from their primary site directly to Azure, instead of a second customer site. To better reflect the service’s new, broader capabilities we will be renaming it Microsoft Azure Site Recovery in conjunction with the release of this preview. Updated resources, including an Academy Live, will be available in June at time of public preview.
We are announcing the public preview of Azure RemoteApp: a new service delivering remote applications from the Azure cloud. With Azure RemoteApp, business applications run on Windows Server in the Azure cloud where they’re easier to scale and update. Employees install Microsoft Remote Desktop clients on their Internet-connected laptop, tablet, or phone—and can then access applications as if they were running locally.
Azure RemoteApp helps IT:
Azure RemoteApp is available at no additional cost during the preview period. For detailed information, please refer to the following resources:
We have announced the public preview of more enhancements and capabilities in Azure Active Directory Premium. The public preview of these additional enhancements to the service include a new version of the DirSync tool, a new synchronization engine (Azure AD Sync), and Multi-Factor Authentication IP whitelisting allowing companies to specify IP addresses from which MFA is not required. We also announced the public preview of Azure AD Cloud App Discovery feature that provides IT departments with visibility into all the cloud apps used within their organization.
Future investments for Windows Intune are in the areas of managed productivity, including the ability to apply data management and protection policies to an upcoming release of Office mobile apps, and corporate-owned mobile device management.
We are announcing the public preview of Azure API Management. This new service enables organizations to publish APIs to developers, partners and employees securely and at scale. Organizations can use API Management to monetize its core product, transform its product into a platform and create new content distribution channels.
First, Azure Managed Cache service is moving from public preview to general availability. Second, Azure Redis Cache service is available in public preview. Azure Redis Cache is based on the popular open source Redis Cache. A cache created using Redis Cache is accessible from any application within Azure. And, lastly, as previously announced, Azure Shared Caching Service will be retired in September 2014 and with it the Microsoft’s Silverlight-based portal. Because the Azure Cache Service is in general availability, we strongly encourage customers to migrate all existing caches on Shared Caching to the new Azure Managed Cache Service.
We are announcing the general availability of Azure Traffic Manager, which supports both Azure endpoints and external endpoints. Traffic Manager enables customers to control the distribution of user traffic to specified endpoints. With support for endpoints that can reside outside of Azure, customers can now build highly available applications across Azure and on-premises. In addition, intelligent traffic management policies can be applied across all managed endpoints.
We are announcing the public preview of BizTalk Hybrid Connections. This new Azure service enables cloud services to more securely, quickly, and easily integrate Azure cloud solutions with on-premises applications. With no custom code required, Hybrid Connections enables customers to connect to any on-premises TCP or HTTP resource—such as Microsoft SQL Server, MySQL, or any web service—from Azure Web Sites.
We are announcing the release of BizTalk Server 2013 R2. For over a decade, Microsoft customers and partners have deployed thousands of mission-critical integration solutions using BizTalk. This release enables customers to upgrade now with confidence by delivering improvements in performance, reliability, and functionality. Biz Talk Server 2013 R2 allows customers to take advantage of the latest integration platform capabilities from Microsoft and accelerate solutions for vertical industries including healthcare and financial services.
We are announcing the RTM of Visual Studio 2013 Update 2. With over 5 Million downloads of Visual Studio 2013 to date, today we delivered on our promise of enabling developers to create universal Windows apps for Windows 8.1 and Windows Phone 8.1 from one single project in Visual Studio.
We are sharing an early preview of the next version of ASP.NET vNext, a streamlined framework and runtime that is optimized for cloud and server workloads. It allows ASP.NET developers to leverage their existing skills and create applications with automatic cloud support built-in. These components of ASP.NET will be part of the .NET Foundation as an open source project and will run across multiple platforms through a partnership with Xamarin.
We are announcing the public preview of Visual Studio Online APIs. This a set of APIs and service hooks that extends Visual Studio Online and provides integration points to 3rd party services. This makes it easier for organizations to adopt Visual Studio Online without abandoning the tools they’re using today, and for developers to build apps on any platform that can consume Visual Studio Online services.
In addition to the ability for .NET developers to target iOS and Android devices with native-apps through the strategic partnership with Xamarin, we are announcing Visual Studio tooling support for hybrid-apps based on Apache Cordova™ (Multi-Device Hybrid Apps for Visual Studio – CTP). With these tools, web developers can use their existing skills in HTML and JavaScript to create hybrid packaged apps for multiple devices while taking advantage of each device’s capabilities.
We are announcing that virtual machine images for Windows 7 and Windows 8.1 are now available in the Azure virtual machine gallery for MSDN subscribers. This means that you now have the flexibility to utilize an on-demand dev/test environment for client-targeted apps, leveraging the elasticity and scale of Microsoft Azure.
In the next update of Release Management for Visual Studio, customers will be able to directly leverage PowerShell Desired State Configuration (DSC) scripts to configure and manage Windows based environments through Release Management. This extended capability of Release Management will allow customers to manage both on-premises and cloud based infrastructure as part of an application deployment. This capability places Microsoft ahead of Puppet and Chef for configuring and managing both on-premises and cloud based environments as part of an application deployment.
Microsoft has partnered with OpsHub to deliver the OpsHub TFS to Visual Studio Online Migration Utility. This utility is a free offering provided by OpsHub that supports the one-time, one-way migration of on-premises Team Foundation Server data into Visual Studio Online. The goal of the OpsHub TFS to Visual Studio Online Migration Utility is to provide a straightforward migration path from an on-premises Team Foundation Server environment to the Visual Studio Online environment minimizing or eliminating the need for any consulting support.
At TechEd 2014 North America, Microsoft has announced a large set of new innovations for IT Professionals & Enterprise developers to embrace a cloud culture in today’s mobile first, cloud first world. The following is a summary based on Brad Anderson’s keynote on May 5, 2014. I have highlighted my personal favorites.
We are announcing the general availability of the ExpressRoute service. AT&T and Equinix customers are able to use the ExpressRoute service at Silicon Valley, Washington, and London ExpressRoute locations. We are excited to announce a new partnership with TelecityGroup and SingTel which will expand ExpressRoute’s reach in Europe and APAC, and a new partnership with Zadara, which allows Azure customers to use Zadara storage via ExpressRoute in the U.S. ExpressRoute creates private, high-throughput connections between Azure datacenters and your existing infrastructure, whether it’s on-premises or in a colocation environment.
We are announcing the general availability of compute-intensive A8 and A9 instances for virtual machines. These instances provide faster processors, faster interconnectivity, more virtual cores for higher computing power, and larger amounts of memory. With these instances, customers can run compute-intensive and network-intensive applications such as high-performance cluster applications and applications that use modeling, simulation and analysis, and video encoding.
We are announcing the public preview of Azure Files. This new service enables virtual machines in an Azure datacenter to mount a shared file system using the SMB protocol. These VMs will then be able to access the file system using standard Windows file APIs (CreateFile, ReadFile, WriteFile, etc.). Many VMs (or platform-as-a-service roles) can attach to these file systems concurrently, so customers can share persistent data easily between various roles and instances.
We are announcing the general availability of Azure Import/Export service. By using Azure Import/Export, customers can move large amounts of data into and out of Azure Blobs much faster than is possible by downloading data from the internet. Transporting data from hard drives to Azure is easy when using the Microsoft high-speed, security-enabled internal network to transfer the data to our datacenter.
We are announcing the public preview of Microsoft Antimalware and partnerships with Trend Micro and Symantec. For Microsoft Antimalware, we are providing customers the choice on which anti-virus solution to use. One of those solutions is in partnership with Trend Micro. Specifically, deep integration for Trend’s Deep Security™ and SecureCloud™ products in the Azure platform. Additionally, Microsoft is also working to integrate PortalProtect™ with Azure. Another solution we are announcing is in partnership with Symantec. Symantec End Point Protection (SEP) is being supported on Azure. Through deep portal integration, customers have the ability to specify that they intend to use SEP within a VM.
We are announcing the public preview of Internal Load Balancing. This new service provides the ability to load balance Azure virtual machines with private IP addresses. The internally load balanced endpoint will be accessible only within a virtual network (if the VM is within a virtual network) or within a cloud service (if the VM isn’t within a virtual network). Internal Load Balancing is available in the standard tier of VMs at no additional cost.
We are announcing general availability of the two most requested virtual networking features: multiple site-to-site VPN and VNET-to-VNET connectivity. Virtual Network now supports more than one site-to-site VPN connection so customers can securely connect multiple on-premises locations with a virtual network (VNET) in Azure. VNET-to-VNET connectivity enables multiple virtual networks to be directly and securely connected with one another. We are enabling both cross-region VNET-to-VNET and in-region VNET-to-VNET connectivity.
We are announcing the IP Reservation for VIPs and public preview of Instance-level public IPs for virtual machines. For IP reservation, customers can now reserve public IP addresses and use them as virtual IP (VIP) addresses for their applications. This enables scenarios where applications need to have static public IP addresses or where applications need to be updated by swapping the reserved IP addresses. During preview, customers can obtain two public IP addresses per subscription at no additional charge. With Instance-level Public IPs for VMs, customers can now assign public IP addresses to their virtual machines, so they become directly addressable without having to map an endpoint. This feature will enable scenarios like running FTP servers in Azure and monitoring virtual machines directly using their IPs.
We are announcing new capabilities for Azure Hyper-V Recovery Manager that will be in public preview next month. Today, Windows Azure Hyper-V Recovery Manager provides a disaster recovery solution for customers which helps protect the availability of System Center private clouds. In June a public preview of new features will enable customers to replicate virtual machines from their primary site directly to Azure, instead of a second customer site. To better reflect the service’s new, broader capabilities we will be renaming it Microsoft Azure Site Recovery in conjunction with the release of this preview. Updated resources, including an Academy Live, will be available in June at time of public preview.
We are announcing the public preview of Azure RemoteApp: a new service delivering remote applications from the Azure cloud. With Azure RemoteApp, business applications run on Windows Server in the Azure cloud where they’re easier to scale and update. Employees install Microsoft Remote Desktop clients on their Internet-connected laptop, tablet, or phone—and can then access applications as if they were running locally.
Azure RemoteApp helps IT:
Azure RemoteApp is available at no additional cost during the preview period. For detailed information, please refer to the following resources:
We have announced the public preview of more enhancements and capabilities in Azure Active Directory Premium. The public preview of these additional enhancements to the service include a new version of the DirSync tool, a new synchronization engine (Azure AD Sync), and Multi-Factor Authentication IP whitelisting allowing companies to specify IP addresses from which MFA is not required. We also announced the public preview of Azure AD Cloud App Discovery feature that provides IT departments with visibility into all the cloud apps used within their organization.
Future investments for Windows Intune are in the areas of managed productivity, including the ability to apply data management and protection policies to an upcoming release of Office mobile apps, and corporate-owned mobile device management.
We are announcing the public preview of Azure API Management. This new service enables organizations to publish APIs to developers, partners and employees securely and at scale. Organizations can use API Management to monetize its core product, transform its product into a platform and create new content distribution channels.
First, Azure Managed Cache service is moving from public preview to general availability. Second, Azure Redis Cache service is available in public preview. Azure Redis Cache is based on the popular open source Redis Cache. A cache created using Redis Cache is accessible from any application within Azure. And, lastly, as previously announced, Azure Shared Caching Service will be retired in September 2014 and with it the Microsoft’s Silverlight-based portal. Because the Azure Cache Service is in general availability, we strongly encourage customers to migrate all existing caches on Shared Caching to the new Azure Managed Cache Service.
We are announcing the general availability of Azure Traffic Manager, which supports both Azure endpoints and external endpoints. Traffic Manager enables customers to control the distribution of user traffic to specified endpoints. With support for endpoints that can reside outside of Azure, customers can now build highly available applications across Azure and on-premises. In addition, intelligent traffic management policies can be applied across all managed endpoints.
We are announcing the public preview of BizTalk Hybrid Connections. This new Azure service enables cloud services to more securely, quickly, and easily integrate Azure cloud solutions with on-premises applications. With no custom code required, Hybrid Connections enables customers to connect to any on-premises TCP or HTTP resource—such as Microsoft SQL Server, MySQL, or any web service—from Azure Web Sites.
We are announcing the release of BizTalk Server 2013 R2. For over a decade, Microsoft customers and partners have deployed thousands of mission-critical integration solutions using BizTalk. This release enables customers to upgrade now with confidence by delivering improvements in performance, reliability, and functionality. Biz Talk Server 2013 R2 allows customers to take advantage of the latest integration platform capabilities from Microsoft and accelerate solutions for vertical industries including healthcare and financial services.
We are announcing the RTM of Visual Studio 2013 Update 2. With over 5 Million downloads of Visual Studio 2013 to date, today we delivered on our promise of enabling developers to create universal Windows apps for Windows 8.1 and Windows Phone 8.1 from one single project in Visual Studio.
We are sharing an early preview of the next version of ASP.NET vNext, a streamlined framework and runtime that is optimized for cloud and server workloads. It allows ASP.NET developers to leverage their existing skills and create applications with automatic cloud support built-in. These components of ASP.NET will be part of the .NET Foundation as an open source project and will run across multiple platforms through a partnership with Xamarin.
We are announcing the public preview of Visual Studio Online APIs. This a set of APIs and service hooks that extends Visual Studio Online and provides integration points to 3rd party services. This makes it easier for organizations to adopt Visual Studio Online without abandoning the tools they’re using today, and for developers to build apps on any platform that can consume Visual Studio Online services.
In addition to the ability for .NET developers to target iOS and Android devices with native-apps through the strategic partnership with Xamarin, we are announcing Visual Studio tooling support for hybrid-apps based on Apache Cordova™ (Multi-Device Hybrid Apps for Visual Studio – CTP). With these tools, web developers can use their existing skills in HTML and JavaScript to create hybrid packaged apps for multiple devices while taking advantage of each device’s capabilities.
We are announcing that virtual machine images for Windows 7 and Windows 8.1 are now available in the Azure virtual machine gallery for MSDN subscribers. This means that you now have the flexibility to utilize an on-demand dev/test environment for client-targeted apps, leveraging the elasticity and scale of Microsoft Azure.
In the next update of Release Management for Visual Studio, customers will be able to directly leverage PowerShell Desired State Configuration (DSC) scripts to configure and manage Windows based environments through Release Management. This extended capability of Release Management will allow customers to manage both on-premises and cloud based infrastructure as part of an application deployment. This capability places Microsoft ahead of Puppet and Chef for configuring and managing both on-premises and cloud based environments as part of an application deployment.
Microsoft has partnered with OpsHub to deliver the OpsHub TFS to Visual Studio Online Migration Utility. This utility is a free offering provided by OpsHub that supports the one-time, one-way migration of on-premises Team Foundation Server data into Visual Studio Online. The goal of the OpsHub TFS to Visual Studio Online Migration Utility is to provide a straightforward migration path from an on-premises Team Foundation Server environment to the Visual Studio Online environment minimizing or eliminating the need for any consulting support.
At this year’s TechEd, Microsoft will announce and demo many remarkable new capabilities and functionalities to be delivered to the IT and developer industry. If not able to attend TechEd 2014 in person, you can join us online via Tech Ed Live Streaming all week long including the keynotes and technical breakout sessions.
In this article, I’ve included the schedule for this week’s TechEd sessions that will be live streamed and the registration link you can use for joining us online. Hope to see you there virtually!
We have a full week planned of great technical content via the TechEd 2014 Live Stream sessions. Be sure to tune in for these topics …
| Day | Time | Session Title | Primary Speaker |
| 5/12/2014 | 09:00AM – 10:30AM Central Time | Tech Ed 2014 Keynote Session | Brad Anderson, Corporate Vice President, Windows Server and System Center |
| 5/12/2014 | 11:00AM – Noon Central Time | Enabling Enterprise Mobility with Windows Intune, Microsoft Azure, and Windows Server | Adam Hall; Andrew Conway; Demi Albuz; Jason Leznek |
| 5/12/2014 | 01:15PM – 02:30PM Central Time | Windows PowerShell Unplugged with Jeffrey Snover | Jeffrey Snover |
| 5/12/2014 | 03:00PM – 04:15PM Central Time | RemoteApp for Mobility and BYOD | Demi Albuz;Samim Erdogan |
| 5/12/2014 | 04:45PM – 06:00PM Central Time | Microsoft System Center 2012 Configuration Manager: MVP Experts Panel | Greg Ramsey;Jason Sandys;Johan Arwidmark;Kent Agerlund;Steve Thompson |
| 5/13/2014 | 08:30PM – 09:45AM Central Time | INTRODUCING: The Future of .NET on the Server | Scott Hanselman;Scott Hunter |
| 5/13/2014 | 10:15AM – 11:30AM Central Time | DEEP DIVE: The Future of .NET on the Server | David Fowler;Scott Hanselman |
| 5/13/2014 | 01:30PM – 02:45PM Central Time | Group Policy: Notes from the Field – Tips, Tricks, and Troubleshooting | Jeremy Moskowitz |
| 5/13/2014 | 03:15PM – 04:30PM Central Time | Microsoft Desktop Virtualization Overview Session | Demi Albuz;Robin Brandl;Thomas Willingham |
| 5/13/2014 | 05:00PM – 06:15PM Central Time | TWC: Sysinternals Primer: TechEd 2014 Edition | Aaron Margosis |
| 5/14/2014 | 08:30AM – 09:45AM Central Time | Making Sense of the Microsoft Information Protection Stack | Chris Hallum |
| 5/14/2014 | 10:15AM – 11:30AM Central Time | Mark Russinovich and Mark Minasi on Cloud Computing | Mark Minasi;Mark Russinovich |
| 5/14/2014 | 01:30PM – 02:45PM Central Time | Entity Framework: Building Applications with Entity Framework 6 | Rowan Miller |
| 5/14/2014 | 03:15PM – 04:30PM Central Time | Windows PowerShell Best Practices and Patterns: Time to Get Serious | Don Jones |
| 5/14/2014 | 05:00PM – 06:15PM Central Time | What’s New in Windows Server 2012 R2 Hyper-V | Jeff Woolsey |
| 5/15/2014 | 08:30AM – 09:45AM Central Time | Real-World Windows 8.1 Deployment: Notes from the Field | Johan Arwidmark |
| 5/15/2014 | 10:15AM – 11:30AM Central Time | Async Best Practices for C# and Visual Basic | Mads Torgersen |
| 5/15/2014 | 01:00PM – 02:15PM Central Time | VDI Deployment Walkthrough | John Kelbley;Rich McBrine;Robin Brandl |
| 5/15/2014 | 02:45PM – 04:00PM Central Time | 2014 Edition: How Many Coffees Can You Drink While Your PC Starts? | Matthew Reynolds |
Use the link below to register for the TechEd Live Stream to watch the sessions online this week – live from Houston TX.
Which of the announcements, new features or enhancements are you most excited to begin leveraging in your IT organization? Let us know your thoughts in the Comments area below! In addition, be sure to follow us online via the #MSTechEd hashtag on Twitter.
In Microsoft Azure, an administrator can now use PowerShell to migrate a VM from one subnet to another within the same virtual network. This offers an opportunity to reorganize an application topology for better managing subnet capacity and grouping. For instance, when an existing subnet, ABC, is running out of IP addresses, customers can move the associated VMs to a different and perhaps larger subnet. At this time, subnet ABC can then be deleted to recover the IP address space.
The logical process to carry out a subnet migration is to:
The MSDN documentation at http://msdn.microsoft.com/en-us/library/azure/dn643636.aspx offers a sample PowerShell statement as below.
Get-AzureVM –Name <a target VM name> –ServiceName <the associated service name> `
| Set-AzureSubnet –SubnetNames <a target subnet to migrate to> `
| Update-AzureVM
And I am here providing a sample scenario of moving a VM from a DEV subnet to a TEST one as illustrated below.
 |
A virtual network, fooNet, has three subnets: AD, DEV, and TEST, while each subnet is configured with a specific IP address range as shown. |
 |
The intent is to move the VM, app1, currently in DEV to the subnet, TEST. |
 |
The VM, app1, is deployed to the service, foo-devtest, i.e. http://foo-devtest.cloudapp.net. |
 |
An ISE session is connecting to the Microsoft Azure subscription account and has successfully moved the VM to the target subnet, TEST.For those who are not familiar with Microsoft Azure PowerShell, a self-training tool called Quick Start Kit (QSK) is available at https://yungchou.wordpress.com/2014/01/21/announcing-windows-azure-iaas-quick-start-kit-qsk-at-http-aka-ms-qsk/. |
 |
The VM now resides in the subnet, TEST. |
There are a number of changes made recently in the process of creating a Microsoft Azure VM. This article presents a sample user experience of creating a VM from Microsoft Azure image gallery and with the quick create method, as of Aril of 2014, after a user has logged into Microsoft Azure Management Portal with a subscription account.
To acquire a Microsoft Azure free trial subscription while it is available, go to http://aka.ms/R2 and click the dropdown list and select the option, Windows Server 2012 R2 on Windows Azure. Detailed instructions are available at http://aka.ms/30.
 |
This is to interactively deploy a Microsoft Azure VM. Using Microsoft Azure PowerShell, we can automate the entire process. Microsoft Azure Quick Start Kit (QSK) has a sample script. |
 |
When creating a VM which is associated with a storage account, a cloud service, or a virtual network, must use FROM GALLERY option. |
 |
There are two tiers i.e. BASIC and STANDARD, of hardware configuration of a VM, and each with a set of selected compute configurations available as show below. |
 |
|
 |
As of April of 2014, the Basic tier has a set of compute configurations from A0 to A4, while Standard is from A0 to A7. There are deployment constraints associated a Basic compute configuration. For instance, deploying a VM with a Basic tier configuration to a virtual network will error out with the following message, |
 |
Notice the endpoint configurations are by default with two preconfigured: one for RDP connections and the other for PowerShell remoting. |
 |
There are 3rd-party extensions now available. These extensions which provides additional functionality to a VM instance can be installed, managed, and uninstalled from a VM, as needed. |
 |
Upon a successful deployment, the VM becomes available. |
 |
In this example, the VM is deployed to a virtual network with the IP address, 10.0.0.4. The article provides additional information on the IP address management in Microsoft Azure virtual network. |
QUICK CREATE method is for deploying a VM without concerning the associated artifacts including a cloud service name, a storage account, and a virtual network. This is a speedy way to deploy a VM for testing, troubleshooting, and training.
 |
QUICK CREATE requires just 7 pieces of information to deploy a VM. A cloud service name is to be created based on the DNS name, a storage account is to be created for current subscription account, and a VIP and a DIP are to be automatically assigned and managed by Microsoft Azure. In this example, the VM is to be deployed with a Basic tier A1 with an Affinity Group which is not associated with a virtual network. |
 |
If to deploy a VM with a Basic tier configuration with an Affinity Group which is associated with a virtual network, it will error out with the following message, |
 |
In this example, the VM is to be deployed with a Standard tier A1 with an Affinity Group which is associated with a virtual network. |
 |
This two-part series details the IP address management of Windows Azure Infrastructure Services including:
We can use Windows Azure PowerShell to assign a static IP to a VM deployed to a Windows Azure virtual network (VNET). The following explains.
To assign a static IP to a VM, use PowerShell. And the VM must be deployed to a VNET. Windows Azure PowerShell v0.7.3.1 released on March 11, 2014 supports static VNET IP address. To install Windows Azure PowerShell and connect to your Windows Azure subscription, follow the instruction at http://aka.ms/AzureCmdlets.
In PowerShell ISE Command Add-On pane, simply search the string, azurestat, you will find out there are four Windows Azure PowerShell cmdlets associated with managing a static IP of a VM deployed to a Windows Azure virtual network, as shown on the left.
A typical routine starts with using Test-AzureStaticVnetIP to confirm the availability of a target IP address. The cmdlet returns a list of suggestions if the target IP address is not available.
Once the availability of a target IP address is confirmed, run Set-AzureStaticVNetIP and Get-AzureStaticVnetIP to assign and verify the IP assignment of a target VM. And as needed, use Remove-AzureStaticVnetIP to remove a static IP from a VM object.
With a static internal IP addresses, VMs in a VNET will maintain the same IP addresses across shutdown, reboot, and re-imaging. And the deployment order of VMs to a VNET does not impact the IP assignments anymore. Supposed two VMs were at the state, Stopped Deallocated, and then later get started again in a random order. The new internal IP addresses will likely be different. However if the two VMs were assigned with static IP addresses, the same IP address will be in the VM upon restart.
The following user experience is based on Windows Azure PowerShell already configured with connectivity to a Windows Azure subscription by following the instructions provided at http://aka.ms/AzureCmdlets.
Three VMs, vm1, vm2, and vm3 were deployed in order to myTestNet which is configured with 10.0.0.0 address space. Upon the initial deployment, 10.0.0.4, 10.0.0.5, and 10.0.0.6 are assigned to the three VMs as shown. VM2 is the target VM for a static IP assignment.
For this particular deployment, it is obvious which IP addresses are available. In an event that Windows Azure Management Portal is not accessible, we can use Test-AzureStaticVnetIP to confirm the availability of a target IP address within a VNET.
Once a target IP address is confirmed available, we can use Set-AzureStaticVnetIP to assign a static IP to a target VM. Here, on the left I use a small routine to first test the availability of a target IP, 10.0.0.9, in an intended VNET. If the IP is available, assign it to a target VM, here vm2. A sample script is available at http://aka.ms/StaticVnetIPSample.
Now vm2 has an IP address as 10.0.0.9. If this is a static IP address, redeploying all three VMs will not change the IP address of vm2 at this time.
To redeploy the three VMs, I first shut down them from Windows Azure Management Portal and brought all to the state, Stopped (Deallocated), which released the internal IP address of each VM. As shown on the left, neither VM had an IP address.
The three VMs were at this time started in the order of vm3, vm1, and vm2. This order is different from that of the initial deployment. And upon the deployment, notice that vm3 which was first started got the IP address, 10.0.0.4. The 2nd started VM was vm1 which got 10.0.0.5. Nevertheless, the last one started, vm2 (instead of getting the next IP address, 10.0.0.6) maintained the assigned static IP, 10.0.0.9. In other words, once a static IP address is assigned to a VM instance, the deployment order no longer impact the IP address assignment of the VM.
The recommended usage pattern is to employ separate subnets for static IP address VMs and dynamic IP address VMs. Use a static IP address subnet for all static IP address VMs, while it is needed to specify a different static IP address for each VM deployed to this subnet. And use a dynamic IP address subnet for PaaS web/worker roles and those Infrastructure Services VMs without the needs for static IP addresses.
Managing VMs with static IP assignments in a separate subnet can help standardize the processes and configurations, hence better automation and streamlined operations.
