Reference
Contacting Infralign
Where to write, and the one identifier that stops each kind of request bouncing back for more detail.
Almost everything goes to support@. Data-protection requests go to privacy@.
| Address | Use it for |
|---|---|
| support@infralign.ai | Connection problems, sign-in, dashboards and data, security review, commercial terms, anything else |
| privacy@infralign.ai | Data-protection requests: access, correction, erasure, and the deletion confirmation at offboarding |
No response-time commitment is published, because none has been agreed. If a turnaround matters to your process, raise it before you connect and get it in writing.
What to include
Section titled “What to include”Almost every slow support thread is one missing identifier. The sections below name what each kind of request needs.
An admin cannot reach the setup wizard
Section titled “An admin cannot reach the setup wizard”Send the tenant ID, the application ID, and the subscription IDs you want analysed. Infralign will agree a transfer method with you for the credential. Manual connection covers this path.
The connection is failing
Section titled “The connection is failing”Send the error code, the subscription ID it failed on, and which of the two roles you have assigned at which scope. If you ran the CLI probes, send the output of the one that failed. Check it against troubleshooting first: propagation delay accounts for most first-attempt failures and clears itself in ten minutes.
A person cannot sign in
Section titled “A person cannot sign in”Send the exact address they signed in with, your tenant’s directory ID, and the AADSTS code or the wording on the screen. An admin can resolve most of these on the People page without writing to anyone.
Your credential is in another Entra tenant
Section titled “Your credential is in another Entra tenant”The wizard refuses a credential from a tenant other than the one on your account. That is a default posture, not a limit. Ask for cross-tenant connections to be enabled on your account, naming both tenant IDs.
A dashboard or figure looks wrong
Section titled “A dashboard or figure looks wrong”Send the dashboard name, the as-of date it shows, the subscription, and the figure you expected. If a source reads STALE, include what the Data Ops dashboard says about it.
You want Teams notifications
Section titled “You want Teams notifications”Send an incoming webhook URL for the channel that should receive them. A person wires it up, and the channel then receives the monthly summary and cost alerts. No self-service field exists, and nothing is posted to you unless you ask.
Security review, DPA, or sub-processors
Section titled “Security review, DPA, or sub-processors”Read security and data handling first: it separates the controls that are implemented from the commitments still being prepared, and lists the open ones by name. Send the specific questions your review has to close, and agree the answers in writing before you connect a tenant.
Commercial terms and measurement method
Section titled “Commercial terms and measurement method”Scope, price, and delivery terms arrive in writing after the audit. To agree a measurement method, an exclusion, or a scope before an engagement starts, write to support and get the agreed wording back in writing. Savings measurement methodology is the document that gets amended.
Ending the connection
Section titled “Ending the connection”Ending the connection has the revocation steps, which you run yourself without asking anyone. Write to privacy@ for the deletion confirmation.