> For the complete documentation index, see [llms.txt](https://docs.secure-contacts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.aadcache.md). # SCA Configuration - SecContacts.AADCache ### SecContacts.AADCache This setting enables an optional AAD Cache as a data source for AAD contacts, significantly improving performance and user experience in large AAD environments. * Name: `SecContacts.AADCache` * Value: `[{"name":"AADCache", "value":""}]` Replace `` with the key generated by AAD Cache. * e.g. `XcTAQTzgO00KQE+Dkr{...}FnxMDuzJ6xI=` ### AAD Cache Overview The AAD Cache feature leverages an Azure Function together with Azure Blob Storage to significantly improve sync performance in large AAD environments. Instead of having SCA pull all AAD contacts sequentially via Graph API - which can be time-consuming -the AAD Cache performs this operation periodically and provides a single encrypted and compressed file through Azure Blob Storage. This approach reduces sync time dramatically and enhances the overall user experience. Download AAD Cache Azure Function: Contact us for details. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.aadcache.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.