diff --git a/msteams-platform/TOC.yml b/msteams-platform/TOC.yml index 40860aedf4e..60011dc3299 100644 --- a/msteams-platform/TOC.yml +++ b/msteams-platform/TOC.yml @@ -69,9 +69,9 @@ - name: Publishing href: ./publishing/apps-publish items: - - name: Office Store checklist + - name: AppSource checklist href: ./publishing/office-store-checklist - - name: Office Store guidance + - name: AppSource guidance href: ./publishing/office-store-guidance - name: Scenarios href: ./scenarios/scenarios diff --git a/msteams-platform/assets/images/bots/bfregister.png b/msteams-platform/assets/images/bots/bfregister.png index bbe90e8af71..ef6e39b871e 100644 Binary files a/msteams-platform/assets/images/bots/bfregister.png and b/msteams-platform/assets/images/bots/bfregister.png differ diff --git a/msteams-platform/concepts/activity-feed.md b/msteams-platform/concepts/activity-feed.md index c02c4533cf3..e0df069e3d2 100644 --- a/msteams-platform/concepts/activity-feed.md +++ b/msteams-platform/concepts/activity-feed.md @@ -2,13 +2,11 @@ title: Activity feed description: Describes the activity feed and how to use it in your apps keywords: teams activity feed +msdate: 01/31/2018 --- # Notify users through the activity feed in Microsoft Teams -> [!NOTE] -> Activity feed support is available only in the [Public Developer Preview](~/resources/general/developer-preview). Additionally, many features in this document are under construction and subject to change. - The activity feed in Microsoft Teams is the user's single inbox for all activity across Teams. The feed aggregates important content from the following: * Teams/channels @@ -17,9 +15,6 @@ The activity feed in Microsoft Teams is the user's single inbox for all activity If your app posts cards and other messages into a channel, they'll automatically show up in the user's feed if he or she has followed that channel. -> [!NOTE] -> The following features are coming soon to the Public Developer Preview. - Additionally, you can also send personal (1:1 chat) messages into the feed as preview cards summarizing your app's activity. You can construct the message such that choosing the card navigates the user straight to the message or object that triggered the notification, such as an entity in a tab. This allows the user to see the full content of the activity. ## Sending content to the activity feed @@ -27,6 +22,7 @@ Additionally, you can also send personal (1:1 chat) messages into the feed as pr Activity feed notification leverages your existing integration with the Bot Framework APIs. You can flag specific messages to generate notifications which appear in the activity feed. This allows generating higher levels of engagement by creating alerts on web/desktop and mobile apps. When constructing your message, the following fields should be populated so that the correct preview content can be shown in the feed: + * `message.text`, which shows up as the activity title * `message.summary`, which shows up as the activity text @@ -35,7 +31,7 @@ When constructing your message, the following fields should be populated so that In addition to simply appearing in the feed, your app can also encode a deep link URL to an entity, such as your app’s tab. This drives user engagement to your app’s tab by allowing "one-click" navigation to that tab’s content. -#### REST API sample +### REST API sample For a message to be eligible to be included in the feed, simply mark an existing bot message with a special property, which indicates it should generate a notification: diff --git a/msteams-platform/concepts/apps/apps-overview.md b/msteams-platform/concepts/apps/apps-overview.md index 0b9b3a9f5b5..1468b0a6ccc 100644 --- a/msteams-platform/concepts/apps/apps-overview.md +++ b/msteams-platform/concepts/apps/apps-overview.md @@ -19,7 +19,7 @@ An app in Teams consists of the following parts: * [Activity feed integrations](~/concepts/activity-feed) * [Outgoing web hooks](~/concepts/outgoingwebhook.md) -A Microsoft Teams app is defined by its manifest (a JSON file). Place the manifest and two icons in a .zip file, and you have an *app package* that you can install into Teams or publish through the Office Store. (For details, see [Create the package for your Microsoft Teams app](~/concepts/apps/apps-package).) +A Microsoft Teams app is defined by its manifest (a JSON file). Place the manifest and two icons in a .zip file, and you have an *app package* that you can install into Teams or publish through AppSource. (For details, see [Create the package for your Microsoft Teams app](~/concepts/apps/apps-package).) *Teams App Studio* is a new tool that will help you to configure your application. It also contains a React control library and configurable samples for cards. See [Getting started with Teams App Studio](~/get-started/get-started-app-studio). diff --git a/msteams-platform/concepts/apps/apps-package.md b/msteams-platform/concepts/apps/apps-package.md index cca9e3685c9..3846022f4eb 100644 --- a/msteams-platform/concepts/apps/apps-package.md +++ b/msteams-platform/concepts/apps/apps-package.md @@ -7,7 +7,7 @@ ms.date: 01/22/2018 # Create an app package for your Microsoft Teams app -App experiences in Teams are defined by their app manifest, and bundled in an app package for use in uploading or Office Store submission. You'll need an app package to test your experience in Teams, via the [upload](~/concepts/apps/apps-upload) process. +App experiences in Teams are defined by their app manifest, and bundled in an app package for use in uploading or AppSource submission. You'll need an app package to test your experience in Teams, via the [upload](~/concepts/apps/apps-upload) process. A Teams app package is a .zip file containing the following: @@ -18,7 +18,7 @@ A Teams app package is a .zip file containing the following: *Teams App Studio* is a new tool that can help configure your manifest. It also contains a React control library and configurable samples for cards. See [Getting started with Teams App Studio](~/get-started/get-started-app-studio). -Your manifest file must be named "manifest.json" and be at the top level of the upload package. Note that manifests and packages built previously might support an older version of the schema. For Teams apps and especially Office Store submission, you must use the current [manifest schema](~/resources/schema/manifest-schema). +Your manifest file must be named "manifest.json" and be at the top level of the upload package. Note that manifests and packages built previously might support an older version of the schema. For Teams apps and especially AppSource (formerly Office Store) submission, you must use the current [manifest schema](~/resources/schema/manifest-schema). > [!TIP] > Specify the schema at the beginning of your manifest to enable IntelliSense or similar support from your code editor: diff --git a/msteams-platform/concepts/apps/apps-upload.md b/msteams-platform/concepts/apps/apps-upload.md index 65a7a87fe13..803f2d6e400 100644 --- a/msteams-platform/concepts/apps/apps-upload.md +++ b/msteams-platform/concepts/apps/apps-upload.md @@ -4,7 +4,6 @@ description: Describes how to upload your app in Microsoft Teams keywords: teams apps Upload ms.date: 01/02/2018 --- - # Upload an app package to Microsoft Teams To test your app experience within Microsoft Teams, you need to upload your app to Teams. Uploading adds the app to the team you select, and you and your team members can interact with it like end users. @@ -16,7 +15,7 @@ For bots designed only for 1:1 contexts, see [Adding a bot for 1:1 chat only](~/ ## Create your upload package -For development as well as Office Store submission you must create an uploadable package that contains the information to describe your experience. The package, a .zip file, contains the application manifest and icons that uniquely define your experience. +For development as well as AppSource (formerly Office Store) submission you must create an uploadable package that contains the information to describe your experience. The package, a .zip file, contains the application manifest and icons that uniquely define your experience. To create an upload package, see [Create the package for your Microsoft Teams app](~/concepts/apps/apps-package). @@ -58,7 +57,7 @@ If the app contains tabs, users can pin them to any channel on the team using th 3. Accept the consent prompt. -4. Configure your tab via its [configuration page](~/concepts/tabs/tabs-configuration) and choose **Save**. +4. Configure your tab via its [configuration page](~/concepts/tabs/tabs-configuration) and choose **Save**. ![The Add a tab dialog box, featuring a gallery of available tabs](~/assets/images/tab_gallery.png) @@ -78,7 +77,7 @@ With the app loaded in the team, users can set up a Connector on any channel in 2. Select your Connector from the **Uploaded** section at the bottom. -3. Configure your Connector via its [configuration page](~/concepts/connectors) and choose **Save**. +3. Configure your Connector via its [configuration page](~/concepts/connectors) and choose **Save**. ![The Add a tab dialog box, featuring a gallery of available tabs.](~/assets/images/connector_gallery.png) diff --git a/msteams-platform/concepts/bots/bots-create.md b/msteams-platform/concepts/bots/bots-create.md index 4c05c4ef2af..a1ba9477913 100644 --- a/msteams-platform/concepts/bots/bots-create.md +++ b/msteams-platform/concepts/bots/bots-create.md @@ -36,7 +36,7 @@ To make your bot experience Teams-ready: 1. [Create an uploadable app package](~/concepts/apps/apps-package) and [upload it to a team](~/concepts/apps/apps-upload) to test it in action. 2. Add [tabs](~/concepts/tabs/tabs-overview) or [other capabilities](~/concepts/apps/apps-overview#map-your-scenario-to-teams-capabilities) to make your experience shine in Teams. -3. [Submit your final app package](~/publishing/apps-publish) for publication in the Office Store. +3. [Submit your final app package](~/publishing/apps-publish) for publication in AppSource (formerly known as Office Store). > [!NOTE] > ## Bots and Microsoft Azure diff --git a/msteams-platform/concepts/bots/bots-overview.md b/msteams-platform/concepts/bots/bots-overview.md index 67a952150e7..4df44cc9105 100644 --- a/msteams-platform/concepts/bots/bots-overview.md +++ b/msteams-platform/concepts/bots/bots-overview.md @@ -48,7 +48,7 @@ Follow these links to build a great Teams bot: - [Create and register your bot in the Bot Framework](~/concepts/bots/bots-create): Take advantage of the great tools, documentation, and community provided by the Bot Framework team. - [Develop your bot](~/concepts/bots/bots-conversations): Add basic conversation flow and leverage channel-specific functionality. If you develop in .NET or Node.js, use our [extensions for the Bot Builder SDK](~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk) to simplify your work. - [Test your bot](~/concepts/bots/bots-test): Add your bot for 1:1 or team conversations to see it in action. -- [Publish your bot](~/publishing/apps-publish): Create your Teams package, add other capabilities, and submit it to the Office Store. +- [Publish your bot](~/publishing/apps-publish): Create your Teams package, add other capabilities, and submit it to AppSource. ## What you need to know: Teams App Studio *Teams App Studio* is a new tool that can help configure your manifest and your app. It also contains a React control library and configurable samples for cards. See [Getting started with Teams App Studio](~/get-started/get-started-app-studio). diff --git a/msteams-platform/concepts/bots/bots-test.md b/msteams-platform/concepts/bots/bots-test.md index 0a5de40a930..5dffc834286 100644 --- a/msteams-platform/concepts/bots/bots-test.md +++ b/msteams-platform/concepts/bots/bots-test.md @@ -71,6 +71,6 @@ To stop your bot receiving messages, go to your Bot Dashboard and edit the Micro To remove your bot completely from Teams, go to your Bot Dashboard and edit the Microsoft Teams channel. Choose the **Delete** button at the bottom. This prevents users from discovering, adding, or interacting with your bot. Note that this does not remove the bot from other users' Teams instances, although it will cease functioning for them as well. -## Removing your bot from the Office Store +## Removing your bot from AppSource -If you want to remove your bot from your Teams app in the Office Store, you must remove the bot from your app manifest and resubmit your app for validation. See [Publish your Microsoft Teams app to the Office Store](~/publishing/apps-publish) for more information. +If you want to remove your bot from your Teams app in AppSource (formerly Office Store), you must remove the bot from your app manifest and resubmit your app for validation. See [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish) for more information. diff --git a/msteams-platform/concepts/connectors.md b/msteams-platform/concepts/connectors.md index 43cf30e131b..f5bc2c6116f 100644 --- a/msteams-platform/concepts/connectors.md +++ b/msteams-platform/concepts/connectors.md @@ -3,14 +3,13 @@ title: Office 365 Connectors description: Describes how to get started with Office 365 Connectors in Microsoft Teams keywords: teams o365 connector --- - # Office 365 Connectors for Microsoft Teams Office 365 Connectors are a great way to push your app's rich content into Microsoft Teams. Any user can connect a team to services like Trello, GitHub, Bing News, or Twitter and get notified of the team's activity in that service. From tracking a team's progress in Trello to following important hashtags in Twitter, Office 365 Connectors help your team to stay in sync and get more done. You can even add actions to your content, turning them into *actionable messages*, so that users can complete tasks directly in the channel. (To learn more about actionable messages in general, see [Actionable messages in Outlook, Office 365 Groups, and Microsoft Teams](https://docs.microsoft.com/en-us/outlook/actionable-messages/).) ->**New:** With Microsoft Teams apps, you can add your existing Office 365 Connector or build a new one to include in Microsoft Teams. See [Build your own Connector](https://docs.microsoft.com/en-us/outlook/actionable-messages/connectors-dev-dashboard#build-your-own-connector) for more information. +>**New:** With Microsoft Teams apps, you can add your existing Office 365 Connector or build a new one to include in Microsoft Teams. See [Build your own Connector](https://docs.microsoft.com/en-us/outlook/actionable-messages/connectors-dev-dashboard#build-your-own-connector) for more information. ## Access existing Office 365 Connectors from Microsoft Teams @@ -215,14 +214,14 @@ The following steps use PowerShell. We assume that you have this installed and a ## Registering your Connector -With Microsoft Teams apps, you can distribute your registered Connector as part of your app package. Whether as a standalone solution, or one of several [capabilities](~/overview#apps-in-microsoft-teams) that your experience enables in Teams, you can [package](~/concepts/apps/apps-package) and [publish](~/publishing/apps-publish) your Connector as part of your Office Store submission, or you can provide it to users directly for uploading within Teams. +With Microsoft Teams apps, you can distribute your registered Connector as part of your app package. Whether as a standalone solution, or one of several [capabilities](~/overview#apps-in-microsoft-teams) that your experience enables in Teams, you can [package](~/concepts/apps/apps-package) and [publish](~/publishing/apps-publish) your Connector as part of your AppSource submission, or you can provide it to users directly for uploading within Teams. To distribute your Connector, you need to register by using the [Connectors Developer Dashboard](https://go.microsoft.com/fwlink/?LinkID=780623). To have your Connector work in Microsoft Teams, select **Microsoft Teams** under **Enable this integration for**. Screenshot of enabling the Connector for Microsoft Teams > [!IMPORTANT] -> After you choose **Save** in the Connectors Developer Dashboard, your Connector is registered. Do not choose **Publish to Store** (which appears after you choose **Save**); if you want to publish your Connector in the Office Store, follow the instructions in [Publish your Microsoft Teams app to the Office Store](~/publishing/apps-publish). +> After you choose **Save** in the Connectors Developer Dashboard, your Connector is registered. Do not choose **Publish to Store** (which appears after you choose **Save**); if you want to publish your Connector in AppSource, follow the instructions in [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish). You can download the auto-generated Teams app manifest from the portal. Before you can use it to test or publish your app, though, you must do the following: @@ -291,4 +290,4 @@ To verify that an `HttpPOST` action is working correctly, use your [custom incom > [!NOTE] > Currently, we do not support users configuring your Connector externally via the **Connect to Office 365** button. Users must visit Microsoft Teams first to add a Connector. -When your app is ready for submission, follow the process to [publish your app to the Office Store](~/publishing/apps-publish). +When your app is ready for submission, follow the process to [publish your app to AppSource](~/publishing/apps-publish). diff --git a/msteams-platform/concepts/messaging-extensions.md b/msteams-platform/concepts/messaging-extensions.md index 61cc7165695..efce07a12fd 100644 --- a/msteams-platform/concepts/messaging-extensions.md +++ b/msteams-platform/concepts/messaging-extensions.md @@ -3,13 +3,10 @@ title: Develop messaging extensions description: Describes how to get started with messaging extensions in Microsoft Teams keywords: teams messaging extensions messaging extensions --- -# Preview: Develop messaging extensions for Microsoft Teams +# Develop messaging extensions for Microsoft Teams Messaging extensions are a powerful new way for users to engage with your app within Microsoft Teams. With this capability, users can query for information from your service and post that information, in the form of rich cards, right into the channel conversation. -> [!IMPORTANT] -> messaging extensions are available only in [Public Developer Preview](~/resources/general/developer-preview). Many details in this document are subject to change. - ![Example of messaging extension card](~/assets/images/compose-extensions/ceexample.png) Messaging extensions appear along the bottom of the compose box. A few are built in, such as Emoji, Giphy, and Sticker. Choose the **More Options** (**⋯**) button to see other messaging extensions, including those that you add from the app gallery or upload yourself. @@ -24,7 +21,7 @@ How would you use messaging extensions? Here are a few possibilities: ## Add a messaging extension to your app -Building a messaging extension involves implementing familiar Microsoft Teams developer-platform concepts like bot APIs, rich cards, and tabs. +Building a messaging extension involves implementing familiar Microsoft Teams developer platform concepts like bot APIs, rich cards, and tabs. At its core, a messaging extension is a cloud-hosted service that listens to user requests and responds with structured data, such as cards. You integrate your service with Microsoft Teams via Bot Framework `Activity` objects. Our .NET and Node.js [extensions for the Bot Builder SDK](~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk) can help you add messaging extension functionality to your app. @@ -134,7 +131,7 @@ In the app manifest, your command item is an object with the following structure ] } ``` - + ### Test via uploading You can test your messaging extension by uploading your app. See [Uploading your app in a team](~/concepts/apps/apps-upload) for details. @@ -151,7 +148,7 @@ Most of your work involves the `onQuery` event, which handles all interactions i If you set `canUpdateConfiguration` to `true` in the manifest, you enable the **Settings** menu item for your messaging extension and must also handle `onQuerySettingsUrl` and `onSettingsUpdate`. > [!IMPORTANT] -> Messaging extensions that use `canUpdateConfiguration` can't be published in the Office Store at this time. +> Messaging extensions that use `canUpdateConfiguration` can't be published in AppSource at this time. ### Handle onQuery events diff --git a/msteams-platform/overview.md b/msteams-platform/overview.md index 9dcc1872197..897c6022702 100644 --- a/msteams-platform/overview.md +++ b/msteams-platform/overview.md @@ -25,7 +25,7 @@ In these topics, you'll find the information you need to bring your content, app | - | - | | [**Get Started**](~/get-started/get-started) | Develop, host and upload your first app and understand how apps work in Teams. | | [**Concepts**](~/concepts/concepts-overview) | Learn more about creating Teams apps, and find everything you need to know about the entire range of capabilities in Teams: tabs, bots, connectors, messaging extensions, and more. | -| [**Publishing**](~/publishing/apps-publish) | Want to publish your Teams app in the Office Store? Look here for the steps and guidelines. | +| [**Publishing**](~/publishing/apps-publish) | Want to publish your Teams app in AppSource? Look here for the steps and guidelines. | | [**Scenarios**](~/scenarios/scenarios) | Go deep into end-to-end scenarios. | | [**Resources**](~/resources/resource-overview) | Find all those nitty-gritty details you need to build a Teams app, such as a design topic, or a manifest schema reference. | | [**Troubleshooting**](~/troubleshoot/troubleshoot) | If your app isn't behaving as expected, check here. | diff --git a/msteams-platform/publishing/apps-publish.md b/msteams-platform/publishing/apps-publish.md index 5b55376d104..67c355dfec8 100644 --- a/msteams-platform/publishing/apps-publish.md +++ b/msteams-platform/publishing/apps-publish.md @@ -11,16 +11,17 @@ ms.date: 01/31/2018 > **Your Microsoft Teams app *must* use the [latest schema](~/resources/schema/manifest-schema) and follow [current packaging guidelines](~/concepts/apps/apps-package).** > > [!NOTE] -> Teams will soon provide an in-app gallery for users to find or discover [high-quality Teams apps](~/resources/design/overview). To have your solution available in this gallery, you must publish your solution through AppSource. -AppSource (formerly Office Store) provides a convenient location for you to distribute your Microsoft Teams app, as well as other Office 365 extensibility types such as Office add-ins and Sharepoint add-ins. To include your solution in AppSource, you submit it to the Seller Dashboard. You need to create an individual or company account if you have not already done so for other Windows apps or Office extensibility types. +> Teams provides an in-app gallery for users to find or discover [high-quality Teams apps](~/resources/design/overview). To have your solution available in this gallery, you must publish your solution through AppSource. + +AppSource (formerly known as Office Store) provides a convenient location for you to distribute your Microsoft Teams app, as well as other Office 365 extensibility types such as Office add-ins and SharePoint add-ins. To include your solution in AppSource, you submit it to the Seller Dashboard. You need to create an individual or company account if you have not already done so for other Windows apps or Office extensibility types. > [!NOTE] > By developing and submitting a Microsoft Teams app, you are subject to the Bot Developer Framework [Terms of Use](https://aka.ms/bf-terms), [Privacy Policy](https://aka.ms/bf-privacy), and [Code of Conduct](https://aka.ms/bf-conduct) for bot, tab, and messaging extension functionality within your app. If your app contains Office 365 Connector functionality, separate terms may also apply as part of your Connector Registration on the [Connectors Developer Dashboard](https://aka.ms/publishconnector). ## Register as an app developer -If you have already registered in the Microsoft Store ecosystem, either by distributing a Universal Windows App (UWA) via the Windows Store or an Office or Sharepoint add-in via AppSource, you should use this account to distribute your Microsoft Teams app. Otherwise, you must first [register as an app developer](https://developer.microsoft.com/en-us/store/register) to create your publisher identity in the Microsoft Store ecosystem. Account registration allows you to secure your company identity and triggers validation checks by the Microsoft Store team to ensure you are who you say you are. +If you have already registered in the Microsoft Store ecosystem, either by distributing a Universal Windows App (UWA) via the Windows Store or an Office or SharePoint add-in via AppSource, you should use this account to distribute your Microsoft Teams app. Otherwise, you must first [register as an app developer](https://developer.microsoft.com/en-us/store/register) to create your publisher identity in the Microsoft Store ecosystem. Account registration allows you to secure your company identity and triggers validation checks by the Microsoft Store team to ensure you are who you say you are. Account management in the Microsoft Store ecosystem relies on a [Microsoft account](https://account.microsoft.com/account). This identity will be the main administrator/owner of your AppSource experience. For more information, please review [Opening a developer account](https://docs.microsoft.com/en-us/windows/uwp/publish/opening-a-developer-account) and the [Developer program FAQ](https://developer.microsoft.com/en-us/store/register/faq). @@ -41,13 +42,13 @@ If you already submitted other product types to AppSource, this additional regis To start the process, choose the **Continue** button under **Office**. -![Office Store Seller Dashboard entry point](~/assets/images/submission/sellerdashboardofficeentry.png) +![AppSource Seller Dashboard entry point](~/assets/images/submission/sellerdashboardofficeentry.png) ## Use the Seller Dashboard to submit to AppSource After your account is approved, you can submit your solution to the [Seller Dashboard](http://go.microsoft.com/fwlink/?LinkId=248605). Add an app of type "Teams App" to initiate the submission process. -![Office Store Seller Dashboard add an app](~/assets/images/submission/sellerdashboardaddapp.png) +![AppSource Seller Dashboard add an app](~/assets/images/submission/sellerdashboardaddapp.png) You need to upload a [submission package](~/concepts/apps/apps-package) and provide the required metadata for the product listing page, including information such as app logo, description, and screenshots. Please review our [Submission and Manifest Metadata Checklist](~/publishing/office-store-checklist) for more information. @@ -76,7 +77,7 @@ When the validation process is complete, you will receive a message to let you k * If the status is **changes requested**, your submission needs changes before approval. Select your submission; on the summary page, choose **View the add-in report** for details about the required changes. * If the status is **approved**, your submission will be listed in the appropriate marketplaces, typically within 24 hours. -Failures are explained, with references to the specific policy violations. All failures must be addressed before resubmission. +Failures are explained, with references to the specific policy violations. All failures must be addressed before resubmission. Be sure to resubmit your app using the tile on the Overview tab. Do not use the *Add a new app* button. > [!NOTE] > If you make changes to an approved Teams experience—specifically, changes to core functionality or the manifest—it must go through the approval process again. For all other changes to your service, such as addressing issues or adding new features, resubmission is not required. @@ -92,3 +93,4 @@ Failures are explained, with references to the specific policy violations. All f * Ensure that metadata in the manifest roughly matches metadata in the Seller Dashboard (and, for bots, in the Bot Framework registration). Note that your Seller Dashboard entry should contain a more detailed and formatted description for use in the AppSource product page. * Check your manifest for completeness and accuracy. Then check it again. * Be sure to include detailed testing notes and a valid, working test account with appropriate prepopulated data. +* Do not use the *Add a new app* button to resubmit your app. Use the tile for your app on the Overview tab instead. diff --git a/msteams-platform/publishing/office-store-checklist.md b/msteams-platform/publishing/office-store-checklist.md index cc958c2720a..e8824c95a8b 100644 --- a/msteams-platform/publishing/office-store-checklist.md +++ b/msteams-platform/publishing/office-store-checklist.md @@ -1,21 +1,23 @@ --- title: Publishing checklist -description: The checklist to use before publishing your Microsoft Teams app to the Office Store +description: The checklist to use before publishing your Microsoft Teams app to AppSource keywords: teams publish store office publishing checklist --- -# Office Store checklist for Seller Dashboard submission +# AppSource checklist for Seller Dashboard submission +A +ppSource is the new name for Office Store. The follow metadata is required in your manifest.json file and for Seller Dashboard submission: |Data|Type|Size|Manifest|Seller Dashboard|Description| |---|---|---|---|---|---| -|App package|.zip|||✔|The actual app package for uploading or Office Store submission.| -|App logo|.png|96×96 pixels|`icon.color`|✔|The icon to display in the product page listing in the Office Store or Teams gallery. This is your full-color product icon.| +|App package|.zip|||✔|The actual app package for uploading or AppSource submission.| +|App logo|.png|96×96 pixels|`icon.color`|✔|The icon to display in the product page listing in AppSource or Teams gallery. This is your full-color product icon.| |App logo outline|.png|20×20 pixels|`icon.outline`||The icon to display in Teams, in the Teams chat channel and other locations. This is your logo rendered as a white outline with transparent background.| |Support link|URL|||✔|A link to support material for end users. Can be HTTP or HTTPS.| |Privacy link|URL||`developer.privacyUrl`|✔|A link to your privacy policy (HTTPS).| |Video link|URL|||Optional|A link to a video about your app.| -|EULA|.doc, .pdf, etc.|||Optional|The Office Store requires an end-user licensing agreement (EULA), which you can provide as an attachment. If you choose not to submit a EULA, one will be provided on your behalf.| +|EULA|.doc, .pdf, etc.|||Optional|AppSource requires an end-user licensing agreement (EULA), which you can provide as an attachment. If you choose not to submit a EULA, one will be provided on your behalf.| |Terms of service|URL||`developer.termsOfServiceUrl`||A link to your terms of service (HTTPS).| ## Localized content @@ -28,7 +30,7 @@ The follow metadata is required in your manifest.json file and for Seller Dashbo |App name|String|30|`name.short`|✔|The name for your application as it should appear in the storefront and in product.| |Long app name|String|30|`name.full`|✔|The name for your application as it should appear in the storefront and in product.| |Short description|String|80|`description.short`|✔|Short description of your app.| -|Long description|String|4000|`description.full`|✔|A more detailed description of your app. In the manifest file, an accurate summary is adequate. In the Seller Dashboard, you can use a richer and formatted description for the Office Store product page.| +|Long description|String|4000|`description.full`|✔|A more detailed description of your app. In the manifest file, an accurate summary is adequate. In the Seller Dashboard, you can use a richer and formatted description for AppSource product page.| |Screen shots (1–5)|.png, .jpg, or .gif|1366w × 768h and smaller than 1024 KB||✔|At least one screen shot that shows your app experience. Uses on the app details page.| ## Submission extras for bots diff --git a/msteams-platform/publishing/office-store-guidance.md b/msteams-platform/publishing/office-store-guidance.md index 8ed219d5dee..d76caf515b0 100644 --- a/msteams-platform/publishing/office-store-guidance.md +++ b/msteams-platform/publishing/office-store-guidance.md @@ -1,12 +1,12 @@ --- title: Publishing guidance -description: Describes the process of publishing your Microsoft Teams app to the Office Store +description: Describes the process of publishing your Microsoft Teams app to AppSource keywords: teams publish store office publishing +ms.date: 01/31/2018 --- - # Use the Seller Dashboard to submit your Microsoft Teams app -For a general overview of the Microsoft Teams app submission flow, see [Publish your Microsoft Teams app to the Office Store](~/publishing/apps-publish). +For a general overview of the Microsoft Teams app submission flow, see [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish). In the Seller Dashboard: @@ -14,7 +14,7 @@ In the Seller Dashboard: ![Office Seller Dashboard entry point](~/assets/images/submission/sellerdashboardofficeentry.png) -2. Choose **Add a new app** to initiate the submission process. +2. Choose **Add a new app** to initiate the submission process. If you have an existing app its tile should be displayed on this page. Choose this tile for re-submitting an existing app. The following steps assume that you are creating a new app. ![Office Seller Dashboard Add an app button](~/assets/images/submission/sellerdashboardaddapp.png) @@ -28,15 +28,16 @@ In the Seller Dashboard: * **App package** – Upload your properly formatted 1.0 manifest. Note that the manifest information prepopulates many of the following fields. * **Submission title** – The name of your app. - * **Version** – Autopopulated from the manifest. + * **Version** – Auto-populated from the manifest. * **Release date** – By default, today's date. This means that your app is eligible to be published as soon as it passes validation. If you want to delay publication, specify the date. Please note: Validation times vary, and there is no guarantee the validation process will be done by the specified date. - * **Category** – You can select up to three categories in which to appear in the Office Store. Please select ones that best match your experience. + * **Category** – You can select up to three categories in which to appear in AppSource. Please select ones that best match your experience. * **Testing notes** – Please ensure you provide enough information for our validation team to successfully load and test your experience. This includes providing sign-in instructions and test accounts, as well as any other notes that might assist in the review of your product. - * **My app calls, support, contains, or uses cryptography or encryption** – This checkbox helps to ensure taht your product is not using cryptography in a way that would prohibit distribution through the Office Store. See [Export restrictions on cryptography](https://docs.microsoft.com/en-us/windows/uwp/security/export-restrictions-on-cryptography) for a detailed explanation. + * **My app calls, support, contains, or uses cryptography or encryption** – This checkbox helps to ensure that your product is not using cryptography in a way that would prohibit distribution through the Office Store. See [Export restrictions on cryptography](https://docs.microsoft.com/en-us/windows/uwp/security/export-restrictions-on-cryptography) for a detailed explanation. + * **My app calls, support, contains, or uses cryptography or encryption** – This checkbox helps to ensure taht your product is not using cryptography in a way that would prohibit distribution through AppSource. See [Export restrictions on cryptography](https://docs.microsoft.com/en-us/windows/uwp/security/export-restrictions-on-cryptography) for a detailed explanation. * **App logo** – Use your full-color 96×96 icon. * **Support document link** – The URL for support content for your app. * **Privacy document link** – Use the URL that appears in `privacyUrl` in your manifest. - * **Video link** – Optional; the URL of a video of your app. This video appears on your product listing page in the Office Store. + * **Video link** – Optional; the URL of a video of your app. This video appears on your product listing page in AppSource. * **End User License Agreement** – If you need a custom EULA, upload it here. Choose **Next** when all required information has been filled in. @@ -57,7 +58,7 @@ In the Seller Dashboard: ![Office Seller Dashboard region block](~/assets/images/submission/sdblockregions.png) - If you do not want to distribute your app in all regions where the Office Store is available, select the regions in which you do *not* want your app to appear. + If you do not want to distribute your app in all regions where AppSource is available, select the regions in which you do *not* want your app to appear. ![Office Seller Dashboard available regions](~/assets/images/submission/sdregions.png) diff --git a/msteams-platform/resources/dev-preview/developer-preview-features.md b/msteams-platform/resources/dev-preview/developer-preview-features.md index f55f7df67b1..91aec746b60 100644 --- a/msteams-platform/resources/dev-preview/developer-preview-features.md +++ b/msteams-platform/resources/dev-preview/developer-preview-features.md @@ -2,26 +2,11 @@ title: Features in the Public Developer Preview description: Describes the features in the Public Developer Preview of Microsoft Teams keywords: teams preview developer features -ms.date: 01/20/2018 +ms.date: 01/31/2018 --- # Features in the Public Developer Preview for Microsoft Teams -The following are available to users of the Public Developer Preview ring. See [What is the Public Developer Preview for Microsoft Teams?](~/resources/general/developer-preview) for more information on enabling it for your development tenant. +As of January 31, 2018 there are no new features in Developer Preview. When this changes new items will be added here. -The following features are available in the Public Developer Preview as of December 12, 2017. +See [What is the Public Developer Preview for Microsoft Teams?](~/resources/general/developer-preview) for more information on enabling it for your development tenant. -## Apps in Microsoft Teams - -Apps in Microsoft Teams allow you to make your service available to users through a single Teams App package, which includes bots, tabs, connectors and messaging extensions. Learn more [here](~/overview). - -### AppSource (formerly Office Store) - -AppSource provides a listing of all apps available in Microsoft Teams spanning various categories. Developers can add their apps by [submitting their apps to AppSource](~/publishing/apps-publish). - -### Messaging extensions - -Messaging extensions make it easy for users to query for information from your service and post them into conversations in the form of rich cards. Learn more [here](~/concepts/-extensimessaging-extensions). - -### Activity feed - -Activity feed support allows apps to send messages using the Bot Framework without having to implement a conversational bot. It also enables your apps to mark messages as important and to post messages to the activity feed. Learn more [here](~/concepts/activity-feed). diff --git a/msteams-platform/resources/general/debug.md b/msteams-platform/resources/general/debug.md index 03c87f78550..7fef9623b77 100644 --- a/msteams-platform/resources/general/debug.md +++ b/msteams-platform/resources/general/debug.md @@ -14,10 +14,10 @@ Microsoft Teams apps can contain one or more capabilities, and the ways to run o For purely local or local Teams testing, you run the experience from your own computer. This allows you to actually compile and run within your IDE, and take full advantage of such techniques as breakpoints and step debugging. For production-scale debugging and testing, we recommend that you follow your own company guidelines to ensure you are able to support testing, staging, and deployment through your own processes. -In general, too, we recommend you utilize multiple manifests and packages to allow you to maintain separation between production and development services. For example, you might choose to register separate development and production bots and create appropriate packages to upload them in your testing environment. We also recommend you upload and test your production package before submitting to the Office Store or distributing to customers. +In general, too, we recommend you utilize multiple manifests and packages to allow you to maintain separation between production and development services. For example, you might choose to register separate development and production bots and create appropriate packages to upload them in your testing environment. We also recommend you upload and test your production package before submitting to AppSource (formerly Office Store) or distributing to customers. > [!NOTE] -> None of these testing solutions fully replicates the end-user experience for an app distributed through the Office Store, because the app installation process does some of the capability checks, such as scope, during installation. +> None of these testing solutions fully replicates the end-user experience for an app distributed through AppSource, because the app installation process does some of the capability checks, such as scope, during installation. ## Purely local diff --git a/msteams-platform/resources/schema/manifest-schema.md b/msteams-platform/resources/schema/manifest-schema.md index 91dbc277301..f70ad7c6658 100644 --- a/msteams-platform/resources/schema/manifest-schema.md +++ b/msteams-platform/resources/schema/manifest-schema.md @@ -175,7 +175,7 @@ A unique identifier for this app in reverse domain notation; for example, com.ex **Required** -Specifies information about your company. For apps submitted to the Office Store, these values must match the information in your Office Store entry. +Specifies information about your company. For apps submitted to AppSource (formerly Office Store), these values must match the information in your AppSource entry. |Name| Maximum size | Required | Description| |---|---|---|---| @@ -188,7 +188,7 @@ Specifies information about your company. For apps submitted to the Office Store **Required** -The name of your app experience, displayed to users in the Teams experience. For apps submitted to the Office Store, these values must match the information in your Office Store entry. +The name of your app experience, displayed to users in the Teams experience. For apps submitted to AppSource, these values must match the information in your AppSource entry. |Name| Maximum size | Required | Description| |---|---|---|---| @@ -199,7 +199,7 @@ The name of your app experience, displayed to users in the Teams experience. For **Required** -Describes your app to users. For apps submitted to the Office Store, these values must match the information in your Office Store entry. +Describes your app to users. For apps submitted to AppSource, these values must match the information in your AppSource entry. Ensure that your description accurately describes your experience and provides information to help potential customers understand what your experience does. You should also note, in the full description, if an external account is required for use. @@ -232,7 +232,7 @@ The value must be a valid HTML color code starting with '#', for example `#4464e ## configurableTabs -*Optional* +**Optional** Used when your app experience has a team channel tab experience that requires extra configuration before it is added. Configurable tabs are supported only in the teams scope, and currently only one tab per app is supported. @@ -246,7 +246,7 @@ The object is an array with all elements of the type `object`. This block is re ## staticTabs -*Optional* +**Optional** Defines a set of tabs that can be "pinned" by default, without the user adding them manually. Static tabs declared in `personal` scope are always pinned to the app's personal experience. Static tabs declared in the `team` scope are currently not supported. @@ -262,7 +262,7 @@ The object is an array (maximum of 16 elements) with all elements of the type `o ## bots -*Optional* +**Optional** Defines a bot solution, along with optional information such as default command properties. @@ -286,13 +286,12 @@ An optional list of commands that your bot can recommend to users. The object is ## connectors -*Optional* -App support for connectors is only available in the [Public Developer Preview](~/resources/general/developer-preview). Connectors themselves are generally available. +**Optional** The `connectors` block defines an Office 365 Connector for the app. The object is an array (maximum of 1 element) with all elements of type `object`. This block is required only for solutions that provide a Connector. - + |Name| Type| Maximum size | Required | Description| |---|---|---|---|---| |`connectorId`|String|64 characters|✔|A unique identifier for the Connector that matches its ID in the Connectors Developer Portal.| @@ -300,9 +299,7 @@ The object is an array (maximum of 1 element) with all elements of type `object` ## composeExtensions -*Optional* - ->[Public Developer Preview](~/resources/general/developer-preview) only +**Optional** Defines a messaging extension for the app. @@ -318,6 +315,7 @@ The object is an array (maximum of 1 element) with all elements of type `object` |`commands`|Array of object|1|✔|Array of commands the messaging extension supports| ### composeExtensions.commands + Your messaging extension should declare one or more commands. Each command appears in Microsoft Teams as a potential interaction from the UI-based entry point. Each command item is an object with the following structure: @@ -335,7 +333,7 @@ Each command item is an object with the following structure: ## permissions -*Optional* +**Optional** An array of `string` which specifies which permissions the app requests, which lets end users know how the extension will perform. The following options are non-exclusive: @@ -344,7 +342,7 @@ An array of `string` which specifies which permissions the app requests, which l ## validDomains -*Optional*, except **Required** for apps with tabs +**Optional**, except **Required** for apps with tabs A list of valid domains from which the extension expects to load any content. Domain listings can include wildcards, for example `*.example.com`. If your tab configuration or content UI needs to navigate to any other domain besides the one use for tab configuration, that domain must be specified here. diff --git a/msteams-platform/troubleshoot/faq.md b/msteams-platform/troubleshoot/faq.md index 1e0c62b66be..9461c248503 100644 --- a/msteams-platform/troubleshoot/faq.md +++ b/msteams-platform/troubleshoot/faq.md @@ -10,7 +10,7 @@ keywords: teams apps faq faqs ### What technology should I use to build my bot or tab? -Tabs are web content that you build and deploy, so you can use any technology you want. +Tabs are web content that you build and deploy, so you can use any technology you want. Because bots must be built with the Bot Framework, we recommend you use one of the languages supported by the Bot Builder SDK: .NET/C# or Node.js. Although the Bot Framework also provides REST APIs usable by any language you choose, the SDK provides additional functionality and helper functions to simplify the development process. @@ -36,13 +36,13 @@ Bots in channels receive messages only when they are explicitly @mentioned. Ther ### How can I distribute my Microsoft Teams app? -Microsoft Teams apps can be distributed to end users via the Office Store and the in-product app-discovery system. For more information, see [Publish your Microsoft Teams app to the Office Store](~/publishing/apps-publish). +Microsoft Teams apps can be distributed to end users via AppSource and the in-product app-discovery system. For more information, see [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish). Microsoft Teams app packages can be manually distributed to your colleagues or other end users and uploaded by them via the [uploading process](~/concepts/apps/apps-upload). Please note that apps distributed in this format are not tested, validated, or trusted by Microsoft. -### What account do I use to create an Office Store or Dev Center account? +### What account do I use to create an AppSource or Dev Center account? -A Microsoft Store developer account is based on a [Microsoft account](https://account.microsoft.com/account), so you should use an existing Microsoft account or create one for this purpose. +An AppSource developer account is based on a [Microsoft account](https://account.microsoft.com/account), so you should use an existing Microsoft account or create one for this purpose. If you already have a Windows Store developer account, you must use the original owner Microsoft account for the Seller Dashboard experience. Although the Windows Store portal allows Azure Active Directory association, the Seller Dashboard is a separate system that works only with your original Microsoft account.