Cloud Cache technology allows storing multiple copies (per Microsoft, the practical limit is 4) of Profile Containers on SMB file shares and keeping its data in sync without the need to deploy complex replication infrastructure. Note though that logon and logoff delays may impact the user experience.
Examples of usage:
Keeping copies of profiles in several storage locations (disaster recovery data center).
Replicating data to the more cost-effective storage.
Migrating from one storage location to another.
To configure multiple Cloud Cache locations (corresponds to CCDLocations setting), simply add them using the [+] button on the User Profile tab.
Profile Container will read data from a provider if the data needed does not already exist in the Local Cache file. When configuring Cloud Cache locations, the order Providers are listed defines the order Profile Container uses them for reading. If the first path specified is unavailable, then Profile Container will attempt to read from the second Provider and so on.
Cloud Cache will always write to all Providers specified in CCDLocations, unless a specified Provider isn't available.
Because the Local Cache file will service most I/O requests, the performance of the Local Cache file will define the user experience. It is critical that the storage used for the Local Cache file is high-performing and highly available. It is also suggested that any storage used for the local cache file should be a physically attached storage or have reliability and performance characteristics that meet or exceed high-performing physically attached storage. When using Cloud Cache, FSLogix profiles can be stored on Azure Files as well as directly on Azure Page Blobs. For Azure Page Blobs, it is important to secure sensitive Azure credentials by using Credential Manager. This is explained in Chapter 3.