GraphWarden-compatible partners

This page lists third-party products whose vendors have published a GraphWarden compatibility statement. Inclusion here reflects a vendor-published declaration, not a GraphWarden-issued certification. To appear on this page, complete the compatibility statement template and contact us.

Help me publish a GraphWarden compatibility statement for my product and request inclusion in the partners list.

My product calls Microsoft Graph and reads the Graph base URL and credentials from configuration. I have reviewed the compatibility guide at https://graphwarden.com/docs/isv/compatibility-guide and run the eight-step test checklist.

I need:
1. Review of my draft compatibility statement against the template at https://graphwarden.com/docs/isv/compatibility-statement
2. The email address or form to send the URL of my published statement for partner-list review
3. An expected timeline between submission and link-check completion

Reference documentation: https://graphwarden.com/llms.txt

Ask me for my product name, my published statement URL, and the Graph endpoints my product uses.

How this list is maintained

The partner list reflects vendor-published declarations. The flow below describes how an entry lands on the table and how it stays there.

1. A vendor publishes a GraphWarden compatibility statement on their own documentation site, using the compatibility statement template as the base.
2. The vendor contacts GraphWarden with the URL of the published statement, the product name, and a short description.
3. GraphWarden runs a link check against the submitted URL. If the page resolves (HTTP 200) and contains the four required sections from the template (integration overview, supported Graph endpoints, known limitations, customer responsibilities), the entry is added in the next docs release.
4. The partner table below is the canonical list. Entries are added in alphabetical order by product name.

GraphWarden does not test the partner's product. The partner self-declares compatibility by publishing the statement; the curation on this page is limited to confirming the statement exists and matches the template's scope.

Listed partners

The table above is a placeholder. When vendors submit their statements, entries replace this row in alphabetical order by product name.

How to appear on this list

The four-step process below takes a vendor from first reading the compatibility guide to landing on this page.

1. Read the compatibility guide. Confirm your product reads the Graph base URL and credentials from configuration. Run the eight-step test checklist against a GraphWarden test instance.
2. Publish your compatibility statement. Copy the template, replace the {curly brace} markers with your product specifics, and publish the result under your own documentation site. A title like "{Your product} compatibility with GraphWarden" works well for discoverability.
3. Contact GraphWarden with the URL. Email the URL of your published statement, your product name, and your primary support contact to the address listed at the bottom of this page.
4. Link-check and addition. GraphWarden confirms the URL resolves and that the statement matches the template's four sections. Once confirmed, the entry lands in the next docs release. You receive a confirmation email with the published entry.

The entire flow is documentation work on the vendor side plus a link check on the GraphWarden side. There is no contract, no fee, and no technical integration with GraphWarden infrastructure — your product never talks to GraphWarden directly.

Removal policy

Entries remain on the list as long as the published statement resolves at the URL the vendor submitted. The curation process applies two removal rules.

• Statement URL returns 404 for more than 30 days. GraphWarden runs a periodic link check against every listed URL. A URL that returns 404 on three consecutive weekly checks is flagged; the vendor receives an email at the contact on file. If the URL does not resolve within 30 days of the first failed check, the entry is removed from the table.
• Vendor requests removal. A vendor can request removal at any time by contacting GraphWarden from the address on file. Removals are processed in the next docs release.

A vendor whose entry was removed can resubmit once the statement URL resolves again — the rejoining flow is the same as the initial submission.

Troubleshooting

The entries below cover the questions vendors ask most often during the submission flow.

My statement submission was rejected

The most common rejection reason is warranty language that GraphWarden cannot endorse on the partner's behalf. Phrasing that reads as a blanket commitment or a forward-looking guarantee lands as "GraphWarden endorses this product indefinitely" — which is not a commitment GraphWarden can make for a third-party vendor. Rework the wording to describe what your product does ("{Product} reads the Graph base URL from configuration and routes calls through the configured endpoint") rather than what it guarantees. The template models the acceptable tone.

My statement URL changed

Contact GraphWarden with both the old URL and the new URL from the address on file. The entry updates in the next docs release; there is no interruption to your listing as long as the new URL resolves when the change is submitted.

I want my entry removed

Contact GraphWarden from the address on file and request removal. Removals are processed in the next docs release. If the address on file has changed, include the entry name and a proof-of-ownership reference (for example, a mention on the vendor's primary support page linking to this list).

My product version changed in ways that affect compatibility

The published compatibility statement should reflect the current supported version range. Update the {Minimum version} section in your published statement and — if the change is material — notify GraphWarden so the Last verified column reflects the re-verification date. Minor version bumps without a compatibility change do not require a re-verification.

Last reviewed: April 19, 2026