Skip to main content

Step by Step: Deploy AX 2012 R3 on Azure via Life Cycle Service

AX 2012 R3 is finally here. With that they have made the demo environment available on Azure and can be deployed using Life Cycle Service.

There are a few posts out there detailing but I thought I do a quick screenshot step by step guide on how to deploy AX 2013 R3 on Azure via Life Cycle Service.

http://blogs.msdn.com/b/axinthefield/archive/2014/05/01/setting-dynamics-ax-2012-r3-demo-with-lcs-and-azure.aspx

http://technet.microsoft.com/en-us/library/dn741581.aspx

1. Log on to LCS and create

2. Create a new project and fill in the required details.

02-R3 New Project

3. Once the project is created click on the “Cloud hosted environment” icon.

03-R3 ProjectMain

4. Now go to Azure portal and grab your subscription ID. You will need it for the next step. It is a GUID.

04-AzureSubscription

5. Back in LCS portal – you click the add button. You will need your Azure Subscription GUID.

05-AzureConnection

6. Now it will give you a certificate to download.

07-AzureDownloadsaveCert

8. In Azure portal click on Settings and upload the certificate.

08-AzureMgmtCert

09-AzureMgmtCertUpload

9. It should show up as loaded with the subscription id.

10-AzureMgmtCertUploadAdded

10. Now in LCS you can select where you want to host your server.

11-AzureAssignRegion

11. Follow the wizard and click on Deploy.

13-AzureDeplyDemo

12. Enter the name of your environment and click next.

14-AzureEnvirName

13. Click on Deploy.

15-Areyousure

14. It will come up with status of Deploying…

Give it a couple of hours or so.

16-DeployingStart9-35amEST

15. Status will come up as Deployed.

17-DeployingFinish10-40amEST

16. Go to Azure portal and now you should have an image with status of Running.

18-ImageDeployedinAzure

16. Just click on the connect button. It will download an mstc file you can jump into.

Server has everything you need deployed from AX, to Management reporter, EP etc.

19-LogintoImage

You can stop and configure it to allocate more resources but for me it ran pretty smooth for the work I was doing.

Enjoy.

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi