> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/known-limitations.md). # Known Limitations This page collects known product limitations, gaps, and recurring issues surfaced through real support cases — things Augmentt currently can't do, known bugs support has acknowledged, or workarounds given in place of a fix. It's organized by product area. Each entry notes roughly when it was last confirmed, since some of these may be resolved by the time you read this — if something below doesn't match what you're seeing, it may have shipped a fix since; check the [Release Notes](#) or ask support to confirm current status. ## Discover * **Exported reports drop Department and Job Title data.** Exporting an Application Usage or employee report to XLSX/CSV includes Department and Job Title columns, but the values are blank — even though those same fields work fine as filters in the web UI. As of June 2026, this was still open with Engineering. * **"Export All Companies" doesn't export all companies.** Exporting Application Usage data with the All Companies scope only produces a subset of tenants rather than the full list. As of February 2026, this was still open with Engineering. ## Engage * **Offboarding does not remove M365 licenses.** The Engage offboarding workflow does not unassign a departing user's Microsoft 365 licenses, and there's no toggle to make it do so — you still need to release the license manually in the M365 admin center after running an offboarding. As of May 2026, this was open with Engineering with no workaround beyond doing it manually. * **User email/name corrections may not propagate.** In at least one case, correcting a user's email address in Augmentt showed as a successful change but the update never actually reached Microsoft 365, even after multiple syncs — it needed a manual fix in the M365 admin center. This was from January 2026 and we don't have confirmation it's a systemic, ongoing issue rather than a one-off — flagging it as something to watch for if a change "sticks" in Augmentt but the tenant doesn't reflect it. ## Monitoring & Alerts * **The "Broken Integration" alert doesn't fire for tenants using Microsoft Entra PIM.** If a tenant has Privileged Identity Management (PIM) enabled, a stalled direct integration can go undetected — one customer had a month-long monitoring gap with no alert raised. As of March 2026, this was open with Engineering. If a PIM-enabled tenant has been quiet longer than expected, don't assume "no alert" means "healthy" — check the integration status directly. ## Reports * **No cross-tenant view of per-user MFA methods.** You can see which authentication methods (SMS, Voice, Authenticator, etc.) each user has registered from the MFA Report's detail view, but only one company/tenant at a time — there's no "All Companies" rollup. For an MSP needing to audit, say, which customers still have users on SMS/Voice ahead of Microsoft's retirement of those methods, this means opening every tenant individually. As of August 2026, support confirmed this limitation and escalated it to Product; no ETA. * **Inactive Accounts counts can disagree between reports for the same tenant.** The Threat Report's "Inactive Accounts" figure and the Compliance Audit's "Inactive Accounts" posture check can report materially different numbers for the same tenant on the same day (one real case showed a 124-account gap), because the two reports run different underlying queries/scopes. As of August 2026, this was open with Engineering — if you see a discrepancy, treat it as a known inconsistency rather than a data-accuracy problem with your tenant, and don't assume either number alone is authoritative until it's resolved. ## Secure — Posture Templates * **Deleted User OneDrive Retention doesn't reliably apply via Posture Templates.** Setting this value inside a Posture Template (e.g. to 93 days) and running the template against a tenant may not actually change the tenant's posture, and the template can also fail to save the new value at all (showing "No Change" instead). This has recurred across multiple cases from at least October 2025 through February 2026. **Workaround:** set the retention value directly on the tenant's individual posture check rather than relying on the template to push it. ## Secure — Intune * **Templating doesn't support app types that require an uploaded installer.** In the Intune Apps template-creation flow, any app type requiring an uploaded installer binary — Win32 apps, Windows MSI line-of-business apps, AppX/Windows Universal AppX, macOS PKG/DMG/LOB apps, and iOS/Android line-of-business apps — is blocked from being saved as a template, showing "Creating templates for line-of-business apps is not supported right now." Only pure-metadata apps (store apps, web links, VPP apps) can be templated today. Confirmed directly in the Augmentt codebase, August 2026 — the check is client-side with no backend guard, and there's no TODO or feature flag suggesting this is temporary. ## Integrations (PSA / CSP) * **PSA/CSP sync interruptions recur as a pattern, not just isolated incidents.** "CW and CSP integrations are not syncing"-type reports have come in independently several times (ConnectWise and CSP-tenant syncing, most recently August 2026, also seen in December 2025). None of these point to one root cause we could confirm as still open, but the recurrence itself is worth knowing: if a tenant stops updating, it's worth checking integration health rather than assuming it's a one-off blip. ## Resolved — included for context, not current * **Intune App Protection Policies (iOS/Android) were not manageable in Augmentt** prior to the 2026.4.2 release (a support case from December 2025 confirmed this gap and that it had been raised with Product). This has since shipped — Augmentt's Intune module fully manages App Protection Policies as of the 2026.4.2 release. Listed here only so this page doesn't get "rediscovered" as a still-open gap; if you're on a release older than 2026.4.2, this may still apply to you. *** ### A note on "Possible Limitations" (GDAP) You'll see "Possible Limitations" as a status on the CSP Setup page fairly often in support history — this is **not** one of the product gaps above. It's a normal GDAP readiness indicator meaning a tenant's GDAP relationship is missing a role or permission a newer Augmentt feature needs (for example, Intune App Protection Policies added a new required Graph permission in 2026.4.2). It's resolved by updating the GDAP relationship, not by a product fix — see [Submit a Support Ticket](/submit-a-support-ticket.md) if you're not sure how. *** *This list reflects a sample of Salesforce support cases pulled in August 2026 and is not exhaustive. Treat anything not re-confirmed recently as a starting point for a support conversation, not a guarantee.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helpdesk.augmentt.com/known-limitations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.