Schema v1.19

New Features

• This update adds a new declarativeAgents array within a new copilotAgents property, enabling developers to build declarative Copilot Agents. Learn more
• To support the development of multi-language copilot agents, a defaultLanguageFile property is introduced, along with a localizationKeys property added to the localization schema. Learn more

Schema v1.17

• Added support for creation of Outlook add-ins with the unified manifest for Microsoft 365. Learn more.
• Added a semanticDescription field in a message extension plugin for Copilot for Microsoft 365. Learn more
• Added support for creating message extensions using API. Learn more
• Added support for apps to easily show as cards on Viva Connections Dashboard. Learn more
• Added new sample prompts to guide users who install or enable a plugin for the first time. Learn more
• Added bot configurations changes. Learn more
• Removal of Apppackagename property. If your manifest has this property, it will not be valid in this new manifest version.
• Removal of callingSidepanel propoerty. This is a minor breaking change. If your manifest has this property, it will not be valid in this new manifest version.

Schema v1.16

Property Updates in Static Tabs

• Added "groupChat" to staticTabs scope. Learn more.

• Added 6 new values to staticTabs context. Learn more.

  • "privateChatTab"
  • "meetingChatTab"
  • "meetingDetailsTab"
  • "meetingSidePanel"
  • "meetingStage"
  • "teamLevelApp"

Property Updates in Meeting Extension Definition

• Added new "supportsAnonymousGuestUsers" property. Learn more.

Schema v1.15

Property Updates in Compose Extensions

• Added new supportsAnonymizedPayloads property. Learn more.

Schema v1.14

Property update for Shared Channels & Meeting Extensions

• Added new supportedChannelTypes property.  Learn more.

• Added new supportsStreams property to meeting extension definition. 

• Added new scopeConstraints property. Learn more.

Schema v1.13

Support for apps running across Microsoft 365

This schema version auto-extends support of Teams apps to run in other Microsoft 365 host applications, including Outlook and Office. Learn more.

Schema v1.12

Resource Specific Consent Permissions Updates

Enable resource-specific consent in Teams - Teams | Microsoft

Test resource-specific consent permissions in Teams - Teams | Microsoft Docs

Reference: Manifest schema for Microsoft Teams - Teams | Microsoft Docs

NOTE: Permissions have been consolidated into a new "authorization" section.

Schema v1.11

Clean-up

Removal of supported platform properties which is a feature that was cancelled for public release.
Compose extension id should be a guid definition not a bot id

Schema v1.10

App Customization

App customization enables admins to change the look-and-feel of the apps loaded through bots, messaging extensions, tabs, and connectors. For example, if the Teams admin customizes the name of an app from Contoso to Contoso Agent, then the app will appear with the new name Contoso Agent to users. However, while adding a connector to a chat, in the list the connectors will still show the name of the app as Contoso

Please refer to the documentation regarding the schema property:
configurableProperties
https://docs.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema#configurableproperties

Schema v1.9

Changes in this release:

MicrosoftTeams.schema.json

defaultInstallScope
Provides a way specify the default installation scope for their apps so the app install experience will make it the default option for users. The rest will be moved to the chevron.

defaultGroupCapability
This value is related to "defaultInstallScope" where you can specify the default capability in the case of having multiple capabilities when your app is installed in the group scope.