Azure PlayFab Party features

This topic provides details about Azure PlayFab Party features and how you can use them in your game.

For a high-level summary of Party features, see the Party overview. If you're ready to start developing, see the Party Quickstart.

Interoperable multiplayer infrastructure

Our goal is to enable you to build interoperable multiplayer experiences across devices and platforms when you're using Party and other PlayFab multiplayer services.

When you're implementing cross-play, always adhere to the best industry design practices. This helps ensure that your game's multiplayer experiences don't put certain device form factors at a disadvantage relative to other devices. Remember to verify that your cross-network/cross-platform multiplayer and player activity design complies with all applicable platform policies. This means checking with every platform that your game is on.


You're responsible for the compliance of your multiplayer and cross-network implementation.

Low-latency secure data communication

Industry-standard encryption and authentication

Party uses industry-standard encryption and authentication for all communication (management data, game data, and real-time communication). This includes all peer-to-peer transmissions and all transactions to Azure services, whether they're web services (using HTTPS) or our transparent cloud relay service (which uses DTLS).

Cross-platform mesh

Party enables data communication by automatically connecting players through a transparent, low-latency cloud relay or select regions on your own, choosing from one of our Azure regions that are distributed across the globe. Alternatively, you can use actual direct peer-to-peer connectivity capabilities.

You can make use of our background Quality of Service (QoS) measurements to ensure that you have the best possible data connection for communication. For more information, see Party QoS measurements.

Networking transport capabilities

Our networking capabilities expand on User Datagram Protocol (UDP) features to provide datagram transport capabilities, including guaranteed delivery, sequential delivery, and coalescing, that are ideal for real-time multiplayer games. For more information, see Transport options.

Flexible topology design possibilities

The flexible design of Party supports a variety of communication topologies. You can create a mesh that suits your game.

You can enable chat at any time or send data messages in the following patterns.

  • Everyone-to-everyone
  • Unidirectionally from one-to-many
  • Constrained to "teams" or game-defined "channels"
  • Multiple local players on a single device
  • Connecting to more than one distinct group of players at a time
  • Arbitrary symmetric or asymmetric subsets, or combinations of the previously mentioned patterns

Party objects in multiple networks can support devices that connect to more than one network at a time. An example usage is to maintain communication with a set of friends over time. This group of friends is still able to join and leave larger, separate game sessions with strangers.

To learn more about designing networks, see Party objects and their relationships.

Accessible voice and text chat

Party chat offers the following communication functionalities.

  • Voice chat: Player devices can bind audio devices to Party networks to accomplish real-time voice chat.

  • Text chat: Players are able to send text chat messages to one another. In-game chat text messages don't drive metering and aren't billed to your account.

  • Speech-to-text: Player voice and synthesized text-to-speech voice can be transcribed into text messages. This functionality was originally designed to enable games to be accessible. It's also useful when gaming in a noisy environment.

  • Text-to-speech/voice synthesis: Generate audio from text. It can be used to synthesize player voice to read incoming text to the recipient. Like speech-to-text, it can be used for making your game more accessible.

  • Ability to add real-time custom voice effects: Access to data in audio buffer enables you to add real-time custom effects like spatial sound using external sound engines. For more information, see Using real-time audio manipulation to apply custom voice effects

  • Real-time translation: Incoming speech and text can be translated in real-time.

    • Incoming speech can be translated into more than 60 languages. Your input source is voice. The output target is audio or text in a different language. For the latest information, see Azure Cognitive Speech Translation.
    • Incoming text can be translated into more than 70 languages. Your input source is text. The output target is text or audio in a different language. For the latest information, see Azure Cognitive Translator.
  • Text moderation: Text chat can be moderated in real-time to filter out offensive language. For more information, see Using text moderation.

Speech-to-text, text-to-speech, and real-time translation use Azure Cognitive Services to power these functionalities. We recommend associating the activation of these capabilities under the Ease of Access player settings. For information about rates and pricing, see PlayFab pricing and Party pricing.

To learn more, see Understanding how Party chat works. For more guidance on how to use the accessibility features that are provided by Party, see Text-to-speech guidelines and Speech-to-text guidelines.

Capabilities designed for multiplayer games

Efficient game states and logic delivery

Game states and logic are essential to games. When synchronizing game states, your game is responsible for deciding when to submit data messages to Party and what these payloads mean.

You can make use of the Party transport system to ensure that submitted messages are delivered securely and efficiently. This can be achieved by using feature options such as guaranteeing delivery (despite internet packet loss) and automatically fragmenting and reassembling messages that are larger than what the environment supports.

Together with ongoing connection quality feedback, such as observed latency, you can decide how your game interprets this information for a response. Tune, predict, or recover in a way that suits your design and tolerances.


Using data transmission in Party is entirely optional. Some games use only the chat features.

Integration ability with custom/existing discovery systems—players finding other players

Discovery is the process that occurs before players start connecting or chatting with one another. Games typically have a discovery or signaling mechanism in place to help players find one another before initial connectivity information can be shared.

Party integrates well with custom or existing discovery systems such as social platforms with invitation systems. What this means is that after players have found one another through this external system, you would pass Party suitable connection information to help you set up communication.

Policy enforcement for connectivity and communication

Games have policies in place to determine if real-time chat or data communication between players should be allowed. Party is able to enforce these policies efficiently through the use of connectivity, voice chat, and text chat API functionalities—together or independently.

Your game is responsible for defining and determining what these policies are. This is based on gameplay, privacy, and privilege implementation. For example, restricted accounts can chat only with players who are friends and must be on a particular social platform (limiting chat capabilities for players who are on behavioral bans) or simply enforcing gameplay rules to allow only players who are on the same/opposing team to chat.

We have a helper module for the Xbox Live social platform. It helps takes care of common tasks that are needed to integrate their privilege ecosystems with Party. For more information, see Party Xbox Live Helper Library.

See also