Polly Microsoft Teams

 admin
-->

Poly creates premium audio and video products so you can have your best Teams meeting—anywhere, anytime, every time. Our Teams-certified headsets, video and audio conferencing products, desk phones, analytics software and services are beautifully engineered to connect people with incredible clarity and work seamlessly with Microsoft Teams. Dec 07, 2020 How to create a poll on Microsoft Teams using Forms. Open Microsoft Teams. Click on Teams from the left navigation pane. Quick note: You can also create polls during a meeting or chat. Click the New conversation button. Click the Messaging extensions (three-dotted) button. Select the Forms option. Information Response; App name: Polly: ID: WA104381060: Capabilities: Bot, Tab, Messaging Extension: Office 365 clients supported: Microsoft Teams: Partner company name. To create a poll, open Microsoft Teams and then click on the three dots under a new chat message or reply. In the window that pops up, select the “Forms” option. A new Forms window will load that allows you to ask a single question. Polly makes it simple to manage scheduling, voting options, question types, anonymity levels, and results visibility—all right in Microsoft Teams.

Last updated by the developer on: December 16, 2019

General information

Information provided by Polly to Microsoft:

InformationResponse
App namePolly
IDWA104381060
CapabilitiesBot, Tab, Messaging Extension
Office 365 clients supportedMicrosoft Teams
Partner company namePolly
URL of partner websitehttps://www.polly.ai
URL of Teams application info pagehttps://www.polly.ai/help/msteams
URL of Privacy Policyhttps://www.polly.ai/privacy
URL of Terms of Usehttps://www.polly.ai/tos

Feedback

Polly

Questions or updates to any of the information you see here? Contact us!

How the app handles data

This information has been provided by Polly about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.

Data access using Microsoft Graph

Microsoft

List any Microsoft Graph permissions this app requires.

This application does not use Microsoft Graph.

Non-Microsoft services used

Agile Polly Microsoft Teams

If the app transfers or shares organizational data with non-Microsoft service, list the non-Microsoft service the app uses, what data is transferred, and include a justification for why the app needs to transfer this information.

Non-Microsoft services are not used.

Data access via bots

If this app contains a bot or a messaging extension, it can access end-user identifiable information (EUII): the roster (first name, last name, display name, email address) of any team member in a team or chat it's added to. Does this app make use of this capability?

Justification for accessing EUII?Is EUII stored in database(s)?Justification for storing EUII?
Providing list of users and channelsAll

Telemetry data

Does any organizational identifiable information (OII) or end-user identifiable information (EUII) appear in this application's telemetry or logs? If yes, describe what data is stored and what are the retention and removal policies?

None

Organizational controls for data stored by partner

Describe how organization's administrators can control their information in partner systems? e.g. deletion, retention, auditing, archiving, end-user policy, etc.

Customers are able to control data retention and perform auditing as part of the Polly Enterprise service plan.

Feedback

Polly

Questions or updates to any of the information you see here? Contact us!

Add Polly To Microsoft Teams

Information from the Microsoft Cloud App Security catalog appears below.

Feedback

Questions or updates to any of the information you see here? Contact us!

Poly Microsoft Teams Room

-->

The recommended approach for retries with exponential backoff is to take advantage of more advanced .NET libraries like the open-source Polly library.

Polly is a .NET library that provides resilience and transient-fault handling capabilities. You can implement those capabilities by applying Polly policies such as Retry, Circuit Breaker, Bulkhead Isolation, Timeout, and Fallback. Polly targets .NET Framework 4.x and .NET Standard 1.0, 1.1, and 2.0 (which supports .NET Core and later).

Microsoft Teams Surveys

The following steps show how you can use Http retries with Polly integrated into IHttpClientFactory, which is explained in the previous section.

Reference the .NET 5 packages

IHttpClientFactory is available since .NET Core 2.1 however we recommend you to use the latest .NET 5 packages from NuGet in your project. You typically also need to reference the extension package Microsoft.Extensions.Http.Polly.

Configure a client with Polly's Retry policy, in Startup

As shown in previous sections, you need to define a named or typed client HttpClient configuration in your standard Startup.ConfigureServices(...) method, but now, you add incremental code specifying the policy for the Http retries with exponential backoff, as below:

The AddPolicyHandler() method is what adds policies to the HttpClient objects you'll use. In this case, it's adding a Polly's policy for Http Retries with exponential backoff.

To have a more modular approach, the Http Retry Policy can be defined in a separate method within the Startup.cs file, as shown in the following code:

With Polly, you can define a Retry policy with the number of retries, the exponential backoff configuration, and the actions to take when there's an HTTP exception, such as logging the error. In this case, the policy is configured to try six times with an exponential retry, starting at two seconds.

Add a jitter strategy to the retry policy

A regular Retry policy can affect your system in cases of high concurrency and scalability and under high contention. To overcome peaks of similar retries coming from many clients in partial outages, a good workaround is to add a jitter strategy to the retry algorithm/policy. This strategy can improve the overall performance of the end-to-end system. As recommended in Polly: Retry with Jitter, a good jitter strategy can be implemented by smooth and evenly distributed retry intervals applied with a well-controlled median initial retry delay on an exponential backoff. This approach helps to spread out the spikes when the issue arises. The principle is illustrated by the following example:

Additional resources

  • Retry pattern
    https://docs.microsoft.com/azure/architecture/patterns/retry

  • Polly and IHttpClientFactory
    https://github.com/App-vNext/Polly/wiki/Polly-and-HttpClientFactory

  • Polly (.NET resilience and transient-fault-handling library)
    https://github.com/App-vNext/Polly

  • Polly: Retry with Jitter
    https://github.com/App-vNext/Polly/wiki/Retry-with-jitter

  • Marc Brooker. Jitter: Making Things Better With Randomness
    https://brooker.co.za/blog/2015/03/21/backoff.html