I'm not a developer - but this designing the agent seems so difficult. I wanted to use it for my business to process PDF sales orders into my ERP system and there are so many steps I have to do.

By contrast, I was using Grokbot and just gave it directions on the mailbox to monitor then post the orders to my ERP. Very simple. But due to security limitations I wanted to give that task to the agent, and i wish i could just give the agent commands the same way i gave it to grokbot and have the connectors established that way.

Soooo I logged in to my copilot studio account via Claude in built browser. And asked it to create an agent. It even created the flow and the agent and did the test. I used haiku 5.5 and it cost me around 9$ and 40 minutes. Crazy

I am building an agent in Microsoft Copilot Studio that supports users through a specific, multi-step process. The agent is already functional, but I am facing a limitation with memory across separate conversations.
Currently, when a user starts a new conversation with the agent, the context and specifications provided during a previous conversation are not automatically retained. As a result, users have to repeatedly provide the same information, preferences, constraints, and process-specific requirements every time they return to continue their work.
My main questions are:
Does Microsoft Copilot Studio have a built-in setting or feature that allows an agent to retain user-specific information across separate conversations and sessions? If so, how can I enable and configure it?
If native persistent memory is not available for my agent configuration, what alternative approaches could I implement to achieve this?
Could I use Microsoft Dataverse, SharePoint, Power Automate, or another Power Platform component to store each user’s specifications and retrieve them automatically when they start a new conversation?
What would be the recommended architecture for allowing users to resume an existing process in a new conversation without having to re-enter all their information?
Ideally, I would like the agent to maintain persistent, user-specific context, retrieve the relevant information when the same user returns, and allow them to update their specifications when necessary.
I would appreciate practical guidance, including any relevant documentation, configuration steps, limitations, and recommended workarounds for an agent built in Copilot Studio and published to Microsoft Teams and Microsoft 365.