Lifecycle Services: Environments & Deployments

Lifecycle Services (LCS) is the primary operational hub for F&O implementations. It manages environments, package deployments, troubleshooting, and application lifecycle — though developer environments are increasingly managed through the Power Platform admin center (covered in the next module).

Simple explanation

Think of LCS as the control tower for your F&O project.

Just like an airport control tower manages planes (takeoff, landing, routing, emergencies), LCS manages your F&O environments. Need a new sandbox? LCS spins it up. Need to deploy your code to production? LCS handles the deployment. Something broken? LCS has Issue Search to help diagnose it. It is the one portal you always have open during an F&O project.

Environment Types

Environment	Purpose	Managed By	Refresh
Development	Write and test code	Developer (cloud-hosted or local VM)	N/A — developer controls
Tier-1 Sandbox	Build verification, basic testing	Microsoft-hosted	Can be reset
Tier-2+ Sandbox	UAT, performance testing, staging	Microsoft-hosted (production-like)	Can be refreshed from production
Production	Live business operations	Microsoft-hosted	Deployment via LCS only

🏗️ Vik’s project reality: “At Axion, every client project starts in LCS. We create the project, provision dev environments, set up Azure DevOps integration, and establish the deployment pipeline. My first deployment to a client’s sandbox goes through LCS — there is no shortcut.”

Environment lifecycle

Provision — create environments from LCS (select region, tier, configuration)
Develop — write code in dev environment, build deployable packages
Deploy — upload package to LCS Asset Library, deploy to sandbox
Test — UAT in sandbox, validate with business users
Promote — deploy the same tested package to production
Monitor — use LCS diagnostics, environment monitoring, Activity Monitor

Issue Search

Issue Search lets you search Microsoft’s knowledge base for known issues, hotfixes, and workarounds.

How to use it:

Navigate to your LCS project
Open Issue Search
Enter keywords, error messages, or KB article numbers
Filter by product version and module
Review matching issues — each includes description, root cause, and resolution (hotfix or workaround)

🎓 Sophie’s troubleshooting story: “My first production issue was a posting error. Instead of panicking, Carl showed me Issue Search. I pasted the error message, found a known issue with a hotfix, downloaded it from the Asset Library, and deployed it to the sandbox for testing. Problem solved in two hours.”

Exam tip: Issue Search vs support ticket

The exam may ask how to research and resolve issues. Issue Search is the FIRST step — check for known issues and existing hotfixes before opening a support ticket. Only escalate to Microsoft Support when Issue Search does not have a matching resolution.

Asset Library

The Asset Library stores all deployment artifacts for your project.

Asset Type	Description	Example
Software deployable package	Compiled code package for deployment	Your custom model package
Process data package	Data packages for import/export	Configuration data, master data
BPM library	Business process recordings from Task Recorder	Standard operating procedures
Configuration	Environment configuration exports	Application configuration
Hotfix	Microsoft-released fixes	Platform and application hotfixes

Package deployment workflow

Build your model in Visual Studio → produces a deployable package (.zip)
Upload the package to the LCS Asset Library
Apply the package to a sandbox environment (LCS manages the process)
Validate in sandbox — run tests, get business sign-off
Mark as release candidate in LCS
Schedule deployment to production — LCS deploys during a maintenance window

Sandbox vs Production Deployment
Aspect	Sandbox Deployment	Production Deployment
Who initiates	Developer or admin via LCS	Admin via LCS with scheduled window
Downtime	Expected — sandbox can be offline	Minimised — Microsoft manages rollout
Rollback	Re-deploy previous package	Microsoft supports rollback
Validation required	Recommended — UAT testing	Mandatory — must be tested in sandbox first
Package source	Asset Library (any package)	Asset Library (release candidate only)

Question

What is the primary purpose of Lifecycle Services (LCS)?

Click or press Enter to reveal answer

Answer

LCS is the central hub for managing F&O implementations: environment provisioning, package deployment, diagnostics, Issue Search, Asset Library, and project management. Every F&O project has an LCS project.

Click to flip back

Question

What is Issue Search in LCS?

Click or press Enter to reveal answer

Answer

A search tool that queries Microsoft's knowledge base for known issues, hotfixes, and workarounds. You search by error message, keywords, or KB numbers. It is the first step in troubleshooting before opening a support ticket.

Click to flip back

Question

What is the Asset Library in LCS?

Click or press Enter to reveal answer

Answer

A storage location for deployment artifacts: software deployable packages, process data packages, BPM libraries, configurations, and hotfixes. Packages must be uploaded to the Asset Library before they can be deployed to environments.

Click to flip back

Question

What is the correct deployment path for custom code to production?

Click or press Enter to reveal answer

Answer

Build in dev → upload package to LCS Asset Library → deploy to sandbox → test and validate → mark as release candidate → schedule production deployment via LCS.

Click to flip back

Knowledge Check

Vik encounters a posting error in a client's sandbox. What should be his first troubleshooting step?

Knowledge Check

Sophie needs to deploy her custom code to the client's production environment. Where must the package be uploaded first?

Knowledge Check

Which LCS artifact type stores Task Recorder recordings for documentation and training?

Next up: Unified Developer Experience & Implementation Portal — the new UDE environments and Power Platform admin center for developers.