You are on page 1of 75

Microsoft Dynamics AX

LCS: Develop Phase: Cloud Hosted Environments


Last Updated: August 2015
AX 2012 R3 / Version 2.1.0
Yuthana Arngmaneekul

Table of Contents
Introduction ...............................................................................................................................................................................................5
LCS: Develop Phase: Cloud-Hosted Environments .........................................................................................................................5
Cloud-hosted environments (Lifecycle Services, LCS) [AX 2012] .......................................................................................... 5
Deploy Microsoft Dynamics AX 2012 R3 on Azure using Lifecycle Services [AX 2012] ................................................. 5
What is Azure? ..................................................................................................................................................................................... 6
The Azure services model................................................................................................................................................................. 7
Architecture of AX 2012 R3 on Azure ........................................................................................................................................... 8
The process for deploying AX 2012 R3 on Azure .................................................................................................................... 11
Plan your Microsoft Dynamics AX 2012 R3 deployment on Azure [AX 2012] ................................................................ 13
Verify that you can log on to Lifecycle Services....................................................................................................................... 14
Purchase an Azure subscription.................................................................................................................................................... 14
Purchase an Azure support plan .................................................................................................................................................. 15
Become familiar with the Azure management portal ............................................................................................................ 16
Become familiar with the Azure VM Agent ............................................................................................................................... 16
Consider Cloud Services resource requirements ..................................................................................................................... 17
Plan for storage accounts ............................................................................................................................................................... 17
Plan your SQL Server configuration ............................................................................................................................................ 17
Estimate costs and understand the Azure billing process .................................................................................................... 20
Consider legal and regulatory requirements ............................................................................................................................ 20
Consider licensing requirements .................................................................................................................................................. 21
Select the AX 2012 R3 environment that you want to deploy ............................................................................................ 23
AX 2012 R3 and AX 2012 R3 CU8 demo environments .................................................................................................... 23
Retail essentials demo environment ....................................................................................................................................... 26
Development environments ...................................................................................................................................................... 27
Test environment.......................................................................................................................................................................... 28
Retail essentials dev/test environment .................................................................................................................................. 31
Retail e-commerce dev/test environment............................................................................................................................. 33
Retail mobility dev/test environment ..................................................................................................................................... 33
High availability environment ................................................................................................................................................... 34

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Deploy an AX 2012 R3 or AX 2012 R3 CU8 demo environment on Azure [AX 2012]................................................... 40


Deploy a Retail essentials demo environment on Azure [AX 2012]................................................................................... 40
Deploy a test environment on Azure [AX 2012] ...................................................................................................................... 40
Deploy a Retail essentials dev/test environment on Azure [AX 2012] .............................................................................. 40
Deploy a Retail e-commerce dev/test environment on Azure [AX 2012] ........................................................................ 40
Deploy a Retail mobility dev/test environment on Azure [AX 2012] ................................................................................. 40
Deploy a high availability environment on Azure [AX 2012] ............................................................................................... 40
Deploy a development environment on Azure [AX 2012] .................................................................................................... 40
Prerequisites....................................................................................................................................................................................... 41
1. Log on to Lifecycle Services ...................................................................................................................................................... 41
2. Create a project............................................................................................................................................................................. 41
3. Connect the project to your Azure subscription ................................................................................................................. 41
4. Connect your corporate network to the Azure virtual network...................................................................................... 43
Create a site-to-site VPN connection ..................................................................................................................................... 43
Create an Active Directory in Azure ........................................................................................................................................ 43
Create a domain trust.................................................................................................................................................................. 45
Give the Administrators group the right to log on as a batch job................................................................................. 45
Change the default organizational unit ................................................................................................................................. 45
5. Deploy a development environment on Azure ................................................................................................................... 45
6. Prepare AX 2012 R3 for use ...................................................................................................................................................... 48
Log on to the AOS virtual machine ......................................................................................................................................... 48
Compile AX 2012 R3 .................................................................................................................................................................... 48
Initialize AX 2012 R3 .................................................................................................................................................................... 48
Install sample data ....................................................................................................................................................................... 49
Give users access .......................................................................................................................................................................... 49
Set up and configure AX 2012 R3............................................................................................................................................ 50
7. Learn more about the service accounts for this environment ........................................................................................ 51
Domain accounts .......................................................................................................................................................................... 51
Local administrator accounts .................................................................................................................................................... 53
Conclusion ............................................................................................................................................................................................... 74

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Glossary and Additional Background Content ............................................................................................................................. 74


Disclaimer ................................................................................................................................................................................................ 75

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Version
1.0
2.0
2.1

Description
Initial version (Winston Hait)
Additional information and updated document with July update (Yuthana Arngmaneekul)
Additional information and updated document with August update (Yuthana)

Date
June 2014
July 2015
August 2015

[https://technet.microsoft.com/en-us/library/dn268616.aspx]

Introduction
LCS: Develop Phase: Cloud-Hosted Environments

Develop Phase Cloud-Hosted Environments


LCS is a cloud-based, continuously updated set of services that helps you achieve repeatable and predictable
success with your Microsoft Dynamics AX 2012 R2 and later implementations. This demo will highlight the
features and functionality of cloud-hosted environments.
For more details about cloud-hosted environments, click here.
Cloud-hosted environments (Lifecycle Services, LCS) [AX 2012]

Updated: September 12, 2014


Applies To: Microsoft Dynamics AX 2012 R3
In Microsoft Dynamics Lifecycle Services, Cloud-hosted environments is a tool that you can use to deploy
Microsoft Dynamics AX 2012 R3 environments on Microsoft Azure.
When you use the Cloud-hosted environments tool, youll need to select the type of Microsoft Dynamics AX
environment that you want to deploy, such as a demo or developer/test environment. Based on your selection,
the Cloud-hosted environments tool provisions the appropriate number of virtual machines in Azure. These
virtual machines have Microsoft Dynamics AX components (and all of their prerequisites) already installed on
them.
Deploy Microsoft Dynamics AX 2012 R3 on Azure using Lifecycle Services [AX 2012]

Updated: April 20, 2015


Applies To: Microsoft Dynamics AX 2012 R3
Microsoft Dynamics AX 2012 R3 can be deployed on Microsoft Azure virtual machines. This article
introduces you to Azure and explains how to deploy AX 2012 R3 environments on Azure by using the Cloud-

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

hosted environments tool in Microsoft Dynamics Lifecycle Services.

Azure overview (article)


Azure diagram (poster)
What is Azure?
The Azure services model
Architecture of AX 2012 R3 on Azure
The process for deploying AX 2012 R3 on
Azure

Azure pricing (pricing calculator)


Azure videos channel (videos)
Lifecycle Services for Microsoft Dynamics User
Guide (LCS) (article)
Lifecycle Services (blog)
Microsoft server software support for Windows
Azure virtual machines (article)

What is Azure?

Azure is an open and flexible cloud platform that enables you to quickly build, deploy, and manage
applications across a global network of datacenters that are managed by Microsoft.
Azure enables cloud computing. Cloud computing is the delivery of computing capabilities as a service. Cloud
computing makes it easy to access IT resources such as computers, networking, and storage. As with any
utility, you generally only pay for what you use with cloud computing. By using cloud services, you can
harness the power of massive datacenters without having to build, manage, or maintain costly, complex IT
building blocks. With the cloud, much of the complexity of IT is abstracted away, letting you focus on the
infrastructure, data, and application development that really matter to your business.
You can deploy AX 2012 R3 on Azure. When you do, you may realize the following benefits:

Reduce costs
Since you dont have to build out or manage infrastructure with Azure, IT costs may be greatly
reduced.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Save time
An on-premises AX 2012 R3 environment may take weeks to plan, acquire necessary hardware, and
deploy. By using the Cloud-hosted environments tool in Lifecycle Services, you can deploy an AX
2012 R3 environment on Azure in hours.

Gain flexibility
The cloud enables you to easily scale up (or scale down) to meet the changing needs of your business.

The Azure services model

Azure offers three types of services: Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and
Infrastructure-as-a-Service (IaaS).
Type of service
Software-as-aService (SaaS)

Use to

Description
You use a web browser to use applications that are hosted in the
Consume
cloud.

Platform-as-aService (PaaS)

Build

Infrastructure-asa-Service (IaaS)

Host

You dont manage or control the network servers or operating


system. PaaS is more developer-oriented. It allows you to focus
on the business logic of applications and quickly move
applications from concept to launch.
You have control over your virtual machines and the network
configuration, but you dont have to worry about hardware.

When you deploy AX 2012 R3 on Azure, you will be using the IaaS offering. This means that Azure provides
the virtual machines, storage, and networking capabilities. You must manage and secure the operating systems,
applications, and data installed on the virtual machines.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Architecture of AX 2012 R3 on Azure

To deploy AX 2012 R3 on Azure, you can use Microsoft Dynamics Lifecycle Services. Lifecycle Services is a
cloud-based collaborative workspace that customers and partners can use to manage Microsoft Dynamics AX
projects. The Cloud-hosted environments tool, available on the Lifecycle Services website, helps you deploy
AX 2012 R3 environments on Azure.
When you use the Cloud-hosted environments tool to deploy, youll need to select the type of environment that
you want to deploy on Azure, such as a demo or development/test environment. Based on your selection, the
Cloud-hosted environments tool provisions the appropriate number of virtual machines on Azure. These virtual
machines have AX 2012 R3 componentsand all of their prerequisitesalready installed on them.
For example, if you deploy an AX 2012 R3 test environment, the architecture looks like this:

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

You can deploy the following types of AX 2012 R3 environments on Azure with the Cloud-hosted
environments tool:
Type of
environment

Environment

Description
Deploy this environment to demo AX 2012 R3.

This environment includes 1 virtual machine. This virtual


machine has Windows Serverand the software and
sample data that youll need to demo AX 2012 R3
already installed on it.
Deploy this environment to demo AX 2012 R3 Cumulative
AX 2012 R3 CU8
Update 8.
demo
AX 2012 R3 demo

Demo

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

This environment includes 1 virtual machine. This virtual


machine has Windows Serverand the software and
sample data that youll need to demo AX 2012 R3 CU8
already installed on it.
Deploy this environment to demo Retail essentials for AX
2012 R3.
Retail essentials
demo

Development

Dev/test

This environment includes 1 virtual machine, by default.


This virtual machine has Windows Serverand the
software and sample data that youll need to demo Retail
essentialsalready installed on it.
Deploy this environment to develop features for AX 2012
R3.
This environment includes 2 virtual machines, by default.
These virtual machines have Windows Serverand the
software that youll need for AX 2012 R3 development
purposesalready installed on them.
Deploy this environment to develop features for AX 2012
R3. The database for each development VM instance will
be deployed to a shared SQL Server instance.

Development with
shared SQL Server This environment includes 3 virtual machines, by default.
These virtual machines have Windows Serverand the
software that youll need for AX 2012 R3 development
purposesalready installed on them.
Deploy this environment to test features for AX 2012 R3.
Test

Retail essentials
dev/test

10

This environment includes 4 virtual machines, by default.


These virtual machines have Windows Serverand the
software that youll need for AX 2012 R3 testing
purposesalready installed on them.
Deploy this environment to develop or test features for
Retail essentials for AX 2012 R3.
This environment includes 1 virtual machine, by default.
This virtual machine has Windows Serverand the
software that youll need for Retail essentials development
and testing purposesalready installed on it.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Deploy this environment to create and test an online sales


channel that is fully integrated with AX 2012 R3.
Retail e-commerce
This environment includes 1 virtual machine, by default.
dev/test
This virtual machine has Windows Serverand the
software that youll need for Retail e-commercealready
installed on it.
Deploy this environment to enable your sales staff to
process sales transactions, enter customer orders, and
perform daily operations and inventory management with
mobile devices anywhere in a store.
Retail mobility
dev/test
This environment includes 1 virtual machine, by default.
This virtual machine has Windows Serverand the
software that youll need for Retail mobilityalready
installed on it.
Deploy this environment to use AX 2012 R3 in an
environment that can be configured for high availability.

High
availability

High availability

This environment includes 14 virtual machines, by default.


These virtual machines have Windows Serverand the
software that youll need to use AX 2012 R3already
installed on them.
Note

When you deploy this environment, the AX 2012 R3 CU8


version of this environment is deployed by default. If you
want to deploy the AX 2012 R3 RTM version, you can
select that version during deployment.
For more information about the virtual machines, and the software installed on each virtual machine in these
environments, see Plan your Microsoft Dynamics AX 2012 R3 deployment on Azure.
The process for deploying AX 2012 R3 on Azure

The process for deploying AX 2012 R3 on Azure is complex and should be completed by system
implementers who have experience with:

11

Licensing requirements

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Youll need to provide license information for the software included in the AX 2012 R3 environment.
This documentation will point you to resources to help you complete this task, but will not provide a
step-by-step procedure for completing this task.

Networks and domains


To enable users in your corporate network to easily access the virtual machines on Azure, youll need
to create a site-to-site VPN connection. This documentation will point you to resources to help you
create the VPN connection, but will not provide a step-by-step procedure for completing this task.

To deploy AX 2012 R3 on Azure, see the TechNet articles that are listed in the following table.
Task

Plan your
deployment

More information
Before you can deploy AX 2012 R3 on Azure, there are
several things you must consider and decisions you must
make. For example, you must consider licensing
requirements, purchase an Azure subscription, and select the
type of AX 2012 R3 environment that you will deploy on
Azure.
For more information, see Plan your Microsoft Dynamics AX
2012 R3 deployment on Azure.
Microsoft Dynamics Lifecycle Services is a cloud-based
collaborative workspace that customers and partners can use
to manage Microsoft Dynamics AX projects. Youll use the
Cloud-hosted environments tool in Lifecycle Services to
deploy AX 2012 R3 on Azure.
To deploy a demo environment, see:

Deploy AX 2012
R3 on Azure

Deploy an AX 2012 R3 or AX 2012 R3 CU8 demo


environment on Azure
Deploy a Retail essentials demo environment on
Azure

To deploy a dev/test environment, see:

12

Deploy a development environment on Azure


Deploy a test environment on Azure
Deploy a Retail essentials dev/test environment on
Azure

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Deploy a Retail e-commerce dev/test environment on


Azure
Deploy a Retail mobility dev/test environment on
Azure

To deploy an environment that can be configured for high


availability, see:

Deploy a high availability environment on Azure

Manage your AX
To help you manage your AX 2012 R3 environment on
2012 R3
Azure, see the tips and tricks in Manage your Microsoft
environment on
Dynamics AX 2012 R3 deployment on Azure.
Azure

Troubleshoot
issues that may
occur

If you need to contact Microsoft with licensing questions or


technical issues, you must first determine which support team
to contact: the Azure support team or the Microsoft Dynamics
AX support team. For information about when and how to
contact each support team, see Troubleshoot your Microsoft
Dynamics AX 2012 R3 deployment on Azure.

Plan your Microsoft Dynamics AX 2012 R3 deployment on Azure [AX 2012]

Updated: June 5, 2015


Applies To: Microsoft Dynamics AX 2012 R3
Before you can deploy Microsoft Dynamics AX 2012 R3 on Microsoft Azure, there are several things you
must consider and decisions you must make. This article guides you through the planning process.

Verify that you can log on to Lifecycle


Services

Deploy Microsoft Dynamics AX 2012 R3 on Azure


using Lifecycle Services (article)

Purchase an Azure subscription


Lifecycle Services (blog)
Purchase an Azure support plan

13

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Become familiar with the Azure


management portal
Become familiar with the Azure VM
Agent

My personal Azure FAQ on Azure Networking


SLAs, bandwidth, latency, performance, SLB, DNS,
DMZ, VNET, IPv6 and much more (blog post)
Guidelines for deploying Windows Server Active
Directory on Azure virtual machines (article)

Consider Cloud Services resource


requirements
Plan for storage accounts
Plan your SQL Server configuration
Estimate costs and understand the Azure
billing process
Consider legal and regulatory
requirements
Consider licensing requirements
Select the AX 2012 R3 environment that
you want to deploy
Next steps
Verify that you can log on to Lifecycle Services

Microsoft Dynamics Lifecycle Services is a cloud-based collaborative workspace that customers and partners
can use to manage Microsoft Dynamics AX projects. Youll use the Cloud-hosted environments tool, available
on the Lifecycle Services website, to deploy AX 2012 R3 on Azure.
Lifecycle Services is available to customers and partners as part of their support plans. You can access it with
your CustomerSource or PartnerSource credentials.
Verify that you can log on to Lifecycle Services
Purchase an Azure subscription

To use Azure, you must purchase a subscription. For information about subscription plans and pricing details,
see the Azure pricing page. Then follow the instructions on that page to purchase a subscription.

14

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

The subscription must be large enough to support the AX 2012 R3 environment that you want to deploy on
Azure. The following table lists the types of AX 2012 R3 environments that you can deploy on Azure, and the
number of cores required to deploy each environment in its default configuration
Note

Keep in mind that when you deploy an environment, you can change the number and size of the
virtual machines that are deployed. However, this table lists the number of cores required to
deploy each environment in its default configuration.
Type of
Number of cores to deploy the
Environment name
environment
environment in its default configuration
AX 2012 R3 demo
8 cores
Demo
AX 2012 R3 CU8 demo
8 cores

Dev/test

Retail essentials demo


Development
Development with shared
SQL Server
Test

8 cores
9 cores
14 cores
13 cores

Retail essentials dev/test


4 cores
Retail e-commerce dev/test 4 cores
Retail mobility dev/test
4 cores
High availability

High availability
environment

45 cores

If you already have an Azure subscription, note the following:

To view the size of your subscription:


You can view the size of your subscription in the Azure management portal. To do so, log on to the
Azure management portal, and then click Settings > Usage.

To increase the size of your subscription:


To increase the size of your subscription, youll need to create a support ticket with the Azure support
team. To do so, go to the Azure support options page, and then click Get Support to create the support
ticket. When creating the support ticket, be sure to indicate that the ticket is for billing support.

Purchase an Azure support plan

15

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Azure support plans provide technical and billing support for Azure. The Azure support plans offer flexible
support options that will allow you to select the right level of support for your Azure deployment. The support
options range from support services included with your Azure subscription at no charge to premier support
services.
To learn about the available support plans and to purchase a plan, see the Azure support plans page.
Become familiar with the Azure management portal

The Azure management portal provides developers and IT professionals the ability to provision, configure,
monitor, and manage their Azure components. Its important to become familiar with the management portal
because youll use it to:

Upload a management certificate. (The management certificate enables Lifecycle Services to deploy
AX 2012 R3 environments on Azure on your behalf.)
Connect to virtual machines.
Monitor the health and status of your AX 2012 R3 environment.

After you purchase an Azure subscription, you can access the management portal by clicking here. The
following image shows the management portal.

Become familiar with the Azure VM Agent

16

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

The Azure VM Agent is now automatically deployed with every VM deployed via Lifecycle Services. The
Azure VM Agent is used to install, configure, manage and run Azure Virtual Machine Extensions (VM
Extensions). VM extensions can help you monitor and manage your VMs. For more information, click here.
Consider Cloud Services resource requirements

When a topology is deployed, the deployment system will inspect the virtual machine (VM) SKUs that were
selected. In order to ensure that Azure deploys these VMs to the proper clusters where the VMs are available,
each level of VM SKU must have its own Azure Cloud Service. The VM SKU breakdown is as follows:
SKU
Size
A
Standard As [A0-A4]
AM Standard A's [A5-A7]
AL
D
DS

Standard As (large) [A8-A11]


Standard Ds [all D series]
Standard DSs [all DS series]

Standard Gs [all G series]

A Cloud Service will be created with the following naming scheme: Version-Topology-EnvironmentNameSKU-GUID
Please consider the Cloud Services resource requirements for you deployments and request additional Cloud
Services capacity in your Azure Subscription from Azure Support if necessary.
Plan for storage accounts

For each project created in Lifecycle Services, one or more distinct storage accounts will be created in the
Azure subscription. A storage account is created when you connect your project to your Azure subscription.
This storage account is a Locally Redundant Storage (LRS) account, and is used to house scripts and VHDs
which are required for deployments. An additional Premium storage account is created for each project when
the first Premium storage-enabled topology is deployed from the project. Storage accounts are not shared
across Lifecycle Services projects, even if the deployments are to the same Azure subscription. When a
Premium storage account is created, it too is created as LRS. For more information about storage, click here.
Plan your SQL Server configuration

Azure Premium Storage delivers high-performance, low-latency disk support for I/O intensive workloads
running on Azure virtual machines (VMs). With Premium Storage, your applications can have up to 32 TB of
storage per VM, achieve 50,000 IOPS (input/output operations per second) per VM, and have extremely low

17

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

latencies for read operations. Premium Storage is recommended for running AX 2012 R3 in Azure to ensure
predictable performance. Premium Storage is enabled by default for High Availability deployments when
Azure DS-series VMs are selected. Premium Storage is only offered on DS-series VMs at this time. Premium
Storage is enabled exclusively for the SQL Server AlwaysOn database servers, while non-Premium storage is
used for all other storage needs. When a SQL Server AlwaysOn availability set is created, Lifecycle Services
will attach a disk for every disk slot supported by the DS-series VM selected. For more information about VM
disk capacity, click here.
The SQL Server AlwaysOn availability set is created automatically through Lifecycle Services. It is important
to consider your data and performance needs before deploying a High Availability topology for use with a
production system. Please refer to Azure Premium Storage information here.
Once you have planned your deployment with Premium Storage, the High Availability topology provides
configuration options to help you achieve your cost and performance objectives. Under Advanced Settings for
the High Availability topology, the following SQL Server configuration options appear:
Note

These SQL Server configuration options are available in Preview mode.

Customize the SQL Server image configuration This option allows the use of a custom SQL
Server Enterprise image or an Azure Gallery SQL Server Enterprise image.
o Custom SQL Server image (default) This image contains a trial edition of SQL Server
Enterprise 2014. The trial license is enabled for 3-6 months. Use this option if you want to use
an existing EA/etc. license.
o Gallery SQL Server image This image contains SQL Server Enterprise 2014 and uses
consumption-based Azure pricing. More information can be found on the Azure Virtual
Machines Pricing page and the SQL Server in Azure Virtual Machines page.
Customize the SQL Server storage space configuration You can specify the number and size of
the disks that will be attached to the SQL Server VMs.
Keep the following points in mind when specifying the number of disks that should be used to create
the storage space within SQL Server:
o

18

The VM size that is selected for the database server dictates how many disks are supported by
that VM SKU. Information about the number of disks that are supported by each VM can be
found here.
One of the available disk slots on the VM will be used by the Lifecycle Services deployment
service. This means the VMs maximum number of disksminus 1equals the available slots
to fill.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Leaving this setting blank will allow the deployment service to attach disks up to the maximum
supported by the VM. It is recommended for production deployments that the maximum disks
be used.

Keep the following points in mind when specifying the size (in GB) of each disk attached to the VM:
o
o
o
o
o

Allowed values are 100 GB 1024 GB.


Default is 128 GB.
The size of the disk used dictates the Premium Storage tier used.
The Premium Storage tier dictates cost, IOPS per disk, and throughput of the system being
deployed. For more information, click here.
All disks are formatted to 64k cluster size. This results in up to a 20% increase in performance.
For more information, click here.

TempDB and logs are deployed onto storage spaces as to benefit from the performance gains.
One virtual disk is created over the number of disks configured for the storage space. The virtual disk is then
partitioned as follows:

SQL data = 1/2 of the total size of pool


SQL logs = 1/4 of the total size
SQL Temp db = 1/8 of the total size
SQL backup = remaining 1/8 of the total size

Other considerations to keep in mind:

When planning your deployment, ensure that Premium Storage is available in the Azure region you are
targeting. For more information, click here.
If you have a VPN/Express Route connection (or plan to) between your corporate network and Azure,
please ensure this is done for an Azure region that supports Premium Storage.
Consult the Azure Premium Storage documentation to understand limitations of use.
If non-Premium Storage VMs are deployed with the High Availability topologies, all of the above SQL
Server configuration settings are applicable; however, Premium Storage benefits will not apply.
When setting up your Lifecycle Services project for deployment, you must select a region that supports
Premium Storage.

SQL Server best practices implemented by the deployment service include those recommended by the SQL
Server team. For more information, click here. In addition, the following items are done:

19

Multiple temp files (one per CPU core).


Set max memory for SQL Server to 90% of available machine RAM.
Set max degree of parallelism.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Enabled trace flags -T1204, -T1222.

Estimate costs and understand the Azure billing process

To help estimate the cost of your AX 2012 R3 deployment on Azure, use the Azure pricing calculator.
Its also important to understand the Azure billing process before you deploy AX 2012 R3 on Azure. For an
overview of the Azure billing process, links to sample invoices, and information about how to download daily
usage data for the current billing period, see Understand your bill.
Note

Keep in mind, you can shut down an AX 2012 R3 environment that has been deployed on
Azure when its not in use. For example, you may want to shut down an environment on the
weekends to reduce costs. When you shut down an environment, the environment still exists;
however, the virtual machines in the environment are shut down. You wont be charged for the
virtual machines when theyre not running. For more information, see How do I shut down an
environment? in the Manage your Microsoft Dynamics AX 2012 R3 deployment on Azure
article.
Consider legal and regulatory requirements

Microsoft runs Azure services with common operational practices and features across multiple geographies
and jurisdictions. However, it is ultimately up to you to determine if Microsoft services satisfy your regulatory
needs.
To help provide you with up-to-date information, the Azure trust center provides the following information
about security, privacy, and compliance.

Security
The Azure security page provides an overview of the provisions Microsoft is taking to provide a secure
environment within geographically dispersed datacenters. Among the extensive list of security-related
resources, the Standard Response to Request for Information: Security and Privacy white paper outlines
how Azure meets the suggested principals and mapped them to the International Standards
Organization (ISO) 27001:2005 and ISO 27002.

Privacy
The Azure privacy page includes links to multiple resources that describe privacy practices of the
Azure environment. It includes a link to the Azure privacy statement.

20

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Compliance
The Azure compliance page provides resources to help you comply with the specific laws and
regulations applicable to your unique industry and use scenario.

Consider licensing requirements

Licensing the various components of the AX 2012 R3 virtual machine environment is an important
consideration. For deployments on Azure, you will want to evaluate the special licensing terms specific to
Azure and the impact that these terms have on the overall suitability of the solution.
Licensing requirements vary based on the type of AX 2012 R3 virtual machine environment that you deploy
on Azure. The following table provides more information.
Type of
environment

Licensing requirements
The software that is included in the virtual machine environment is timebound and licensed according to the terms in the Software License Terms.

Demo

Software License Terms for the AX 2013 R3 demo environment


Software License Terms for the AX 2013 R3 CU8 demo environment
Software License Terms for the Retail essentials demo environment

All software included in the virtual machine environment must be properly


licensed. Please investigate your licensing needs thoroughly with your partner
and your Microsoft representative. You will need to investigate the terms for
each piece of software that is included in the virtual machine environment. For
the complete list of software that is included in the virtual machine
environment, review the Software License Terms.
Dev/test and
high availability

21

Software License Terms for the development environment


Software License Terms for the development with shared SQL Server
environment
Software License Terms for the test environment
Software License Terms for the Retail essentials dev/test environment
Software License Terms for the Retail e-commerce dev/test
environment
Software License Terms for the Retail mobility dev/test environment
Software License Terms for the high availability environment

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

When reviewing the licensing terms and requirements, you need to pay special
attention to any terms that apply specifically to deploying on Azure, as well as
terms that apply to your intended use. For example, Microsoft Office has
terms that are specific to Azure; but those terms vary depending on whether
you deploy Office for development or test purposes, or whether you deploy
Office for production purposes.
Some resources to help you get started are linked to below. Most of the
resources that are linked to below contain links to in-depth information for
several products and scenarios; however, you may need to review additional
information, as well. This information is provided to help guide your
authorized use of products you license; it is not your agreement. Your use of
products licensed under your volume license agreement is governed by the
terms and conditions of that agreement. In the case of any conflict between
information linked here and your agreement, the terms and conditions of your
agreement control.

Virtual machines licensing FAQ


Common questions regarding licensing on Azure virtual machines are
answered on this page.

Microsoft Product Use Rights and Product List


Learn more about Microsoft Volume Licensing product licensing
models, programs, scenarios, and terms and conditions to help you
make effective business decisions and maximize the value of your IT
purchases on this page.

License Mobility through Software Assurance on Azure program


License Mobility through Software Assurance gives Microsoft volume
licensing customers the flexibility to deploy eligible server
applications with active Software Assurance on Azure. With this
Software Assurance benefit, there is no need to purchase new licenses
and no associated mobility fees. This enables you to easily deploy
existing licenses on the Azure cloud platform. For more information,
see this page. For Development, Test, and High Availability topologies
trial versions of Sharepoint, Visual Studio, SQL Server, and Office are
provided. The trials range from 30-180 days. Please apply licenses
accordingly.

22

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Microsoft Dynamics AX volume licensing buyers guide


For an overview of key licensing options with Microsoft Dynamics
AX, see this page.

Shared computer activation for Office 365 ProPlus


Shared computer activation lets you to deploy Office 365 ProPlus to a
computer in your organization that is accessed by multiple users. For
more information, see this page.

Select the AX 2012 R3 environment that you want to deploy

Youll use the Cloud-hosted environments tool in Lifecycle Services to deploy AX 2012 R3 environments on
Azure.
When you use the Cloud-hosted environments tool to deploy, youll need to select the type of environment that
you want to deploy on Azure, such as a demo or development/test environment. Based on your selection, the
Cloud-hosted environments tool provisions the appropriate number of virtual machines on Azure. These virtual
machines have AX 2012 R3 componentsand all of their prerequisitesalready installed on them.
The following sections describe the AX 2012 R3 environments that you can deploy on Azure.

AX 2012 R3 and AX 2012 R3 CU8 demo environments


Retail essentials demo environment
Development environments
Test environment
Retail essentials dev/test environment
Retail e-commerce dev/test environment
Retail mobility dev/test environment
High availability environment

Note

In these environments, SQL Server is configured to use the SQL_Latin1_General_CP1_CI_AS


collation.
AX 2012 R3 and AX 2012 R3 CU8 demo environments

There are two AX 2012 R3 demo environments: one environment includes Cumulative Update 8, and the other
does not.
The following table lists details about each environment.

23

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Note

The virtual machine included in each environment is a single-instance virtual machine. Singleinstance virtual machines are not covered by an Azure Service Level Agreement.
Number of
virtual
machines
Description Size and name
Software installed
deployed by
default
Windows Server 2012 R2, including:
o Active Directory
o Domain Name Services
(DNS)
o Internet Information Services
(IIS)
o Remote Desktop Services
Microsoft Visual Studio 2013
Microsoft SQL Server 2014
components:
o Database Engine Services
o Reporting Services
o Analysis Services
Size: D3:
o Management Studio
Standard
o Developer tools
compute tier (4
Microsoft SharePoint Server 2013
cores, 14 GB
Demo
Microsoft Office 2013
1
machine
memory)
AX 2012 R3 or AX 2012 R3 CU8
components:
o Databases
Default name:
DEMO-<GUID>
o Server components:
Application Object
Server (AOS)
Web server
components:
Enterprise
Portal (EP)
Enterprise
Search
Help Server
o Business intelligence
components:
Reporting Services
extensions

24

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

o
o

25

Analysis Services
configuration
Management Reporter
components:
Management Reporter
server components
Management Reporter
Report Designer
Client components:
Client
Office add-ins
Remote Desktop
Services integration
Developer tools:
Debugger
Visual Studio Tools
Trace Parser
Integration components:
Web services on IIS
.NET Business
Connector
Management utilities
Retail components:
Retail POS
Retail Headquarters
Commerce Data
Exchange
components:
Synch Service
Real-time
Service
Async Server
Async Client
Retail Channel
Configuration Utility
Retail SDK
Retail online channel
Retail Server
Retail Mass
Deployment Toolkit
Retail channel
database

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

o
o

o
o

RapidStart Connector
Data Import/Export
Framework components:
Data Import/Export
Framework (DIXF)
service
AOS component
Client component
Warehouse Mobile Devices
Portal
Connector for Microsoft
Dynamics

Retail essentials demo environment

Deploy this environment to demo Retail essentials. Retail essentials is a retail-centric configuration option for
Microsoft Dynamics AX.
This environment includes one virtual machine, by default. This virtual machine has Windows Serverand
the software and sample data that youll need to demo Retail essentialsalready installed on it.
The following table lists details about the default Retail essentials demo environment. When you deploy the
environment, you can add additional virtual machines to the environment, or change the size of the virtual
machines.
Note

The virtual machines in this environment are single-instance virtual machines. Single-instance
virtual machines are not covered by an Azure Service Level Agreement.
Number of
virtual
machines
Description
Size and name
Software installed
deployed by
default
Windows Server 2012 R2
Size: D3:
Microsoft SQL Server 2014
Standard compute
components:
Retail
tier (4 cores, 14
o Database Engine Services
1
essentials demo GB memory)
o Management Studio
machine
o Developer tools
Default name:
AX 2012 R3 components:
DEMO-<GUID>
o Databases

26

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

o
o

Server components:
Application Object
Server (AOS)
Client components:
Client
Integration components:
.NET Business
Connector
Retail components:
Retail
Headquarters
Commerce Data
Exchange
components:
Real-time
Service
Async
Server
Async
Client
Retail channel
database

Development environments

Deploy these development environments when you need to quickly jumpstart a development effort for one to
many developers. Deploy a development virtual machine (VM) for each of your developers in a matter of
hours instead of days. With a development environment, you have all the same domain and virtual network
customizations that you have with the Test environment.
Two topology options are provided for developer scenarios:

Development: Includes all-in-one VMs deployed with Active Directory.


Development with shared SQL Server: Includes all-in-one VMs deployed with Active Directory. The
database for each development VM instance will be deployed to a shared SQL Server instance.

For those doing BI development you can deploy one instance for the purpose. All other instances will not
deploy with BI.

27

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

The development VMs provided have all the AX 2012 R3 components installed with Visual Studio 2013 and
AX 2012 R3 development tools. The VMs are joined to the Active Directory domain at deployment time. If
you provided an Active Directory domain as a customization option, then the VMs will join to that domain.
Development VMs will be deployed up to the point of the AX 2012 R3 checklist, and have all the software
installed that is listed in the Test environment.
Note

The virtual machines in this environment are single-instance virtual machines. Single-instance
virtual machines are not covered by an Azure Service Level Agreement.
Test environment

Deploy this environment to test features for AX 2012 R3.


This environment includes several virtual machines, by default. These virtual machines have Windows
Serverand the software that youll need for AX 2012 R3 testing purposesalready installed on them.
The following table lists details about the default test environment. When you deploy the environment, you can
add additional virtual machines to the environment, or change the size of the virtual machines.
Note

The virtual machines in this environment are single-instance virtual machines. Single-instance
virtual machines are not covered by an Azure Service Level Agreement.
Number of
virtual
Size and
machines Description
Software installed
name
deployed
by default
Size: D1:
Basic
compute
tier (1 core,
Windows Server 2012 R2, including:
Domain
3.5 GB
o Active Directory
1
controller
memory)
o Domain Name Services (DNS)

28

AOS server

Default
name: AD<GUID>
Size: D3:
Standard

Windows Server 2012 R2, including:


o Internet Information Services (IIS)

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

compute
tier (4
cores, 14
GB
memory)

Default
name:
AOS<GUID>

Database
server/BI
server

Size: D3:
Standard
compute
tier (4
cores, 14
GB
memory)

Microsoft Visual Studio 2013


Microsoft Project Server
Microsoft SQL Server 2014 components:
o Management Studio
o Native Client
AX 2012 R3 or AX 2012 R3 CU8
components:
o Server components:
Application Object Server
(AOS)
o Client components:
Client
Office add-ins
Remote Desktop Services
integration
o Integration components:
Web services on IIS
.NET Business Connector
o Management utilities
o Retail components:
Retail Headquarters
Commerce Data Exchange
components:
Synch Service
Real-time Service
Async Server
o RapidStart Connector
o Data Import/Export Framework
components:
Data Import/Export Framework
(DIXF) service
AOS component
Windows Server 2012 R2
Microsoft SQL Server 2014 components:
o Database Engine Services
o Reporting Services
o Analysis Services
o Management Studio
Note

29

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Default
name:
SQL<GUID>

Reporting Services is configured to run in


Native mode. To use Power View, youll
need to complete additional configuration
steps. For more information, see the
prerequisites listed in Create a report by using
Power View to connect to a cube.

AX 2012 R3 or AX 2012 R3 CU8


components:
o Databases
o Business intelligence components:
Reporting Services extensions
Analysis Services configuration

Windows Server 2012 R2, including:


o Internet Information Services (IIS)
Microsoft SQL Server 2012 components:
o Full-text Search
Microsoft SharePoint Server 2013
AX 2012 R3 or AX 2012 R3 CU8
components:
o Server components:
Web server components:
Enterprise Portal (EP)
Enterprise Search
Help Server
o Management Reporter components:
Management Reporter server
components
o Retail components:
Commerce Data Exchange
components:
Async Client
Retail Server
Retail Online Channel
Retail Channel Database
Retail Channel Configuration
Utility
Retail Hardware Station
o Warehouse Mobile Devices Portal
o Connector for Microsoft Dynamics

Size: D3:
Standard
compute
tier (4
cores, 14
Enterprise
GB
Portal server
memory)
Default
name: EP<GUID>

30

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Client
computer

Size: D3:
Standard
compute
tier (4
cores, 14
GB
memory)
Default
name: CLI<GUID>

Remote
Desktop
Services
server

Size: D3:
Standard
compute
tier (4
cores, 14
GB
memory)

Windows Server 2012 R2


Microsoft Visual Studio 2013
Microsoft SQL Server 2014 components:
o Developer tools
Microsoft SharePoint Server 2013 Client
Components SDK
Microsoft Office 365 ProPlus
AX 2012 R3 or AX 2012 R3 CU8
components:
o Management Reporter components:
Management Reporter Report
Designer
o Client components:
Client
Office add-ins
Remote Desktop Services
integration
o Developer tools:
Debugger
Visual Studio Tools
Trace Parser
o Management utilities
o Retail components:
Retail POS
o Data Import/Export Framework
components:
Client component

Windows Server 2012 R2, including:


o Internet Information Services (IIS)
o Remote Desktop Services
Microsoft SQL Server 2012 Native Client

Default
name:
RDS<GUID>
Retail essentials dev/test environment

31

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Deploy this environment to develop or test features for Retail essentials.


This environment includes one virtual machine, by default. This virtual machine has Windows Serverand
the software that youll need for Retail essentials development and testing purposesalready installed on it.
The following table lists details about the default Retail essentials dev/test environment. When you deploy the
environment, you can add additional virtual machines to the environment, or change the size of the virtual
machines.
Note

The virtual machines in this environment are single-instance virtual machines. Single-instance
virtual machines are not covered by an Azure Service Level Agreement.
Number of
virtual machines
Description Size and name
Software installed
deployed by
default
Windows Server 2012 R2
Microsoft SQL Server 2014
components:
o Database Engine Services
o Management Studio
o Developer tools
AX 2012 R3 components:
o Databases
Size: D3:
o Server components:
Standard compute
Application Object
Retail
tier (4 cores, 14
Server (AOS)
1
essentials
GB memory)
o Client components:
server
Client
o Integration components:
Default name:
.NET Business
ESSEN-<GUID>
Connector
o Retail components:
Retail Headquarters
Commerce Data
Exchange
components:
Real-time
Service

32

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Async
Server
Async
Client
Retail channel
database

Retail e-commerce dev/test environment

Deploy this environment to create and test an online sales channel that is fully integrated with AX 2012 R3.
This environment includes one virtual machine, by default. This virtual machine has Windows Serverand
the software that youll need for Retail e-commercealready installed on it.
The following table lists details about the default Retail e-commerce dev/test environment. When you deploy
the environment, you can add additional virtual machines to the environment, or change the size of the virtual
machines.
Note

The virtual machines in this environment are single-instance virtual machines. Single-instance
virtual machines are not covered by an Azure Service Level Agreement.
Number of
virtual machines
Description
Size and name
Software installed
deployed by
default
Windows Server 2012 R2
Microsoft SharePoint Server
2013
AX 2012 R3 components:
Size: D3:
o Retail components:
Standard compute
Commerce Data
Retail etier (4 cores, 14
Exchange
1
commerce
GB memory)
components:
server
Async
Default name: EClient
Retail online
COM-<GUID>
channel
Retail channel
database
Retail mobility dev/test environment

33

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Deploy this environment to enable your sales staff to process sales transactions, enter customer orders, and
perform daily operations and inventory management with mobile devices anywhere in a store.
This environment includes one virtual machine, by default. This virtual machine has Windows Serverand
the software that youll need for Retail mobilityalready installed on it.
The following table lists details about the default Retail mobility dev/test environment. When you deploy the
environment, you can add additional virtual machines to the environment, or change the size of the virtual
machines.
Note

The virtual machines in this environment are single-instance virtual machines. Single-instance
virtual machines are not covered by an Azure Service Level Agreement.
Number of
virtual machines
Description
deployed by
default

Size and name

Software installed

Retail
server

Size: D3: Standard


compute tier (4
cores, 14 GB
memory)
Default name:
MOBIL-<GUID>

Windows Server 2012 R2


AX 2012 R3 components:
o Retail components:
Commerce Data
Exchange
components:
Async
Client
Retail Server
Retail channel
database

High availability environment

Deploy this environment to use AX 2012 R3 in an environment that can be configured for high availability.
This environment includes several virtual machines. These virtual machines have Windows Serverand the
software that youll need to use AX 2012 R3already installed on them.
The following table lists details about the default high availability environment. When you deploy the
environment, you can add additional virtual machines to the environment, or change the size of the virtual
machines.

34

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Note

We recommend you use Azure Premium Storage for high availability environments. For more
information, see Deploy a high availability environment on Azure.
Note

The virtual machines in this environment are covered by an Azure Service Level Agreement.
Number of virtual
Size and
machines deployed Description
name
by default
3
Note

Three domain
controllers are
deployed in this
environment. If one Domain
domain controller
controller
fails, you must be
left with two,
online domain
controllers in order
to meet Azures
Service Level
Agreement.

Size: D1:
Basic
compute
tier (1
core, 3.5
GB
memory)

Software installed

Windows Server 2012 R2, including:


o Active Directory
o Domain Name Services (DNS)

Windows Server 2012 R2, including:


o Internet Information Services
(IIS)
Microsoft Visual Studio 2013
Microsoft Project Server
Microsoft SQL Server 2014
components:
o Management Studio
o Native Client
AX 2012 R3 or AX 2012 R3 CU8
components:
o Server components:
Application Object
Server (AOS)
o Client components:
Client

Default
name:
AD<GUID>

Size: D3:
Standard
compute
tier (4
cores, 14
GB
AOS server
memory)

Default
name:
AOS<GUID>

35

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

o
o

o
o

Database
server

Size: D3:
Standard
compute
tier (4
cores, 14
GB
memory)
Default
name:
SQL<GUID>

Windows Server 2012 R2


Microsoft SQL Server 2014
components:
o Database Engine Services
o Management Studio
Note

A Quorum server is also deployed. This


virtual machine is a listener for the
AlwaysOn availability group. This
virtual machine:
o

36

Office add-ins
Remote Desktop Services
integration
Integration components:
Web services on IIS
.NET Business
Connector
Management utilities
Retail components:
Retail Headquarters
Commerce Data
Exchange components:
Synch Service
Real-time Service
Async Server
RapidStart Connector
Data Import/Export Framework
components:
Data Import/Export
Framework (DIXF)
service
AOS component

Is not represented in the High


Availability VM list, but it is
deployed with High Availability
environments.
Is named QRM-<GUID>. This
name cant be customized.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

o
o
o

Is an A2 virtual machine.
Runs a gallery image of
Windows Server 2012 R2.
Post deployment, this VM
appears as a Database Server
when adding VMs to the High
Availability environment. The
3rd VM referenced here is the
A2 Quorum Server which is
explicitly not a SQL Server.

Note

Reporting Services is configured to run


in Native mode. To use Power View,
youll need to complete additional
configuration steps. For more
information, see the prerequisites listed
in Create a report by using Power View
to connect to a cube.

Size: D3:
Standard
compute
tier (4
Business
cores, 14
intelligence GB
(BI) server memory)
Default
name: BI<GUID>

37

AX 2012 R3 or AX 2012 R3 CU8


components:
o Databases

Windows Server 2012 R2


Microsoft SQL Server 2014
components:
o Database Engine Services
o Reporting Services
o Analysis Services
o Management Studio
Note

Reporting Services is configured to run


in Native mode. To use Power View,
youll need to complete additional
configuration steps. For more
information, see the prerequisites listed
in Create a report by using Power View
to connect to a cube.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

AX 2012 R3 or AX 2012 R3 CU8


components:
o Business intelligence
components:
Reporting Services
extensions
Analysis Services
configuration

Windows Server 2012 R2, including:


o Internet Information Services
(IIS)
Microsoft SQL Server 2012
components:
o Full-text Search
Microsoft SharePoint Server 2013
AX 2012 R3 or AX 2012 R3 CU8
components:
o Server components:
Web server components:
Enterprise Portal
(EP)
Enterprise Search
Help Server
o Management Reporter
components:
Management Reporter
server components
o Retail components:
Commerce Data
Exchange components:
Async Client
Retail Server
Retail Online Channel
Retail Channel Database
Retail Channel
Configuration Utility
Retail Hardware Station
o Warehouse Mobile Devices
Portal

Size: D3:
Standard
compute
tier (4
cores, 14
Enterprise
GB
Portal server
memory)
Default
name: EP<GUID>

38

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Client
computer

Size: D3:
Standard
compute
tier (4
cores, 14
GB
memory)
Default
name:
CLI<GUID>

39

Remote
Desktop
Services
server

Size: D3:
Standard
compute
tier (4
cores, 14
GB
memory)

Connector for Microsoft


Dynamics

Windows Server 2012 R2


Microsoft Visual Studio 2013
Microsoft SQL Server 2014
components:
o Developer tools
Microsoft SharePoint Server 2013
Client Components SDK
Microsoft Office 365 ProPlus
AX 2012 R3 or AX 2012 R3 CU8
components:
o Management Reporter
components:
Management Reporter
Report Designer
o Client components:
Client
Office add-ins
Remote Desktop Services
integration
o Developer tools:
Debugger
Visual Studio Tools
Trace Parser
o Management utilities
o Retail components:
Retail POS
o Data Import/Export Framework
components:
Client component

Windows Server 2012 R2, including:


o Internet Information Services
(IIS)
o Remote Desktop Services
Microsoft SQL Server 2012

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Default
name:
RDS<GUID>
Deploy an AX 2012 R3 or AX 2012 R3 CU8 demo environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn741578.aspx
Deploy a Retail essentials demo environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn798907.aspx
Deploy a test environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn798908.aspx
Deploy a Retail essentials dev/test environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn798905.aspx
Deploy a Retail e-commerce dev/test environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn798906.aspx
Deploy a Retail mobility dev/test environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn798909.aspx
Deploy a high availability environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn948285.aspx
Deploy a development environment on Azure [AX 2012]
https://technet.microsoft.com/EN-US/library/dn917488.aspx

Updated: June 5, 2015


This article explains how to deploy a Development or Development with shared SQL Server environment on
Microsoft Azure. To deploy the environment, youll use the Cloud-hosted environments tool in Microsoft
Dynamics Lifecycle Services.

Prerequisites

Deploy Microsoft Dynamics AX 2012 R3 on


Azure using Lifecycle Services (article)

1. Log on to Lifecycle Services


Lifecycle Services (blog)

40

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

2. Create a project
3. Connect the project to your Azure
subscription
4. Connect your corporate network to the
Azure virtual network
5. Deploy a development environment on
Azure
6. Prepare AX 2012 R3 for use
7. Learn more about the service accounts for
this environment
Prerequisites

Before you complete the procedures in this article, make sure that the following prerequisites are in place.
Category
Prerequisite
Required tasks Plan your Microsoft Dynamics AX 2012 R3 deployment on Azure
1. Log on to Lifecycle Services

Microsoft Dynamics Lifecycle Services provides a cloud-based collaborative workspace that customers and
partners can use to manage Microsoft Dynamics AX projects. Youll use this website to deploy AX 2012 R3
on Azure.
Lifecycle Services is available to customers and partners as part of their support plans. You can access it with
your CustomerSource or PartnerSource credentials.
Log on to Lifecycle Services
2. Create a project

After you log in to Lifecycle Services, open an existing project, or create a new project. Projects are the key
organizer of your experience in Lifecycle Services. The methodology associated with a project determines
which phases and tasks are included in the project by default.
3. Connect the project to your Azure subscription

41

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Connect the Lifecycle Services project to your Azure subscription. This will enable Lifecycle Services to
deploy an AX 2012 R3 environment to the subscription. To connect the project to your Azure subscription,
complete the following procedure.
Keep in mind that a project can be connected to only one Azure subscription. If you have multiple Azur e
subscriptions, be sure to identify which subscription you want to use before you complete this procedure.
1. Click Cloud-hosted environments. The Cloud-hosted environments page is displayed.
2. The Microsoft Azure setup panel is displayed on the side of the screen. If it is not displayed, click
Microsoft Azure settings.
3. Enter your Azure subscription ID.
If you need to find your subscription ID, complete the following steps:
1. Open another instance of your browser.
2. Log on to the Azure management portal.
3. In the navigation pane on the left, click Settings. (You may have to scroll to the bottom of the
navigation pane to see the Settings link.) The Settings page is displayed.
4. Copy your subscription ID, and then paste it into the Azure subscription ID field in Lifecycle
Services (which is currently displayed in another browser instance).
4. Click Next.
5. Click Download to download a management certificate.
This management certificate enables Lifecycle Services to communicate with Azure on your behalf. By
default, the management certificate is saved to the Downloads folder on your computer and is named
LifecycleServicesDeployment.cer.
6. Upload the management certificate to Azure. To do so, complete the following steps:
1. Open another instance of your browser. (Or, go to the browser instance that you may have
opened in step 3.)
2. Log on to the Azure management portal.
3. In the navigation pane on the left, click Settings. The Settings page is displayed.
4. Click Management certificates.
5. Click Upload at the bottom of the page.
6. In the Upload a management certificate window, browse to the management certificate that you
downloaded in step 5. Then click the check mark.
7. Go back to the browser that displays the Microsoft Azure setup panel in Lifecycle Services. Click Next.
8. Select the region that is closest to you. The AX 2012 R3 environment will be deployed to a datacenter
in this region.
9. Click Connect.

42

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

The project is now connected to the Azure subscription that you specified. If you discover that you
connected the project to the wrong Azure subscription (that is, assuming you have multiple Azure
subscriptions), youll need to delete the project, create a new project, and then repeat this procedure to
connect the new project to the appropriate Azure subscription.
4. Connect your corporate network to the Azure virtual network

The following sections provide information about how to configure the Azure virtual network and domain so
that your corporate users can access AX 2012 R3. It is recommended that if you require login to these systems
using corporate credentials that you set up the connectivity before you deploy the environment.
This will require using Azure networking capabilities to extend you corporate network to one or more Azure
virtual networks. It will additionally require you to deploy an Active Directory into the Azure virtual network,
which will be set up for trust to your corporate Active Directory. This Active Directory will be used to manage
VM-related resources in the Azure virtual network. This Active Directory will not be used for single sign-on,
and should not be set up to sync the corporate directory. Single sign-on capabilities will be provided through
the domain trust.
Create a site-to-site VPN connection

To enable corporate users to access resources on the virtual machines in the Azure virtual network, youll need
to create a site-to-site VPN connection between the Azure virtual network and your on-premises, corporate
network. For information about how to do this, see:

Virtual network overview


Virtual network configuration tasks
Set up a simulated hybrid cloud environment for testing
Site-to-site VPN in Azure virtual network using Windows Server 2012 Routing and Remote Access
Service (RRAS)
Configure a virtual network gateway in the management portal
Create an Active Directory in Azure

An Active Directory is required in the Azure virtual network. An Active Directory can be deployed to the
Azure virtual network. Please follow Guidelines for Deploying Windows Server Active Directory on Azure
Virtual Machines. Please note that Active Directory Federation Services is not presently supported with AX
2012 R3.
If you are providing the Active Directory, you will need to create the following service accounts within it that
can be used by LCS deployment services when you deploy the environment.
Account

43

Description

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

<DomainName>\AXServiceUser
<DomainName>\AOSServiceUser

AX 2012 R3 service account


AOS service account

<DomainName>\BCProxyUser
<DomainName>\SPServiceUser

Business Connector proxy account


SharePoint service account

<DomainName>\SqlServiceUser

SQL Server service account


AX 2012 R3 installation account
Note: This account must have permission to join
computers to the domain. To give this account
permission, complete the following steps:

<DomainName>\DynamicsInstallUser

44

1. Click Start, click Run, type dsa.msc, and then


click OK.
2. In the task pane, expand the domain node.
3. Locate and right-click the organizational unit
that you want to modify, and then click Delegate
Control.
4. In the Delegation of Control Wizard, click Next.
5. Click Add to add a specific user or a specific
group to the list, and then click Next.
6. In the Tasks to Delegate page, click Create a
custom task to delegate, and then click Next.
7. Click Only the following objects in the folder,
and then from the list, click to select the
Computer objects check box. Then, select the
check boxes below the list, Create selected
objects in this folder and Delete selected objects
in this folder.
8. Click Next.
9. In the Permissions list, click to select the
following check boxes:
o Reset Password
o Read and write Account Restrictions
o Validated write to DNS host name
o Validated write to service principal name
10. Click Next, and then click Finish.
11. Close the Active Directory Users and Computers
MMC snap-in

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

You will need to provide the passwords for these accounts when you deploy the environment.
Create a domain trust

To enable corporate users to access resources on the virtual machines in your Azure domain, you must create
an Active Directory trust between the domains. For information about how to create a trust, see Create a Forest
Trust. This process is the same process you would use to create a trust between two on-premises domains.
Give the Administrators group the right to log on as a batch job

Log in to the Active Directory domain controller and complete the following steps to give the built-in
Administrators group the right to log on as a batch job.
1.
2.
3.
4.

Click Start, click All Programs, and then click Administrative Tools.
In the Administrative Tools menu, select Group Policy Management.
In the Group Policy Management console tree, click Forest: <ServerName>, and then click Domains.
Click the name of your server, expand Domain Controllers, right-click Default Domain Controllers
Policy, and then click Edit.
5. In the Group Policy Management Editor, click Default Domain Controllers Policy <ServerName>
Policy, expand Computer Configuration, and then click Policies.
6. In the Policies tree, expand Windows Setting, and then click Security Settings.
7. In the Security Settings tree, expand Local Policies, and then click User Rights Assignment.
8. In the results pane, scroll to and then click Log on as a batch job.
9. In the Log on as a batch job Properties dialog box, click Add User or Group.
10. In the Add User or Group dialog box, click Browse.
11. In the Select Users, Computers, or Groups dialog box, type Administrators.
12. Click Check Names to verify that the built-in Administrators account appears, and then click OK three
times.
Change the default organizational unit

If you want virtual machines to be added to Active Directory in a custom organizational unitversus the
default organizational unityou can change the default organizational unit in your Active Directory prior to
starting deployment. For more information, click here.
5. Deploy a development environment on Azure

Complete the following procedure to deploy a development environment on Azure.


1. On the Cloud-hosted environments page, click the Add (+) icon.
2. In the Select environment topology panel, select Dev/test.

45

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

3.
4.
5.
6.

Click Development or Development with shared SQL Server.


In the Environment name field, enter a name for the environment that will be deployed.
Click Advanced settings.
To customize domain settings, click Customize domain settings. Then use the following table to enter
information.
If you want to:
Create a new domain in Azure
for the environment

Do this:
1. Click New domain.
2. Enter a name for the domain. By default, the
domain is named contoso.com.

Add the environment to an


existing domain in Azure

3. Click Existing domain.


4. Enter the name of the domain. For example,
contoso.com.

7. To customize the service accounts that will be created in the domain, click Customize service accounts.
Service accounts and/or service account passwords may be specified through the Advanced Settings
option for a deployment. If neither is provided, default accounts are used and random passwords are
selected. Use these features when you want to maintain account naming and password rules for your
corporation.
Account and password rules:
o
o

A valid service name must be less than 20 characters with no special characters.
A valid password must be more than 8 characters and contain uppercase letters, lowercase
letters, numbers, and at least one of the following characters: ['@', '!', '=', '*']
You cant use common passwords, such as: pass@word1

8. To select the version of AX 2012 R3 that you want use, click Supported version.
By default, the AX 2012 R3 CU8 version of this environment will be deployed. If you dont want to
use the CU8 version, select Dynamics ERP 2012 R3 RTM from the list.
9. To customize virtual machine names, click Customize virtual machine names.
In order to support common IT naming guidelines, the ability to name virtual machines is provided
through the Advanced settings option on most deployment topologies. In addition to defining the name,

46

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

a starting index can be selected for each virtual machine type. The index is incremented for each
instance of the virtual machine type that is deployed.
Virtual machine names must be 13 characters or less. The index is separated from the machine name by
a hyphen (-), followed by the index that supports a maximum of 2 digits. Example:
ACustomVMName-99
When virtual machine instances are added to an environment after the initial deployment, the
deployment service will start incrementing the virtual machine name where it left off. For example, if
you deployed four AOS virtual machines with a starting index of 2, then the last AOS instance name
will be AOS-6. If you add two more AOS instances, they will be AOS-7 and AOS-8.
If one of the virtual machine types in your deployment is customized, then all of the virtual machine
names must be customized. This is done to ensure that a long deployment does not occur because a
virtual machine name was accidentally missed.
10. To customize virtual network settings, click Customize virtual network. Then use the following table to
enter information.
If you want to:
Create a new virtual
network in Azure for
the environment

Add the environment


to an existing virtual
network in Azure

47

Do this:
0. Click New virtual network.
1. Enter a name for the virtual network.
2. Click Existing virtual network.
3. Select the name of the existing virtual network that you
want to use.
4. The Address space field will automatically display the
appropriate value. Select the provided value.
5. The Application subnet name field will display available
options. If you are deploying to an AD that was
previously deployed through Lifecycle Services, select
the *APPNET* value.
6. The Active Directory subnet must be entered and match
the Active Directory subnet IP/Range found in the
Azure management portal for the AD you desire to
target.
1. Log on to the Azure management portal.
2. In the navigation pane on the left, click
Networks.
3. Click the name of the virtual network that youre
going to use.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

4. Click Configure.
Details about the virtual network are listed on the
page.
11. Click Done. The Deploy environment panel is redisplayed.
12. The number and size of each virtual machine that will be deployed is listed. Change the number and
size of the virtual machines, as needed.
o For information about the software installed on each virtual machine in this environment, see
Plan your Microsoft Dynamics AX 2012 R3 deployment on Azure.
o For sizing and pricing details about virtual machines, see Virtual machines pricing details.
13. Click Software License Terms to review the licensing terms and conditions. Then select the check box
to indicate that you agree to the terms.
14. Click Next.
15. Click Deploy to confirm that youre ready to deploy the environment.
The deployment may take a few hours to complete. When the deployment is done, the Deployment
Status column on the Cloud-hosted environments page will display Deployed. (You may need to
refresh your browser to see this.)
If the deployment fails, you may see an error message right away. If the error occurs later in the
deployment process, error details will be displayed in the details pane on the right-side of the page.
6. Prepare AX 2012 R3 for use

Now that the environment has been deployed on Azure, you must set up and configure AX 2012 R3 for use.
See the following sections for more information.
Log on to the AOS virtual machine

Log on to the AOS-<GUID> virtual machine using the <DomainName>\DynamicsInstallUser account. For
instructions, see the How do I log on to a virtual machine? section of the Manage your Microsoft Dynamics
AX 2012 R3 deployment on Azure article.
Compile AX 2012 R3

Compile AX 2012 R3 by using AxBuild.exe. For instructions, see AxBuild.exe for Parallel Compile on AOS
of X++ to p-code.
Initialize AX 2012 R3

48

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Open the AX 2012 R3 client and complete the initialization checklists. For instructions, see Initialization
checklists.
Install sample data

If you want sample data installed in your environment, complete the following steps.
1. Log on to the SQL-<GUID> virtual machine.
Log on to the virtual machine using the <DomainName>\DynamicsInstallUser account. For
instructions, see the How do I log on to a virtual machine? section of the Manage your Microsoft
Dynamics AX 2012 R3 deployment on Azure article.
2. Go to the following location on the virtual machine:
F:\TestTransferTool
3. Install the Test Data Transfer Tool. For instructions, see Install the Test Data Transfer Tool (beta) for
Microsoft Dynamics AX.
4. Open a command prompt and navigate to the following location:
C:\Program Files (x86)\Microsoft Dynamics AX 2012 Test Data Transfer Tool (Beta)
5. Run the following command:
dp.exe import F:\DemoData MicrosoftDynamicsAx
Note

The sample data includes trial license keys for AX 2012 R3. If you choose not to install the
sample data, you can download trial license keysfor development or testing purposesfrom
CustomerSource or MSDN.
Give users access

To enable your users to access AX 2012 R3, complete the following tasks:

Add each users domain account to the Remote Desktop Users group on the CLI-<GUID> virtual
machine.
Give users access to AX 2012 R3. For instructions, see Create new users in Microsoft Dynamics AX.

Note

49

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

If you dont want to create a VPN connection and a domain trust, you can still give users access
to AX 2012 R3. To do so, youll need to log on to the virtual machine that serves as the domain
controller, and create domain accounts for each user. Then, youll need to complete the two
tasks mentioned above.
Set up and configure AX 2012 R3

The procedures for setting up and configuring AX 2012 R3 on Azure are the same procedures used for setting
up and configuring on-premises deployments. See the following resources for more information.
Task

Resources
System setup for Microsoft Dynamics AX
The Microsoft Dynamics AX client
Application Object Servers
Reporting in Microsoft Dynamics AX
Note

Be sure to deploy the default reports and grant users


access to them.

Management Reporter 2012


Analytics in Microsoft Dynamics AX
Note

See the
instructions on
TechNet

To process the cubes that are included with AX 2012


R3, we recommend that you increase the
ExternalCommandTimeout value to 7200. For more
information, see SSAS Error in processing a dimension:
HYT00, Query Timeout Expired on the Coding Rocks!
blog.

Help server
Enterprise Portal and Role Centers
Note

Enterprise Portal is configured to run on port 81, so be


sure to exclude that port in your firewall settings.

50

Enterprise Search
Services and Application Integration Framework (AIF)

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

View printable
guides and
white papers
Use the
Microsoft
Dynamics AX
web search tool

Microsoft Dynamics AX Retail for IT pros and


developers
.NET Business Connector
Security

Printable guides
White papers for system administrators

Web search for developers


Web search for system administrators
Web search for application users
Combined web search

7. Learn more about the service accounts for this environment

The following sections provide information about the service accounts that were created when you deployed
the environment.
Domain accounts

The following table lists the default names of the domain accounts that are created when you deployed the
environment.
Domain account

<DomainName>\AOSServiceUser

Description
The account used to run the
following services on AOS<GUID> virtual machines:

Password

The passwords are


Microsoft Dynamics AX displayed on the
Object Server
Cloud-hosted
environments page in
Lifecycle Services.
The account used to run the
following services on SQL<GUID> virtual machines:

<DomainName>\SQLServiceUser

51

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

<DomainName>\DynamicsInstallUser

SQL Server Analysis


Services
(MSSQLSERVER)

The account used to install AX


2012 R3.
The account used to run the
following services on EP<GUID> virtual machines:

<DomainName>\SPServiceUser

<DomainName>\BCProxyUser

AppFabric Caching
Service
SharePoint Search Host
Controller
SharePoint Server Search
15
SharePont Timer Service
SharePoint User Code
Host

The account used as the Business


Connector proxy.
The account used to run the
following services on AOS<GUID> virtual machines:

Microsoft Dynamics AX
Data Import/Export
Framework Service
Microsoft Dynamics ERP
RapidStart Connector

<DomainName>\AXServiceUser
The account is also used to run
the following services on CLI<GUID> virtual machines:

52

Microsoft Dynamics AX
for Retail Commerce
Data Exchange Async
Client

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Local administrator accounts

Each virtual machine that you deployed has a local administrator account. This account is:
builtin\axlocaladmin.
The passwords for the local administrator accounts are displayed on the Cloud-hosted environments page in
Lifecycle Services.

Select the Cloud hosted


environments tile.

You must attach a Microsoft Azure


subscription to your project prior to the demo
by using the Microsoft Azure settings
selection at the top. You can find out how to
do that here.

53

https://manage.windowsazure.com

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

54

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

55

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

http://www.azurespeed.com/

You see the cloud-hosted environments deployment portal.


The upper section is where you add or remove environments from the project as well as use Microsoft Azure
settings to enter your Microsoft Azure ID to connect it to the project or adjust Microsoft Azure settings. The
last option you use to open the Microsoft Azure management portal.
Below that is the list of the environments that have been deployed into the associated Microsoft Azure
subscription through cloud-hosted environments.

56

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Tip: Removing an environment here only removes the association from the project. It does not spin down,
stop, or delete the VMs within Microsoft Azure or stop any charges they may incur while running. You can
only do that through the Microsoft Azure Management Portal. This is where you stop, start, and change the
size of the VMs and manage your Microsoft Azure subscription VMs.

Click the plus sign (+) near the top


under Cloud.

High Availability
Demo

57

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

DevTest

58

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

59

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

60

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

[Development with shared SQL Server]

61

Click DEVTEST. (The colored back


ground of the selection shows it is
selected.)

Click Next.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

62

Enter the environment name.

Select the check box to acknowledge


that you agree to the pricing and
licensing terms viewable by the link
just below it.

Click Next.

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

63

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

64

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Click Deploy.

Tip: Once you click Deploy, the Microsoft


Azure billing, per the Microsoft Azure price
list, will begin immediately.

You will see that the environment now


appears in the list in alphabetical order by
environment name and that its deployment
status is Deploying.

Troubleshooting

65

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

66

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Deployment Status: Stopped > Deallocating >


Pending delete

67

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Deployment Status: Pending delete >


Deleting

[Redeploy]

68

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

When the deployment status is Deployed:

You can click the name of the


deployment.

The Topology window opens to the right


with all the detail for the deployed
environment including the names of the VMs,
description, status, and the logon information.
To see that the VM is deployed and running,

Click Microsoft Azure portal.

The Microsoft Azure Management Portal is


opened in a separate tab and you are logged
on to your subscription. Here you can see the
VM has been deployed and is running.
For information on managing VMs including
how to log on to a VM, configure, and
manage them, click here.

69

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Log on to the AOS virtual machine: Log on to


the AOS-<GUID> virtual machine using the
<DomainName>\DynamicsInstallUser
account. For instructions, see the How do I
log on to a virtual machine? section of the
Manage your Microsoft Dynamics AX 2012 R3
deployment on Azure article.

Initiate Dev Shared SQL Environment See _LCSinActionWorkshop-Develop12_InitiateDevSharedSQLEnvironment.docx >>> To be continued???

[Demo AX 2012 R3 CU9]

70

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

71

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

It took around 1 hour

72

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

[Rearm if need]
1.Click Start, and then click Command Prompt.
2.Type slmgr.vbs -dli, and then press ENTER to check the current status of your evaluation period.
3.To reset the evaluation period, type slmgr.vbs rearm, and then press ENTER.
4.Restart the computer.

73

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Cloud-hosted environments provide a simple and quick way to deploy different Microsoft Dynamics AX 2012
R3 environments to your Microsoft Azure subscription. Simply choose the environment you want to deploy
and it will automate the server setup of the environment, saving you up to hundreds of hours per deployment.
You can also deploy multiple environments simultaneously, helping you save even more time and resources.

Conclusion
The series of demo scripts in this collection walk you through the tools and services in the Develop phase of ALM
for LCS. These services help project managers and business analysts better analyze and plan usage, speed up and
increase user adoption, help meet regulatory requirements, maximize uptime, and help the organization realize
business value faster all while delivering amazing customer experiences.

Glossary and Additional Background Content


There is a series of three videos on LCS, one for each phase, which are available on YouTube:
Microsoft Dynamics AX 2012 R3 Lifecycle Services (LCS) Define Phase Demo and Discussion
http://youtu.be/ij28o4JznJA
Microsoft Dynamics AX 2012 R3 Lifecycle Services (LCS) Develop Phase Demo and Discussion
http://youtu.be/TTAuukkK5Mo
Microsoft Dynamics AX 2012 R3 Lifecycle Services (LCS) Operate Phase Demo and Discussion
http://youtu.be/Uiok3ziH2Eo

74

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

Disclaimer
2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista, Microsoft Dynamics
and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other
countries. Other names and brands may be claimed as the property of others.
The information herein is for informational purposes only and represents the current view of Microsoft
Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it
should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the
accuracy of any information provided after the date of this presentation.
Sample code included in this presentation is made available AS IS. THE ENTIRE RISK OF THE USE OR THE
RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE
INFORMATION IN THIS PRESENTATION. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR
OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS PRESENTATION.
Microsoft products are not intended for use in medical, life-saving, or life-sustaining applications.
Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your
people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar
Microsoft software, automating and streamlining financial, customer relationship and supply chain processes in a
way that helps you drive business success.
U.S. and Canada Toll Free 1-888-477-7989
Worldwide +1-701-281-6500 www.microsoft.com/dynamics

75

Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Cloud Hosted Environments | Last Updated: August 2015

You might also like