Copilot for Security Tip: Conserving SCUs by Utilizing Prompt History in the Standalone Experience
The My Sessions feature caches previous prompting activites
As more organizations discover the value of utilizing Copilot for Security to augment daily security operations, they may want to identify ways to minimize SCU usage.
One way is to utilize the My Sessions list in the standalone experience for Copilot for Security. This list represents prompts that have already been shuffled through the system and have already monopolized consumption. Of note, this list ALSO includes Promptbooks that have been run.
For another way, see: Scheduling Microsoft Copilot for Security Capacities - Control costs associated with Microsoft’s new AI tool
When a session from the list is accessed, it immediately displays stored responses from the previous sessions without utilizing any additional SCU consumption.
You can access My Sessions directly from the hamburger menu in the standalone experience.
Want to discuss this further? Hit me up on Twitter or LinkedIn]
[Subscribe to the RSS feed for this blog]
[Subscribe to the Weekly Microsoft Sentinel Newsletter]
[Subscribe to the Weekly Microsoft Defender Newsletter]
[Subscribe to the Weekly Azure OpenAI Newsletter]
[Learn KQL with the Must Learn KQL series and book]
[Learn AI Security with the Must Learn AI Security series and book]