diff --git a/msal-dotnet-articles/how-to/token-cache-serialization.md b/msal-dotnet-articles/how-to/token-cache-serialization.md
index b2e7ce530..1f66727cf 100644
--- a/msal-dotnet-articles/how-to/token-cache-serialization.md
+++ b/msal-dotnet-articles/how-to/token-cache-serialization.md
@@ -565,7 +565,7 @@ When using a token cache, it's important to consider the potential size of the c
 
 ### Application
 
-- Access tokens are about 2-3KB; 1 token per _app client ID_ \* number of tenants \* downstream resources.
+- Only access tokens are cached. One token about 2-3KB when persisted. There will be 1 token per _app client ID_ \* tenants \* downstream resources. For example a multi-tenanted app serving 1000 tenants and needing tokens for Graph and SharePoint will use: 3KB * 1000 * 2 i.e. approximately 6 MB.
 
 ### User