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.

Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

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())     {    ...
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more