support

Channels, scope, and what to send.

channels

Email

{{SUPPORT_EMAIL}}

Default channel. Target first response: {{SUPPORT_SLA_FIRST_RESPONSE}}.

Issue tracker

{{ISSUE_TRACKER_URL}}

For reproducible bugs and documentation errors, including the wiki.

Marketplace support

Billing and entitlement problems go to the marketplace you bought through. Where to buy →

scope

in scope: Installing and running the module. Provider behaviour that differs from the catalog. Verdicts that look wrong. Runbooks that do not match the target platform. Documentation errors.
out of scope: Fixing your Kerberos for you. Changes to AD on your behalf. Reading or regenerating keytabs, which the product itself refuses to do.
evaluation: Evaluation users: {{EVAL_SUPPORT_POLICY}}

what to include in a report

The run ID and module version are on every record the product writes. Include them and the -Verbose output of the failing command. Redact hostnames if you must, but keep the SPN shape: class, host form (FQDN or short), and whether a port was present.

collect

Get-Module SpnManager | Select-Object Version$PSVersionTable.PSVersionInvoke-SpnLifecycle -ProviderId <id> -WhatIf -Verbose 4>&1 | Tee-Object report.txt# plus: run ID, provider ID, expected vs actual, redacted as needed