<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Training on</title><link>https://www.jaestevan.com/en/tag/training/</link><description>Recent content in Training on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Wed, 25 Nov 2015 00:00:00 +0100</lastBuildDate><atom:link href="https://www.jaestevan.com/en/tag/training/index.xml" rel="self" type="application/rss+xml"/><item><title>Prepare Yourself for the New Microsoft Dynamics AX</title><link>https://www.jaestevan.com/en/blog/2015/prepare-yourself-for-the-new-microsoft-dynamics-ax/</link><pubDate>Wed, 25 Nov 2015 00:00:00 +0100</pubDate><guid>https://www.jaestevan.com/en/blog/2015/prepare-yourself-for-the-new-microsoft-dynamics-ax/</guid><description>&lt;p&gt;We have already commented several times that &lt;a href="https://www.jaestevan.com/tag/lcs/"&gt;Lifecycle Services&lt;/a&gt; is going to be a fundamental piece when managing the infrastructure of the new Microsoft Dynamics AX. Tasks such as deploying new environments, modifications, updates, monitoring, etc. will be LCS&amp;rsquo;s responsibility in the short term, so while we wait for the public &lt;em&gt;preview&lt;/em&gt; launch, we can start preparing our LCS to have it ready on launch day.&lt;/p&gt;
&lt;figure&gt;&lt;img src="https://www.jaestevan.com/images/2015/lcs.png"
alt="Microsoft Dynamics Lifecycle Services"&gt;
&lt;/figure&gt;
&lt;h2 id="connect-lcs-with-azure-subscriptions"&gt;Connect LCS with Azure Subscriptions&lt;/h2&gt;
&lt;p&gt;The first thing we need to do is connect our LCS project to our &lt;a href="https://www.jaestevan.com/tag/azure/" title="Tag: Azure"&gt;Azure&lt;/a&gt; subscriptions, which will be essential to deploy our work environments, including development, testing, demo, &lt;em&gt;build&lt;/em&gt;, etc.&lt;/p&gt;</description></item></channel></rss>