ProfileUnity ships a built-in portability ruleset for New Teams (Microsoft Teams 2.x) that covers standard commercial tenants. Organizations running Microsoft Teams in a DoD or GCC High tenant require a modified ruleset because Teams writes WebView2 profile data to a different folder. This article explains the difference and shows how to add or import the DoD ruleset.
Background — Why Two Rulesets?
New Teams (2.x) uses Microsoft's WebView2 browser engine to render its UI. WebView2 stores per-session cache data — GPU shader cache, code cache, service worker cache, web storage, and so on — inside a named profile folder under the Teams LocalCache directory:
| Teams Tenant Type | WebView2 Profile Folder |
|---|---|
| Commercial / standard | %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw |
| DoD / GCC High | %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_DoD |
These cache folders are large, session-specific, and should never roam. The portability ruleset must explicitly exclude them so they are not captured into the user's profile. The standard ruleset only excludes WV2Profile_tfw. In a DoD/GCC High environment the profile folder is WV2Profile_DoD, so its cache is captured and roamed unless the DoD ruleset is used instead.
WV2Profile_DoD and WV2Profile_tfw so it is safe to use in mixed environments where some users may access both tenant types.Rule Comparison
Both rulesets target %LOCALAPPDATA% (Folder ID 12). Include rules capture the path into the roaming profile. Exclude rules suppress a sub-path so it is never captured.
Rules identical in both rulesets
| Operation | Path (relative to %LOCALAPPDATA%) | Purpose |
|---|---|---|
| Include | Packages\MSTeams_8wekyb3d8bbwe | Captures Teams MSIX package local data |
| Include | Publishers\8wekyb3d8bbwe | Captures Teams publisher shared data |
| Include | Publishers\8wekyb3d8bbwe\TeamsSharedConfig\app_switcher_settings.json | Roams app switcher preferences |
| Include | Publishers\8wekyb3d8bbwe\TeamsSharedConfig\tma_settings.json | Roams Teams machine-wide app settings |
| Exclude | Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs | Suppresses Teams log files |
| Exclude | Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\GrShaderCache | Suppresses GPU shader cache |
| Exclude | Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs | Suppresses performance logs |
| Exclude | ...\EBWebView\WV2Profile_tfw\Cache | Suppresses commercial WebView2 HTTP cache |
| Exclude | ...\EBWebView\WV2Profile_tfw\Code Cache | Suppresses commercial JS/WASM code cache |
| Exclude | ...\EBWebView\WV2Profile_tfw\GPUCache | Suppresses commercial GPU cache |
| Exclude | ...\EBWebView\WV2Profile_tfw\Service Worker\CacheStorage | Suppresses commercial service worker cache |
| Exclude | ...\EBWebView\WV2Profile_tfw\Service Worker\ScriptCache | Suppresses commercial service worker scripts |
| Exclude | ...\EBWebView\WV2Profile_tfw\WebStorage | Suppresses commercial web storage |
| Exclude | Publishers\8wekyb3d8bbwe\TeamsSharedConfig\tmp | Suppresses Teams shared config temp files |
Rules added only in the DoD ruleset
The DoD ruleset adds six additional Exclude rules that suppress the equivalent cache paths under WV2Profile_DoD:
| Operation | Path (relative to %LOCALAPPDATA%) | Purpose |
|---|---|---|
| Exclude | ...\EBWebView\WV2Profile_DoD\Cache | Suppresses DoD WebView2 HTTP cache |
| Exclude | ...\EBWebView\WV2Profile_DoD\Code Cache | Suppresses DoD JS/WASM code cache |
| Exclude | ...\EBWebView\WV2Profile_DoD\GPUCache | Suppresses DoD GPU cache |
| Exclude | ...\EBWebView\WV2Profile_DoD\Service Worker\CacheStorage | Suppresses DoD service worker cache |
| Exclude | ...\EBWebView\WV2Profile_DoD\Service Worker\ScriptCache | Suppresses DoD service worker scripts |
| Exclude | ...\EBWebView\WV2Profile_DoD\WebStorage | Suppresses DoD web storage |
Adding or Importing the DoD Ruleset
The standard New Teams - 6.8.7 ruleset is built into ProfileUnity and appears automatically under Portability → Portability Rulesets. The DoD variant is not included by default and must be added manually or imported from the provided JSON file.
Option A — Import from JSON
- In the ProfileUnity Management Console, navigate to Portability → Portability Rulesets.
- Click Import and select the
New Teams - 6.8.7 - DoD.jsonfile. - Confirm the import. The ruleset named New Teams - 6.8.7 - DoD will appear in the list.
- Assign the ruleset to the appropriate configuration or user filter in place of (or in addition to) the standard ruleset, depending on your environment.
Option B — Add the extra exclude rules manually
- Open the existing New Teams - 6.8.7 ruleset (or clone it and rename it to New Teams - 6.8.7 - DoD).
- Add six new Exclude filesystem rules, each targeting Local AppData (Folder ID 12), with the paths listed in the DoD-only rules table above.
- Save and assign the ruleset as appropriate.
Use the standard ruleset for environments where all users connect to a commercial Microsoft 365 tenant. Use the DoD ruleset for environments where users connect to a DoD or GCC High tenant — it includes all the same rules as the standard ruleset plus the additional DoD cache exclusions, so it is a drop-in replacement.
| Product | Liquidware ProfileUnity with FlexApp |
| Applies To | ProfileUnity 6.8.7 and later |
| Updated | June 30, 2026 |