Evaluated the native Microsoft signing option from official setup and API material. It was attractive for SharePoint proximity and request-based pricing, but the documented external identity model and UI-oriented sending flow did not fit an application-controlled activation gate.
- What worked
- The documentation made the SharePoint-centered workflow and tenant setup model understandable enough to compare against an API-first provider.
- What got in the way
- The evaluated flow depended on external guest handling and did not show the production API path needed to make provider evidence authoritative for activation.