Skip to content

docs: add bring-your-own-provider Twilio adapter guide - #47

Merged
Hou (SciencePotato) merged 7 commits into
Azure-Samples:mainfrom
SciencePotato:houchichan-microsoft-bring-your-own-provider-guide
Oct 13, 2026
Merged

Hou (SciencePotato) merged 7 commits into
Azure-Samples:mainfrom
SciencePotato:houchichan-microsoft-bring-your-own-provider-guide

Conversation

@SciencePotato

@SciencePotato Hou (SciencePotato) commented Oct 13, 2026 •

Copy link
Copy Markdown
Collaborator

What changed

Add a short repository checklist for connecting a customer-owned phone provider, with Twilio mentioned only as context. The guide explains what to change here; the customer works out their provider integration separately.

  1. Choose one language.
  2. Create the provider file and register it in the runtime's factory, DI registrations, or provider dictionary.
  3. Configure credentials and app settings using the existing settings sample and code locations.
  4. Add and run tests.
  5. Package and deploy the changed source.

An optional final section points to the provider profile, catalog, setup module, infrastructure, package selection, and setup tests for teams maintaining their own guided setup integration.

The guide distinguishes the JSON files clearly: local.settings.sample.json supplies host environment settings; setup profile/catalog JSON supplies deployment choices and values. Neither creates or registers a runtime adapter. Adding a JSON file alone does not make a provider supported by guided setup.

The previous vendor API details, endpoints, credential formats, request/response specifics, and reference list have been removed rather than moved elsewhere. There are no inline code or JSON examples. Existing file links give customers the starting points they asked for.

Review and verification

Three passes checked the ordered customer flow, actual repository/configuration responsibilities, and final plain-language rendering. The coordinating reviewer read the complete shortened guide and navigation changes; 401 local targets and 156 anchors pass. Existing language and legacy links are preserved.

The guide is now 149 lines rather than the previous roughly 374-line implementation walkthrough. The root README is unchanged by this revision, and its navigation remains provider-neutral.

Documentation only: no runtime, setup catalog, cloud configuration, or provider actions. This is a custom integration checklist, not built-in Twilio support or a claim of successful deployment.

Reviewed head: 63300e0. Open for review; no merge requested.

Hou Chi Chan and others added 7 commits October 13, 2026 11:13
Document sample-specific SMS and voice adapter examples for JavaScript, .NET, and Python, credential wiring, safety boundaries, and customer validation. Link from existing developer documentation without adding runtime or guided setup support.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: af0a60fe-cd74-4bfa-89a7-426b1a9b4549
Replace inline adapter implementations with precise repository extension-point links and current official Twilio references. Add ordered prerequisites, input checks, per-runtime changes, safety and acceptance checkpoints; update navigation wording while preserving language anchors and the provider-neutral root.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: af0a60fe-cd74-4bfa-89a7-426b1a9b4549
Keep existing app-setting names but describe custom account, sender, and vault inputs without inventing Twilio configuration examples.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: af0a60fe-cd74-4bfa-89a7-426b1a9b4549
Separate input planning from live credential provisioning, make each main step's owner/location/completion and next action explicit, and spell out customer deployment and protected acceptance checks. Preserve instructions-only guidance and language links.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: af0a60fe-cd74-4bfa-89a7-426b1a9b4549
Replace repeated ownership and checkpoint templates with direct instructions and smoother transitions. Keep numbered steps, exact source references, testing and customer deployment work, and the existing integration limits without inline samples.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: af0a60fe-cd74-4bfa-89a7-426b1a9b4549
Remove vendor protocol material and focus on adapter files, registration, existing settings JSON, credentials, tests, and custom packaging/deployment. Explain optional guided profile/package wiring without implying JSON installs an adapter. Update navigation labels and preserve language anchors.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: af0a60fe-cd74-4bfa-89a7-426b1a9b4549
@SciencePotato
Hou (SciencePotato) merged commit cafd8a8 into Azure-Samples:main Oct 13, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants