add-global-variable

To create global variables in Copilot Studio, you define variable properties like name, scope, visibility, and default values through YAML configuration. This enables cross-topic conversation state persistence so data remains accessible across different topics.

Cross-topic state persistence allows you to store and retrieve variables across different topics within the same conversation. You need it when maintaining user preferences, tracking conversation progress, or storing dynamic URLs for knowledge sources across topic transitions.

Yes, you can customize global variables in Copilot Studio by defining variable names, descriptions, visibility to the AI orchestrator, and default values. This customization is handled through YAML configuration during variable creation.

You set up a persistent variable by providing the variable name, such as 'LastVisitedCity', and a default value, like 'Unknown'. The variable is then created using YAML configuration, allowing you to store and retrieve user preferences across topics.

No, the add-global-variable skill requires no external dependencies to manage conversation state. It operates independently within Copilot Studio, using YAML configuration to handle variable creation and cross-topic state persistence.

Copilot Studio agents lose variable data between topics because standard variables are topic-scoped. You need global variables configured via YAML to maintain cross-topic state persistence, ensuring data remains available throughout the entire conversation.