MCSD: App Builder

I have MCSD: App Builder — where should I go now?

For a holder who still writes C# and ASP.NET applications, modern .NET and ASP.NET Core usually preserve the most existing expertise. Add Azure hosting, identity, delivery and monitoring according to the applications you maintain. Your prerequisite, elective and subsequent work matter: App Builder was not a single cloud-development syllabus.

Strongest legacy background	Closest modern pathway	What to add next
C# and established .NET applications	.NET developer / modernization	Supported .NET, dependency assessment and tested framework migration
ASP.NET MVC, HTTP services and browser applications	ASP.NET Core and web APIs	Middleware, API contracts, Entra scopes and integration tests
Azure services, data access and asynchronous processing	Azure application and integration development	Managed identity, Functions, containers and distributed diagnostics
TFS, testing, ALM or application deployment	DevOps / platform delivery	GitHub/Azure Pipelines, workload federation and release recovery
Application architecture and Azure design	Cloud solution architecture	Azure operations, governance, failure domains and cost tradeoffs
UWP and Windows client applications	Windows client modernization	Windows App SDK/WinUI migration and client/API authentication

These are MCSEDirectory editorial recommendations based on skills overlap, not official MCSD equivalencies. Modern guidance checked: 7 September 2026. Azure Developer Associate / AZ-204 is retired; the credential choices below account for that change. Microsoft status; retirement date.

What was this certification?

Microsoft Certified Solutions Developer: App Builder belonged to the MCSD — Microsoft Certified Solutions Developer family. It combined a qualifying MCSA development foundation with an additional specialization. Microsoft’s streamlined programme aligned these qualifications with areas of partner competence, while allowing developers to select different technologies. Microsoft programme slides, pages 2–3 and 11.

Introduction and programme relationships

The September 2016 elective pool is preserved in Microsoft’s roadmap updated 6 October 2016. This establishes the introduction era; the exact first-award day has not been established from the programme sources reviewed. The qualification brought together routes related to MCSD: Web Applications, MCSD: Universal Windows Platform and MCSD: SharePoint Applications, all named in Microsoft’s transition-award list. Roadmap, pages 4 and 11.

The earlier MCSD: Web Applications had a documented route of 70-480 + 70-486 + 70-487. App Builder’s MCSA-plus-elective model was more flexible; similar exam records can therefore represent different programme generations. Microsoft Press, April 2016.

Microsoft replaced the recurring MCSD recertification-exam model with a non-expiring award and an opportunity to earn another dated entry through an additional elective each year. That was optional continuing recognition, not a requirement to keep App Builder valid. Programme rule, page 3.

Retirement and existing holders

The remaining exams retired on 31 January 2021, following an extension announced on 26 March 2020 from the original June 2020 deadline. App Builder ceased to be available to earn as Microsoft moved to role-based credentials. That programme change did not automatically award a modern certification to MCSD holders. Final Microsoft notice.

An earned MCSD does not expire under Microsoft’s credential policy and remains a historical achievement. Retirement affects availability and transcript categorization, not whether you passed the qualification. Microsoft’s current policy keeps a non-expiring retired credential in the active transcript section for two years after retirement; the original retirement notice also describes later movement to an inactive section. Use the exact title and award year on your CV, alongside evidence of your current development work. Holder policy; retirement FAQ.

Historical certification requirements

Standard award rule: one prerequisite AND one additional elective

Earn either MCSA below, then pass a qualifying elective that was not already used for that prerequisite. The MCSD did not require both MCSAs or every elective. Microsoft roadmap; Microsoft Support clarification.

Prerequisite certification	Required exam combination
MCSA: Web Applications	70-486 AND either 70-480 OR 70-483
MCSA: Universal Windows Platform	70-483 AND 70-357

Exam	Exact title	Place in the foundation
70-480	Programming in HTML5 with JavaScript and CSS3	Browser-programming alternative in Web Applications
70-483	Programming in C#	C# alternative in Web Applications; required for UWP
70-486	Developing ASP.NET MVC Web Applications	Required for Web Applications
70-357	Developing Mobile Apps	Required for UWP; Windows 10 UWP context, despite the broader title

The combinations and titles appear on page 11 of the Microsoft roadmap. Microsoft’s developer blog separately identifies 70-357 as its UWP exam, distinct from the Xamarin certification. Microsoft Developer Support.

Later elective choices: documented January 2020 rule

Elective	Exact title	When it added the MCSD component
70-357	Developing Mobile Apps	Additional client-development exam for a Web Applications holder
70-486	Developing ASP.NET MVC Web Applications	Additional web-development exam for a UWP holder
70-487	Developing Microsoft Azure and Web Services	Additional services/data/Azure exam for either prerequisite

Microsoft Support explicitly confirmed the three-exam pool and the prohibition on reusing a prerequisite exam in January 2020. Thus 70-480 + 70-486 earned the web MCSA, but did not also earn App Builder just because 70-486 appeared in the elective list. Adding 70-487 was one completion route; adding 70-357 was another. For a UWP holder with 70-483 + 70-357, 70-486 OR 70-487 supplied the additional component. These combinations follow the documented rule. January clarification; corroborating support answer.

Earlier elective pool: September 2016 snapshot

The launch-era pool was broader. Microsoft’s roadmap explicitly labels the following list September 2016; it must not be treated as the final 2020 list. Page 11.

Exam	Exact title in the roadmap
70-532	Developing Microsoft Azure Solutions
70-534	Architecting Microsoft Azure Solutions
70-487	Developing Microsoft Azure and Web Services
70-488	Developing Microsoft SharePoint Server 2013 Core Solutions
70-489	Developing Microsoft SharePoint Server 2013 Advanced Solutions
70-354	Universal Windows Platform – App Architecture and UX/UI
70-355	Universal Windows Platform – App Data, Services, and Coding Patterns
70-496	Administering Microsoft Visual Studio Team Foundation Server
70-497	Software Testing with Visual Studio
70-498	Delivering Continuous Value with Visual Studio Application Lifecycle Management

These were alternative specializations. A testing or SharePoint elective did not establish the same Azure experience as 70-532 or 70-534. The exact changeover dates for every intermediate elective pool have not been reconstructed; see the source notes for a February 2019 variation.

Transition awards and alternative routes

Microsoft’s October 2016 rules provided routes beyond sitting a new three-exam combination:

Active holders of the listed MCSD: Web Applications, MCSD: Universal Windows Platform or MCSD: SharePoint Applications could receive the corresponding new 2016 award through transcript reevaluation, without additional exams.
A qualifying elective passed since 1 January 2016 could trigger the corresponding award if all other exam requirements were met.
Through 31 December 2016, holders of inactive MCSE/MCSD qualifications could use a recertification exam or a new qualifying elective under the transition rules.

These were dated programme provisions, not a permanent exemption from prerequisites. The reviewed slides do not identify a dedicated numbered “App Builder upgrade exam”; they describe transcript credit and existing exams. Do not mistake a predecessor’s upgrade or recertification exam for a mandatory App Builder exam. Microsoft transition rules, pages 4–5.

Technologies and development skills represented

The foundation differed by route. Web Applications combined browser or C# programming with MVC application design, user experience, debugging and application security. UWP combined C# with Windows client development. A Web Applications holder could qualify without sitting the standalone C# exam, so the award alone does not prove a 70-483 pass. Foundation roadmap; MVC objectives; C# data-access reference.

Elective background	Distinctive technical emphasis
70-487: services and data	Data-access selection, Entity Framework/LINQ, transactions, caching, HTTP APIs and Azure deployment. Earlier objectives included substantial WCF implementation; the January 2018 revision retained WCF consumption while adding more cloud-service work. Microsoft objective changes
70-532 / 70-534: Azure	Azure solution development or architecture respectively. These offer a historical basis for a cloud direction, but the roadmap alone does not establish the detailed objective version a particular holder took. Dated exam pool
70-357 / 70-354 / 70-355: UWP	Windows client applications, with the older electives distinguishing UI/architecture from application data and services. This was not proof of Xamarin or general iOS/Android development. Roadmap; Microsoft UWP/Xamarin distinction
70-488 / 70-489: SharePoint	SharePoint Server 2013 development specialization. Its platform-specific application model should be separated from general ASP.NET and Azure knowledge. Roadmap
70-496 / 70-497 / 70-498: delivery	TFS administration, software testing or ALM respectively. These justify a delivery/testing branch when supported by subsequent work; they were not three compulsory DevOps exams. Roadmap

Cloud development was already present in the later syllabus. The 70-487 changes effective 15 January 2018 include Docker hosting, Azure Functions, API Management, Azure AD/OAuth, Application Insights and continuous deployment. It would be inaccurate to say every App Builder holder came from an exclusively IIS/.NET Framework world, or that containers and serverless arrived only after retirement. Objective revision, pages 3–4.

What remains relevant today

C# data modelling, collections and LINQ remain useful for application logic and data access. MVC separation, HTTP resource design, validation, asynchronous I/O and diagnosing an exception still provide a foundation for ASP.NET Core work. The value lies in understanding behaviour and dependencies even when the framework APIs change. Historical C# reference; current ASP.NET Core learning path.

For a 70-487 specialist, reasoning about query execution, transactions, retries and service contracts is especially valuable when moving data between applications. For a testing/ALM specialist, regression analysis and release coordination remain useful when the build system changes. Treat these as correspondences to your actual study and work, rather than skills guaranteed by the MCSD title alone.

What has changed

.NET Framework and modern .NET are different migration targets. Current .NET supports cross-platform applications, but Windows-specific dependencies and unsupported application models need assessment. Moving an ASP.NET application requires changes to its hosting, configuration and request pipeline as well as its target framework. Microsoft migration guidance.
API identity has explicit application boundaries. In Entra-based applications, distinguish user sign-in, authorization scopes/app roles and the application’s own access to Azure resources. Use Microsoft.Identity.Web for protected ASP.NET Core APIs and managed identity for supported Azure service access; one does not replace the other. API guidance; managed identity.
Serverless still needs runtime and failure management. For C# Functions, learn the isolated worker model. Microsoft lists 14 September 2026 as the end of support for Functions runtime 1.x and 10 November 2026 for the .NET in-process model. Old Functions examples therefore need a runtime check before reuse. Current Functions guidance.
Delivery spans application and infrastructure code. GitHub Actions and Azure Pipelines support reviewed, tested deployments, including federated workload authentication and deployment recovery. Current delivery responsibilities extend beyond a Visual Studio publish operation or TFS server administration. AZ-400 objectives.
Observability must cross service boundaries. Application Insights remains relevant, while Microsoft’s Azure Monitor OpenTelemetry distribution provides current instrumentation. Correlate an incoming request with its downstream work rather than relying only on isolated exception logs. OpenTelemetry guidance.

How these skills map to Microsoft development today

These are editorial technology correspondences, not official certification replacements.

Historical knowledge	Modern application	Gap to investigate
C#, LINQ and .NET libraries	Modern .NET services and reusable application code	Package compatibility, Windows dependencies and changed APIs. Migration
ASP.NET MVC / Web API	ASP.NET Core controllers, Razor UI and HTTP APIs	Middleware, dependency injection, hosting and authorization. Learning path; Entra API
WCF and data-service contracts	HTTP APIs where appropriate; assessed migration for existing service consumers	Protocol compatibility, versioning and consumer expectations; an HTTP endpoint is not a drop-in SOAP service. Migration assessment
Azure services and asynchronous integration	Functions, Service Bus and managed application hosting	Trigger behaviour, duplicate delivery, current SDKs and identity. Functions; current cloud objectives
Docker and Azure deployment	Container Apps for suitable APIs and workers	Image lifecycle, revisions, scaling and application health. Hosting capabilities
TFS, ALM and testing	GitHub and Azure DevOps delivery	Repository policies, pipeline identity, artifact promotion and rollback. Current delivery objectives
Application Insights and troubleshooting	Azure Monitor with OpenTelemetry	Trace correlation and useful service-level diagnostics. Instrumentation
UWP client development	Assess Windows App SDK / WinUI modernization	UI/API differences and packaging; retain reusable logic where possible. Microsoft migration guidance

Where do I go from here?

MCSEDirectory recommendation: choose the branch that matches your recent work, then use a project with measurable behaviour to expose the remaining gaps. The learning sequences and exercises below are our recommendations, not Microsoft certification requirements.

If you remained a .NET developer

Likely direction: .NET application developer or application modernization engineer. Preserve domain modelling, C#, LINQ and testing skills. The main gap for a .NET Framework developer is often dependency and application-model migration, rather than basic programming.

Learning sequence: use Microsoft’s .NET upgrade guidance to inventory a familiar solution → separate portable business logic from Windows/framework dependencies → move one library and its callers to supported .NET → check serialization, date handling, database behaviour and asynchronous cancellation → compare results with the original application.

Concrete project: modernize an order-pricing component with tests for tax, rounding and discount boundaries, then expose the same behaviour through an ASP.NET Core endpoint. If Entity Framework is involved, measure the generated queries and transaction behaviour instead of assuming a provider change is harmless. Record dependencies that prevent migration and how callers remain compatible.

Use selected modules from Build web apps with ASP.NET Core for beginners for unfamiliar framework mechanics; an experienced developer can skip introductory C# material. This is a technology learning route, with no separate certification prerequisite. An AI-focused credential is useful only if you also want the additional AI work described below.

If web/API development became your main work

Likely direction: ASP.NET Core backend or full-stack developer. This branch builds directly on 70-486’s application/security work and 70-487’s HTTP-service design. Keep HTTP semantics, validation and debugging; add the modern request pipeline, dependency injection and explicit API authorization.

Learning sequence: complete the API-controller and Razor modules in the ASP.NET Core learning path → migrate one MVC/API feature → add Entra protection with Microsoft.Identity.Web → exercise authorization and error contracts in integration tests.

Concrete project: implement an order API with separate read and write permissions, an authenticated browser client and a database-backed update. Test missing/expired tokens, wrong audiences, insufficient permissions and concurrent edits. Preserve an existing client’s response contract while replacing its backend implementation. This demonstrates a more useful transition than merely returning a successful HTTP response.

No additional Microsoft credential is prescribed for this branch. The ASP.NET Core web app that consumes an API Applied Skills credential retired on 30 January 2026, so its old assessment must not be presented as a current target. The linked training remains a separate learning resource. Microsoft retirement register.

If you moved into Azure application development

Likely direction: Azure application developer or application integration developer. 70-487’s data/services work and the earlier 70-532 elective provide a specific foundation. The gaps are current Azure resource permissions, service limits, runtime choices and diagnosing failures across components.

Learning sequence: refresh ASP.NET Core and current Azure SDK use → host an API in App Service or Container Apps according to its needs → give the hosted application a managed identity → implement a C# isolated-worker Function → instrument the request and worker using Application Insights/OpenTelemetry. Keep human/API authentication separate from the worker’s service permissions.

Concrete project: accept an import request through an API, store its payload in Blob Storage and queue work in Service Bus. Have a Function validate the input and update an application database. Make retries safe with an import identifier and an explicit idempotency rule; test duplicate messages and a failed database write. Track the request through processing, expose a status endpoint and demonstrate recovery from a dead-lettered message. This builds directly on data access and asynchronous-service reasoning, while adding distributed-system operation.

For container experience, package the API, publish its image to Azure Container Registry and deploy two Container Apps revisions. Test a traffic shift and recovery to the previous revision. Learn Kubernetes administration if your platform responsibilities require it; operating a containerized application does not itself require running a cluster. Container Apps capabilities.

Current credential choice: Azure Developer Associate, formerly associated with AZ-204 — Developing Solutions for Microsoft Azure, retired on 31 July 2026. Azure AI Cloud Developer Associate is currently available and uses AI-200 — Developing AI Cloud Solutions on Azure. Its page lists no prerequisite certification, but expects Python, Azure SDKs, containers and vector-database knowledge. No retirement is announced in the pages checked. Status register; AI-200 objectives.

Choose AI-200 when AI backend development is your intended work. After the integration exercise, add Python and a retrieval service with stored embeddings, a defined evaluation dataset and measured query latency. AI-200 overlaps with Azure services, containers and monitoring, but its AI/data requirements go beyond MCSD’s C#/web foundation. A conventional .NET/API developer can follow the technology route without treating this credential as a required conversion.

If you moved toward DevOps/platform delivery

Likely direction: application delivery engineer, DevOps engineer or developer platform engineer. The earlier 70-496/497/498 electives and later 70-487 deployment work make this a justified branch for holders who actually worked with builds, tests and releases. Add cloud operation, deployment identity and environment management to the development foundation.

Learning sequence: review the current AZ-400 objectives → put an ASP.NET Core API’s tests and deployment configuration in Git → build and test through GitHub Actions or Azure Pipelines → publish a versioned artifact → deploy through a narrowly scoped federated identity → verify the deployed service and practise rollback.

Concrete project: deliver the order API and its Bicep-defined Azure resources through a pipeline. Block a deliberately broken change with integration tests, deploy a backwards-compatible schema change, then demonstrate that the previous application version still works. Correlate a failing release with Application Insights telemetry and recover using the previously built artifact. Explain which permissions belong to the pipeline and which belong to the application.

Relevant credential: DevOps Engineer Expert, with AZ-400 — Designing and Implementing Microsoft DevOps Solutions. The checked credential page requires Azure Administrator Associate OR Azure Developer Associate, plus AZ-400. Since Azure Developer Associate is retired, Azure Administrator Associate / AZ-104 is the clearly available prerequisite route for a new candidate. Its page lists no prerequisite certification. No retirement is announced for AZ-104 or AZ-400 in the sources checked. Administrator credential; retirement register.

The DevOps page still names the retired developer credential; it does not establish AI-200 as a substitute. If you already hold Azure Developer Associate, confirm your eligibility with Microsoft before relying on that award. MCSD itself does not satisfy the prerequisite. Microsoft also expects both Azure administration and development experience, and familiarity with GitHub and Azure DevOps. Current DevOps requirements.

If you want to move toward cloud architecture

Likely direction: application/cloud solution architect. Application boundary design, data contracts and deployment choices transfer; the earlier 70-534 elective makes this especially relevant for holders with Azure design experience. The main gap is broader operational design: networking, identity, governance, recovery and cost across the whole workload.

Learning sequence: close AZ-104-level administration gaps → assess a workload using the Azure Well-Architected Framework → design and prototype two hosting/integration options → measure their behaviour under load and partial failure → explain the migration and recovery plan.

Concrete project: compare an App Service API plus Functions worker with a Container Apps API and worker for the same import workload. Document message delivery guarantees, access boundaries, scaling limits, database recovery objectives and running costs. Test a worker outage and estimate how long the backlog takes to drain. Use those results to justify the design, including whether the extra components are warranted.

Relevant credential: Azure Solutions Architect Expert requires Azure Administrator Associate plus AZ-305 — Designing Microsoft Azure Infrastructure Solutions. No retirement is announced in the checked sources. App Builder and the historical 70-534 exam do not waive the current prerequisite. Treat this as a broader role change, with operational experience before the design exam.

If your background was UWP client development

Likely direction: Windows application developer, with web services as an adjacent skill rather than a compulsory career change. Preserve C# logic and client/service separation. Investigate Windows App SDK/WinUI migration according to the APIs, UI and packaging your application actually uses. Microsoft Windows migration guidance.

Learning sequence and project: assess a UWP application’s dependencies → move a reusable validation/service library → port one data-entry screen → check keyboard accessibility, app state and packaging → call a protected ASP.NET Core API and test expired sign-in and offline/error behaviour. Document Windows-specific features that need a different implementation. No current certification is asserted as an official UWP or App Builder equivalent.

For a holder whose earlier elective was SharePoint development, first identify how much of the application depends on SharePoint’s server object model. The web/API and integration branches can help with reusable service code, but they do not by themselves constitute a SharePoint migration plan.

Prerequisite relationships: MCSA: Web Applications and MCSA: Universal Windows Platform are documented above with their exact exam combinations; neither should be confused with an MCSD of a similar name.
Earlier awards: MCSD: Web Applications, Universal Windows Platform and SharePoint Applications appear in Microsoft’s 2016 transition rules. Programme slides.
Historical exam references: 70-483 data access, 70-486 web applications and 70-487 services help interpret the technologies behind a transcript.
Modern credential context: Azure Developer Associate is retained as a retired reference. Azure Administrator Associate is relevant to the expert prerequisite routes above.

Sources and methodology

Historical facts are drawn from Microsoft programme material, Microsoft exam objectives and Microsoft Press. Later award-rule clarification uses Microsoft Community Support, identified separately from formal programme documentation. Modern credential checks and technical learning resources come from Microsoft Learn. Pathway selection and all exercises are MCSEDirectory editorial recommendations. Reviewed: 7 September 2026.

Historical snapshots and source limitations

The October 2016 roadmap was downloaded from Microsoft and visually inspected: several important rules and exam numbers do not survive plain-text extraction. Page 11 labels its elective pool September 2016; page 1 dates the document 6 October. This supports the programme era, not an exact launch day. Pages 3–5 establish award, optional re-earning and transition rules.

The later three-elective rule is a January 2020 snapshot, corroborated by another Microsoft Support answer; it is not projected backwards over the whole programme. The January answer initially contains an inconsistent 70-483 reference, then explicitly confirms 70-357/486/487 and explains the no-reuse rule. A February 2019 moderator answer also mentions 70-480 as an unused elective. That is evidence of differing historical advice, but its effective period and complete pool remain unconfirmed; it is not merged into either verified snapshot. These support pages were available as indexed text when direct retrieval failed.

The 70-487 document shows tracked additions and deletions effective 15 January 2018. Its rendered pages were inspected to distinguish older WCF/server objectives from added Functions, Docker, API Management and monitoring content. The older document header says “Windows Azure”; the later programme exam title says “Microsoft Azure.” No single objective revision is attributed to every holder. Detailed objective versions for all early electives remain outside the verified scope.

The retirement notice retains June 2020 wording below its January 2021 extension, and contains an apparent 70-457 typo beside “Developing Mobile Apps.” The independent roadmap and Microsoft exam references identify that exam as 70-357. Transcript policy is linked separately rather than deriving an exact later transcript-movement date from the stale notice.

The modern credential pages and retirement register were checked together. The DevOps prerequisite page still lists Azure Developer Associate after its retirement; no unverified AI-200 substitution is asserted. Some old Functions learning-path URLs now redirect to the general catalogue, so this page links the current technical guide instead.

At a glance