At TechEd and via email, I've had many questions about the future of Zero Touch Provisioning. Here's some information in an FAQ form:

1. Is it true that ZTP v3.0 is the last version? Why is Microsoft passing over this solution?

Answer: v3.0 is likely the last version to be called Zero Touch Provisioning. However, there's a Microsoft Services solution group project code named Provisioning 4.0 that is based on the ZTP 4.0 planned architecture. To be clear, Microsoft isn't missing out on this opportunity, rather we’re investing more into the solution development and marketing. Just remember, more investment means more project rigor and financial measurement, which can lead to delays or scope changes.

2. What is the future Provisioning strategy with future Microsoft products like System Center Service Manager and Identity Lifecycle Manager v2.0?

Answer: Provisioning 4.0 will continue to be a common request and workflow engine across the Windows Server System and across IT disciplines. As Microsoft's products evolve and adopt WF technology, Provisioning 4.0 should support even more cross product integration actions and new product hosting. The goal of Provisioning is to enable self-service and task delegation for any activity across the platform (software, service, or device). On the technology side, we're moving to Windows Workflow (just like our products) to match the common technical architecture direction for all workflow at Microsoft and plan to provide WF activities for our products.

3. OK, but I saw a demo of Self-Service Provisioning on Service Manager using Configuration Manager to deploy an application.

Answer: Yes, this doesn't preclude products from shipping SDK samples, adapters, or solutions for specific high-value scenarios. However, Provisioning 4.0 spans Deployment Management, Configuration Management, Identity Management, Operations Management, and Service Management. Ideally, Powershell automation and Provisioning Packs will become common engineering criteria like Management Packs.

A main tenet of Provisioning is to protect the solution investment while enabling our future products. This may mean that some functionality delivered today in custom code will be moved into product features, but the overall investment in the solution is preserved by expanding service definitions and integration scenarios. In other words, if you are solely concerned with provisioning for 1 IT discipline, then an eminent product may be a better choice, but each provisioning scenario decreases investment risk dramatically and pushes you toward Provisioning 4.0. In fact, Provisioning 4.0 could enable transitioning to future Microsoft products faster.

4. So, who owns Provisioning at Microsoft?

Answer: Today, Provisioning is a Microsoft Services solution, now owned by the formal solutions group. However, it is not farfetched to picture certain Provisioning Packs as SDK samples, adapters, or solution accelerators licensed for specific products. In the long run, I hope to see Provisioning as a common product feature with a shared architecture across the Windows Server System.

5. What does this mean for David?

Answer: I’m not sure, but I may not be working on Provisioning for much longer. The solutions group has Architects, Program Managers, Development Managers, Product Managers, and teams of developer/test resources. Ironically, it’s not clear that there is room for me. I’ve been working on Provisioning since 2003, both with world class resources like Brandon (Danny and Graham, or Nilesh, Balaji, and Dave) and sometimes by myself. It’s very satisfying and scary to see my vision take hold and live beyond my control. Perhaps it’s time to let Provisioning fly without me. Then again, it would be awesome to work with the various business groups to more formally productize Provisioning.