New Keys, New Process: Submitting Forms to SharePoint

Microsoft fully retired Azure Access Control Service (ACS) on April 2, 2026. For agencies running Adaptive Forms that submit to SharePoint lists, that retirement would have broken the Client ID/Client Secret connection method every one of those forms relied on. Ahead of the deadline, DoIT Web Services worked directly with every affected agency to migrate existing forms to a new architecture — every form that was live before the change has already been updated, tested, and confirmed working. The Forms section of the Author Guide has now been fully updated to match, for anyone building or modernizing a form going forward.

Forms no longer connect to SharePoint directly. Every submission now goes through a central AEM servlet, which hands off to a Microsoft Power Automate flow that writes the record to the correct SharePoint list. The result for authors is actually simpler:

• Submit Action is now Submit to REST endpoint, POSTing to /bin/forms/submit
• No credentials are entered on the form, ever. Authentication is handled centrally — there's nothing to register with SharePoint yourself
• A hidden Title field on the form now serves as the routing key, set to a slug (af-{agency}-{form-name}) that DoIT Web Services provides when your route is configured

The new architecture isn't just a like-for-like swap — it added capability the old Client ID/Secret method never had:

The build order has flipped. You no longer register anything with SharePoint before you can start — build your form and your destination SharePoint list first, then hand off to Web Services to get routed:

1. Build your Adaptive Form and your destination SharePoint list, matching your form field Names exactly to your SharePoint column FieldIDs (still required, case-sensitive)
2. Contact Web Services with your SharePoint site URL and list display name
3. Web Services configures the route and sends you your form's Title slug
4. Test, then publish

The Forms section has several new and updated pages worth a look, even if you're not actively building a form right now:

• Pertinent Information to Submit to SharePoint List — the full rewrite: current submission setup, column-naming rules, and five documented failure patterns (character limits, boolean columns, multi-select columns, date formatting, and the Terms & Conditions component's known nested-boolean issue) with resolutions for each
• Document of Record — new page covering auto-generated vs. template-based Document of Record setup, including full step-by-step template binding
• Scribble Signature — new component page walking through both signature setup paths
• Do You Need a Signature? and Categorizing Your Forms for Modernization — new planning pages for anyone auditing or modernizing a batch of existing forms

Every form that was submitting to SharePoint before the ACS retirement is already running on the new process — no action needed there. Going forward, this is simply how form submissions to SharePoint work: no credentials to register, a routing handoff to Web Services once your form and list are built, and now an audit trail and dead-letter recovery behind the scenes if something ever does go wrong. Building or modernizing a form? Start with the guidance linked above.