Onboard an implementation project
This article describes how to onboard a finance and operations project by using Microsoft Dynamics Lifecycle Services (LCS).
Microsoft 365 Admin Center
After your organization has purchased a subscription to a finance and operations app, the service must be activated on your organization's Azure Active Directory (Azure AD) tenant by a tenant administrator. In this article, tenant administrator refers to any user of the Azure AD tenant with the Global Administrator security role. For more information about Azure AD roles, please see Understand roles in Azure Active Directory.
The tenant administrator must complete the following steps:
Open an InPrivate or Incognito browser session and go to the Microsoft 365 Admin Center.
Sign in with your tenant administrator credentials.
Go to Billing > Products & services and confirm that there is an active subscription for the application that you want to deploy.
If you do not see an active subscription, consult with your licensing partner to confirm the status of the subscription transaction. It is important to confirm that the subscriptions were purchased for the correct Azure AD tenant. By default, all Microsoft online services should be running on the same Azure AD tenant. The most frequent cause for onboarding delays is that subscriptions are inadvertently placed on an incorrect Azure AD tenant.
If the subscription in question is shown as active, proceed to the next step by signing in to LCS to trigger the Implementation Project creation flow.
Open another private browser tab and go to Lifecycle Services. Select Login to access LCS with your current tenant administrator credentials.
Connection endpoints might be different for Government Community Cloud (GCC) and other local cloud deployment options. For more information see, Sovereign and local cloud deployment options for Dynamics 365 Finance and Dynamics 365 Supply Chain Management.
Accept and confirm any other prompts displayed to complete the implementation project provisioning.
The tenant administrator is assigned the Project Owner security role in the provisioned implementation project.
If the tenant administrator will not be a participant in the implementation, at least one additional Project Owner must be assigned to the implementation project.
For an overview of LCS user management, including the security roles that can be assigned to users, see Configure Lifecycle Services (LCS) security.
LCS implementation project workspace
After the tenant administrator has completed the finance and operations subscription activation and added additional project users as appropriate, those team members can access the Implementation project workspace.
The first step to be completed in LCS is Project onboarding. This step is required for all LCS implementation projects that are created on or after August 22, 2019, PST, prior to deploying any of the Microsoft-managed environments. You can access the Project onboarding feature using the action center notification or the LCS Implementation project menu. You must be assigned to the Project owner security role to access Project onboarding in LCS.
To get started with LCS, see Lifecycle Services (LCS) for finance and operations apps customers.
FastTrack onboarding services
After the LCS Implementation project workspace is provisioned, the Microsoft FastTrack team will monitor your onboarding progress. If project onboarding is not completed within a few weeks after creating an LCS Implementation project, a reminder will be sent to the project team.
For more information about the FastTrack program and the services provided, see Microsoft FastTrack.
For more information about LCS project onboarding, see LCS project onboarding.
All onboarding-related emails from the FastTrack team will originate from Dynamics 365 Onboarding (email@example.com), so please ensure that any spam blocker/filter allows email from this address.
Key data to keep current in LCS
We recommend that you add key project members (such as project managers) from the customer and partner teams to the LCS implementation project. Be sure to include each person's work email address. In this way, you help us work best with you and help ensure that project members don't miss important communication from us.
Be sure to keep the milestone dates in your LCS project current. In this way, you help us connect with you at different project stages. When you're closer to your go-live date, we will contact you for a project Go-live assessment before we deploy your production environment.
Milestone dates are stored in the LCS implementation methodology. For more information, see the Methodologies section of the "LCS for Customers" article.
Help us understand
Submit and view feedback for