Updates from: 06/05/2021 03:16:56
Service Microsoft Docs article Related commit history on GitHub Change details
platform Submit Your App https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md
- Title: Submit your app to Partner Center
-description: Learn how to create a Partner Center account and submit your app for store validation.
----
-# Submit your Microsoft Teams app to Partner Center
-
-After preparing your store submission, you can officially submit your app for review.
-
-## Create a Partner Center account
-
-To publish your app to the Teams store and AppSource, you must [first set up a developer account](https://docs.microsoft.com/office/dev/store/open-a-developer-account).
-
-## Submit your app
-
-To submit your app, follow these [step-by-step store submission instructions](https://docs.microsoft.com/office/dev/store/add-in-submission-guide). When creating a new submission, specify you're submitting a Teams app.
-
-### App category mapping
-
-During submission, you're asked to categorize your app. The following table maps Teams store categories to the categories listed in Partner Center.
-
-| Teams categories | Partner Center categories |
-|:|:|
-| Analytics and BI | Analytics, Data Visualization and BI |
-| Developer and IT | Developer Tools, IT Admin |
-| Education | Education |
-| Human resources | Human Resources and Recruiting |
-| Productivity | Content Management, Files and documents, Productivity, Training and Tutorials, and Utilities |
-| Project management | Communication, Project Management, Workflow, and Business Management |
-| Sales and support | Customer and Contact Management, Customer Support, Financial Management, Sales and Marketing |
-| Social and fun | Image and Video Galleries, Lifestyle, News and Weather, Social, Travel, and Navigation |
-
-### 3. Fix issues with your submission
-
-If your app fails submission, you receive a failure report so you know what to fix and resubmit. Microsoft also provides a white-glove service to help get your app listed.
-
-## FAQs
-
-### How do I create a Partner Center account?
-
-You can create a Partner Center account one of the following ways:
--- If you're new to Partner Center and don't have an account in the Microsoft network, create an account using the [Partner Center enrollment page](/office/dev/store/open-a-developer-account#create-an-account-using-the-partner-center-enrollment-page).-- If you're already enrolled in the Partner Network, create an account directly in Partner Center using an [existing enrollment page](/office/dev/store/open-a-developer-account#create-an-account-using-an-existing-partner-center-enrollment).-
-### What if I can't find my Office Store account in Partner Center?
-
-Open a [Partner Center support ticket](https://partner.microsoft.com/support/v2/?stage=1) and select the following from the drop-down menus:
-
-| Menu | Option |
-| - | - |
-|Category| Commercial Marketplace|
-| Topic | General Marketplace Help and How-to questions |
-| Subtopic| Office add-in |
-
-### Where can I get support for my Partner Center account issues?
-
-Visit the [publishers support page](https://aka.ms/marketplacepublishersupport) to search for your issue topic and find guidance. If the provided guidance is not helpful, raise a [Partner Center support ticket](/azure/marketplace/partner-center-portal/support#how-to-open-a-support-ticket).
-
-### How do I manage my Office Store account in Partner Center?
-
-Visit the [Manage your Office Store account through Partner Center](/office/dev/store/manage-account-settings-and-profile) for guidance.
-
-### How do I add my phone number to the partner profile contact section?
-
-The phone number has three parts, country code, area code, and telephone number. If your phone number doesn't include an area code, then leave the second box empty, and complete the third box.
-
-### How do I manage my account settings and partner profile in Partner Center?
-
-Visit the [Manage account settings and profile info](/windows/uwp/publish/manage-account-settings-and-profile#additional-settings-and-info) page for guidance on managing your Partner Center account settings.
-
-### Why do I receive the message, "This account is not publish eligible," when I try to submit my app?
-
-You receive the above error message when your [account verification status](/partner-center/verification-responses) is pending. Check your account verification status in the Partner Center [dashboard](https://partner.microsoft.com/dashboard). Select **Settings**, the gear icon in the upper-right corner of the page header shell. Choose **Developer settings** => **Account** => **Account settings**.
-
-![Partner Center account settings page](../../../assets/images/partner-center-accts-page.png)
-
-![Partner Center verification status](../../../assets/images/partner-center-verification-status.png)
-
-The status of each required step, such as **Email Ownership**, **Employment Verification**, and **Business Verification**, are displayed in the account verification process. After the verification process is complete, the verification status of your enrollment on the profile page changes from *pending* to *authorized*. The process steps are no longer displayed.
-
-![Partner Center verification error](../../../assets/images/partner-center-acct-verification-error.png)
-
-### What is verified in the Partner Center account verification process and how to respond?
-
-There are three verification areas, **Email Ownership**, **Employment**, and **Business**. For more information on the verification process, see [What is verified and how to respond](/partner-center/verification-responses#what-is-verified-and-how-to-respond).
-If you are the primary contact, Global admin, or Account admin, go to your Partner Profile to monitor verification status and track the progress.
-
-After the verification process is complete, the verification status of your enrollment on the profile page changes from *pending* to *authorized*. After authorization, the process steps and their status are no longer available on the page. The primary contact receives an email from Microsoft within a few business days after the verification is complete.
-
-### My account verification status hasn't advanced beyond Email Ownership. How should I proceed?
-
-During the **Email Ownership** verification process, a verification email is sent to the primary contact email address. Check your primary contact inbox for an email from **maccount@<span>microsoft</span>.com** with the subject line *Action needed: Verify your email account with Microsoft*. Complete the email verification process. The verification email is sent to the email address listed on your account settings page in Partner Center.
-
-> [!NOTE]
-> * The email verification link is only valid for seven days.
-> * You can request us to resend the email by visiting your partner profile page and selecting the **Resend verification email** link.
-> * To ensure that email is received, safe list the email from microsoft.com as a secure domain, and check your junk email folders.
-
-### How do I get further support for my account-related issues?
-
-Visit the [Support for the Commercial Marketplace program in Partner Center](/azure/marketplace/partner-center-portal/support) page for guidance and steps to create a support ticket.
-
-### I've checked my mail folders and haven't received the verification email. What must I do next?
-
-Try the following:
-* Check your junk or spam folder.
-* Clear the browser cache, go to your Partner Center account dashboard, and select the **Resend verification email** link to have the verification email resent to your email address.
-* Try accessing the **Resend verification email** link from a different browser.
-* Work with your IT department to ensure that the verification emails are not blocked by the email server.
-* Adjust your server's spam filter to allow or safe-list all emails from **maccount@microsoft.<span></span>com**.
-
-### How long does the employment verification process usually take?
-
-If all the submitted details are correct, the employment verification process takes around two hours to complete.
-
-### How long does the business verification process usually take?
-
-If all the required documents are submitted, business verification takes one to two business days to complete.
-
-### If I reach out to the support team, will my ticket be expedited?
-
-Support tickets get resolved in a week. Check for updates sent to the email ID provided when raising the support ticket.
-
-### My issue is not listed here. Are there other pages I can reference for Partner Center issues?
-
-See the [commercial marketplace documentation](/azure/marketplace/) for more help.
-
-### I've created a support ticket and I haven't received an update in 7 business days. Where can I get help?
-
-Send an email to **<teamsubm@microsoft.com>** with the following details:
-
-* **Subject Line**: Partner Center Account Issue for <App_Name> (specify the name of your app).
-* **Email body**:
- * Support ticket number
- * Your seller ID
- * A screenshot of the issue (if possible)
-
-## Next step
-
-> [!div class="nextstepaction"]
-> [Maintain and support your app](~/concepts/deploy-and-publish/appsource/post-publish/overview.md)
platform Tdp Configuration https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/tdp-configuration.md
- Title: App configuration in Developer Portal
-description: Learn how to configure and manage your apps using the Developer Portal for Microsoft Teams
-keywords: getting started developer portal teams
-localization_priority: Normal
---
-# App configuration
-
-The most significant part of a Microsoft Teams app package is its manifest.json file. This file must conform to the [Teams App schema](~/resources/schem). The manifest.json file contains metadata, which allows Teams to correctly present your app to users.
-
-You can perform the following actions in the **Configure** section of the Developer Portal:
-
-* Create an app package easily.
-* Describe the app.
-* Upload your icons.
-* Produce a .zip file for easy distribution.
-
-> [!NOTE]
-> Developer Portal does not produce functional code for your app, or host your app. Your app must already be hosted and running at the URL listed in the manifest for the app upload process to result in a working app.
--
-## Basic information and Branding
-
-The **Basic information** and **Branding** sections define the high-level description of the app you are making. This includes the appΓÇÖs name, description, and visual branding. The information in this section will be used in your app's Teams store listing and app installation dialogue.
-
-## Capabilities
-
-The **Capabilities** section of Configuration has the app's capabilities details listed.
-
-> [!NOTE]
-> The app customization feature is currently available in the developer preview only.
->
-> As a best practice, you must provide customization guidelines for app users and customers to follow when customizing your app. For more information, see [customize apps in Microsoft Teams](/MicrosoftTeams/customize-apps).
-
-Following are the capabilities:
--
-* **Personal app**
-
- This section lets you define a set of tabs that are presented by default in the personal app experience, that is, the experience a user has with your app outside the context of a team or channel. In this section, provide the following details:
-
- * The tab name.
- * A unique identifier.
- * The URL that points to the UI to be displayed in Teams.
- * The URL to use if a user opts to view the tab in a browser. This is an optional information.
- * Any additional domains from which the tab expects to load from or link to.
-
-* **Group and channel app**
-
- A Teams tab becomes part of a channel and provides quick access to team information and resources. For example, the Planner tab for a channel contains a single plan, the Power BI tab maps to a specific report. Users can drill down to the relevant context, but they should not be able to navigate outside the tab. The Power BI tab, for instance, doesn't enable navigation to other Power BI reports, but it does enable the **Go to website** button that launches the report in the main Power BI website.
-
- > [!NOTE]
- > For team tabs, you must provide a Configuration URL to present options and gather information, that would help you to customize the content and experience of your tab. This iframed HTML page is displayed when a user first adds the tab to a channel.
- > You must also provide any additional domains that the tab expects to load from or link to.
-
-* **Bot**
-
- This section allows you to add a [conversational bot](~/bots/what-are-bots.md) to your app. If you already have a bot registered with Bot Framework, you can add that bot by clicking **Set Up** and supplying the bot's name, Bot Framework ID, and defining the scopes in which the bot will work.
-
- If you have not registered the bot with the Bot Framework yet, click **Register** to create a new one. After you have registered your bot, come back to this section of the Manifest Editor to enter its name and Bot Framework ID.
-
- After you have supplied your bot's information, you can now optionally define a list of commands that your bot can suggest to users. Add the name of the command, a description of the command which indicates its syntax and arguments, and the scope(s) to which this command should apply.
-
- Note that if you have defined your bot to only support one scope, commands specified for the unsupported scope will be ignored. You can edit the scopes your bot supports at any time.
-
-* **Connector**
-
- This section allows you to add a connector to your app. If you already have registered an Office 365 connector, select **Set up** and enter the name and ID of the connector. If you want a new connector click **Register** to be taken to the Connector Developer Dashboard in your browser.
-
- > [!NOTE]
- > 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 the users. However, while adding a connector to a chat, in the list, the connectors will still show the name of the app as `Contoso`.
-
-* **Messaging Extensions**
-
- [Messaging extensions](~/messaging-extensions/what-are-messaging-extensions.md) are a powerful way for users to engage with your app within Microsoft Teams. Users can query for information from your service and post that information in the form of cards, right into the channel or chat conversation.
-
- Messaging extensions are powered by Bot Framework bots, so they require a configured bot to operate. If you have the name and Bot Framework ID of the bot you would like to power the messaging extension, enter it. Otherwise, click *Register* to create one and enter the information afterward. Select whether the configuration of a messaging extension can be updated by the user.
-
- After you have the underlying bot configured, define the commands and parameters which the messaging extension can accept.
-
- Each command requires a title and an ID. The command can optionally contain a description for the user. Each command can support up to five parameters, each of which requires the following:
-
- * The name of the parameter as it appears in the Teams client and is included in the user request.
- * A user-friendly title.
- * An optional description.
-
- > [!NOTE]
- > To create messaging extension using app studio, see [create messaging extension using app studio](~/resources/create-messaging-extension-using-appstudio.md).
-
-* **Meeting extension**
-
- //TODO: Rajesh R.
-
-* **Scene**
-
- Scenes in Together Mode is an artifact created by the scene developer using the Microsoft Scene studio that brings people together along with their video stream in a creative setting as conceived by the scene creator. In a conceived scene setting, participants have designated seats with video streams rendered in those seats. For more information, see [Teams Together Mode](~/apps-in-teams-meetings/teams-together-mode.md).
-
-## Permissions
-
-You can enrich your Teams app with native device capabilities, such as camera, microphone, and location.
-
-## Languages
-
-Set up or change the languages that your app supports.
-
-## Single Sign-On
-
-Configure your app to authenticate users with single sign-on (SSO).
-
-## Domains
-
-A list of valid domains for websites the app expects to load within the Teams client. Domain listings can include wildcards, for example, `*.example.com`. This matches exactly one segment of the domain; if you need to match `a.b.example.com` then use `*.*.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.
-
-It is not necessary to include the domains of the identity providers you want to support in your app. For example, to authenticate using a Google ID, it is required to redirect to accounts.google.com, however, you must not include accounts.google.com in `validDomains[]`.
-
-Teams apps that require their own sharepoint URLs to function well, includes "{teamsitedomain}" in their valid domain list.
-
-> [!IMPORTANT]
-> Do not add domains that are outside your control, either directly or through wildcards. For example, `yourapp.onmicrosoft.com` is valid, however, `*.onmicrosoft.com` is not valid.
-
-The object is an array with all elements of the type `string`.
-
-## Advanced
-//Todo by Karthig
-
-### App content
-//Todo by Karthig
-
-### First party settings
-//Todo by Karthig
-
-## See also
-
-* [Overview of Teams Developer Portal](~/concepts/build-and-test/teams-developer-portal.md)
-* [Distribute Teams Developer Portal](~/concepts/tdp-distribute.md)
-* [Tools in Teams Developer Portal](~/concepts/tdp-tools.md)
platform Tdp Distribute https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/tdp-distribute.md
- Title: Distribute your apps
-description: Learn how to distribute your apps using the Developer Portal for Microsoft Teams.
-keywords: getting started developer portal teams
-localization_priority: Normal
---
-# Distribute your apps
-
-## Distribute
-
-After you have finished defining your application, the **Distribute** section allows you to export your appΓÇÖs definition as a zip file which then can be shared and uploaded into the Teams client for testing. Clicking export downloads the zip file as **appname.zip** in your default download directory.
--
-### Manifest
-
-The manifest describes how your app is configured, including its capabilities, required resources, and other important attributes. See [manifest schema](~/resources/schem) for more information.
-
-### Flights
-
-Control who gets app updates. For example, you can release an update to Microsoft employees to identify and fix bugs before releasing it to the public. Select **Create a New Request** to create a new flight request.
-
-### Publish to org
-
-Make your app available to people in your org. Once approved by your IT admin, your app will be featured in Teams under Apps > Built for your org.
-
-### Publish your app to Teams store
-
-On your project home page, you can upload your app to a team, submit your app to your company custom app store for users in your organization, or submit your app to App Source for all Teams users. Your IT admin will review these submissions. You can return to the **Publish** page to check on your submission status and learn if your app was approved or rejected by your IT admin. This is also where you'll come to submit updates to your app or cancel any currently active submissions.
-
-## See also
-
-* [Overview of Teams Developer Portal](~/concepts/build-and-test/teams-developer-portal.md)
-* [Configure Teams Developer Portal](~/concepts/tdp-configuration.md)
-* [Tools in Teams Developer Portal](~/concepts/tdp-tools.md)
platform Tdp Tools https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/tdp-tools.md
- Title: Tools in Developer Portal
-description: Learn about the tools available in the Developer Portal.
-keywords: tools adaptive card scene studio bot
-localization_priority: Normal
---
-# Tools in Developer Portal
--
-## Bot Management
-
-//Todo
-
-## Scene studio
-
-Microsoft has a Scene studio that allows you to build the scenes in Together Mode. It is available on the [Scenes Editor - Teams Developer Portal](https://dev.teams.microsoft.com/scenes).
-
-![Scene studio](~/assets/images/apps-in-meetings/scene-design-studio.png)
-
-For more information, see [Build a scene using Scene studio](../apps-in-teams-meetings/teams-together-mode.md#build-a-scene-using-the-scene-studio).
-
-## Adaptive card editor
-
-//Todo
-
-## Microsoft identity platform management
-
-//Todo
-
-## Teams store app validation
-
-//Todo
-
-## See also
-
-* [Overview of Teams Developer Portal](~/concepts/build-and-test/teams-developer-portal.md)
-* [Configure Teams Developer Portal](~/concepts/tdp-configuration.md)
-* [Distribute Teams Developer Portal](~/concepts/tdp-distribute.md)
platform Overview https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Overview.md
Now, you can understand how Adaptive Cards can be transformed with the new Unive
Adaptive Cards are a combination of content, such as text and graphics, and actions that can be performed by a user. For more information, see [Adaptive Cards](http://adaptivecards.io/). The new Universal Actions for Adaptive Cards enables a common handling of the Adaptive Card actions across platforms and applications. For more information, see [Universal Action Model](/adaptive-cards/authoring-cards/universal-action-model).
-[Work with Universal Actions for Adaptive Cards](Work-with-universal-actions-for-adaptive-cards.md) document takes you through the steps to use the capabilities of Universal Actions for Adaptive Cards for your solution.
+You can get started by updating scenarios using the [quick start guide](Work-with-universal-actions-for-adaptive-cards.md) and leverage Universal Actions.
## See also
platform User Specific Views https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/User-Specific-Views.md
localization_priority: Normal
# User Specific Views
-Earlier if Adaptive Cards was sent in a Teams conversation, all users see the exact same card content. With the introduction of the Universal Actions model and `refresh` for Adaptive Cards, bot developers can now provide User Specific Views of Adaptive Cards to users. The same Adaptive Card can now refresh to a User Specific Adaptive Card.
+Earlier if Adaptive Cards was sent in a Teams conversation, all users see the exact same card content. With the introduction of the Universal Actions model and `refresh` for Adaptive Cards, bot developers can now provide User Specific Views of Adaptive Cards to users. The same Adaptive Card can now refresh to a User Specific Adaptive Card. Maximum 60 different users can see a different version of the card with additional information or actions. This provides powerful scenarios like approvals, poll creator controls, ticketing, incident management, and project management cards.
For example, Megan, a safety inspector at Contoso, wants to create an incident and assign it to Alex. She also wants everyone in the team to be aware about the incident. Megan uses Contoso incident reporting message extension powered by Universal Actions for Adaptive Cards.
var adaptiveCardResponse = JObject.FromObject(new
Card design guidelines to keep in mind while designing User Specific Views:
-* You can create a maximum of **60 User Specific Views** for a particular card being sent to a chat or channel by specifying their `userIds` in the `refresh` section.
+* You can create a maximum of **60 User Specific Views** for a particular card sent to a chat or channel by specifying their `userIds` in the `refresh` section.
* **Base Card:** The base version of the card that the bot developer sends to the chat. This is the version of the Adaptive Card for all users who are not specified in the `userIds` section.
-* A message update or edit can be used to update the base card and simultaneously refresh the User Specific Card.
+* A message update can be used to update the base card and simultaneously refresh the User Specific Card. Opening the chat or channel also refreshes the card for users with refresh enabled.
+* For scenarios with larger groups where users switch to a view on action, which needs dynamic updates for responders, you can keep adding up to 60 users to the `userIds` list. You can remove the first responder from the list when the 61st user responds. For the users who get removed from the `userIds` list, you can provide a manual refresh button or use the refresh button in the message options menu to get the latest result.
+* Give a prompt to users to get a User Specific View, where they see only a particular view of the card or some actions.
## See also