Coming soon: Export and import assistant packages

Download an assistant as a portable package to move it to another instance, share it, or edit it as JSON. You can include knowledge files when the package meets the file limit.

Important: Importing a package can change an existing assistant. Export a backup first, then review the imported settings before saving.

Before you start

Make sure you have permission to edit the assistant and can save the package in an approved, secure location.

Export a package before making significant changes.
Do not include secrets, API keys, or passwords in assistant instructions or files.
Check whether connected tools, integrations, and organisation-specific settings need to be configured again after import.

Download a package

Open the assistant you want to copy or back up.
Select Edit assistant.
In the left-hand menu, under Publishing, select Package.
Choose the package options you need.
Select Download package.
Save the .zip file in an approved location.

Use a clear file name that identifies the assistant, version, and export date. For example: customer-support-assistant-v2-18-sep-2026.zip.

Choose what to include

Package format

Select Package (.zip) to download a portable package. The package can carry the assistant and its knowledge files, so importing it can restore the assistant configuration and included knowledge files. Other attached files are included too.

Include knowledge files

Select Include knowledge files when you want to include the assistant’s knowledge files in the package.

A package can include up to 100 knowledge files. If the assistant has more than 100 knowledge files, export the package without them.

When knowledge files cannot be included:

The package still lists the knowledge files.
After importing, the import process reports which files you need to upload to the new assistant manually.
Upload those files to the imported assistant before relying on its knowledge responses.

View the package schema

Select Schema to download or view the package schema. Use the schema when you need to inspect or edit the package as JSON.

What is not included

A package carries the assistant configuration. Some settings belong to the source instance and stay behind.

Setting	What happens when you import
Credentials	MCP authentication, custom headers, API keys, and OAuth secrets are not included.
Tenant connections	Connections such as Business Central and Dataverse identify the source tenant, so their connection data is not included.
Sharing	An imported assistant starts private to the person who imported it.
MCP servers	Servers are matched by label. The destination instance must already have the server, or the assistant is imported without it.
Global skills	Global skills are matched by name. The assistant’s own skills are different: their bundles are included in the `.zip` package.
Provider IDs	Files are uploaded and indexed again during import. Search works, but the underlying provider IDs are different.
Certification	Certification is set by the destination tenant’s administrators and is not inherited.
History	Conversations, usage, favourites, and pins are not part of the assistant configuration.
Drive Sync	Drive Sync names folders in the source tenant’s Microsoft 365 environment. Review and configure it for the destination tenant.

Choose a model for the destination

Under Model on the destination, choose how the imported assistant should select its model.

Option	When to use it
Use the destination’s default model	Use this when moving or sharing an assistant with another instance. It is the most portable option because the assistant uses the model available in the destination.

Import a package

Create a new assistant, or open the assistant you want to update.
Select Edit assistant.
Open the assistant’s Package settings.
Select the option to import a package.
Choose the exported .zip package.
Review the imported settings and any reported knowledge files.
Upload any knowledge files that were not included in the package.
Reconnect required credentials and tenant connections.
Check MCP servers, global skills, sharing, certification, and Drive Sync settings.
Select Save changes.

Test changes safely

Download a package from the current assistant.
Create a separate test assistant.
Import the package into the test assistant.
Make and test your changes in the test assistant.
Check responses, tools, permissions, integrations, and knowledge files.
Download a package from the tested assistant when you are ready.
Import the tested package into the production assistant, or apply the approved changes manually.

Use clear names such as Customer support assistant – test and Customer support assistant – production to avoid editing the wrong assistant.

Check after importing

Instructions — confirm they are current and suitable for the new purpose.
Model — confirm the selected model is available in the destination instance.
Knowledge files — upload any files reported as not included in the package.
Credentials and tenant connections — reconnect and reauthorise them where required.
MCP servers and global skills — confirm matching servers and skills are available in the destination.
Sharing and certification — set these again for the destination tenant.
Drive Sync — review source folders and configure destination Microsoft 365 folders.
Schedules and automation — check jobs before they run.
Forms — check form fields, required settings, and submission instructions.

If an import does not work

Check that you selected a valid package file, have edit permission for the destination assistant, and have access to the required models, tools, MCP servers, and integrations. Keep the package file and note any error message before contacting your administrator or support team.