This sample demonstrates the use of SignalR combined with Azure Functions integrated with PlayFab to push notifications to clients.

• If you don’t already have Visual Studio 2019 installed, you can download and use the free Visual Studio 2019 Community Edition. Make sure that you enable Azure development during the Visual Studio setup.
• If you don't have an Azure subscription, create a free account before you begin.
• You'll also need a free PlayFab account with a title created for testing purposes.

• Configure a SignalR Service instance as described in the section here.
• Create a Function app as described here.

Please make note that you're required to create/specify a storage account as part of function app provisioning. You'll need this storage account later.

After cloning this repo, there are a few changes you'll need to make to the settings before it can be run and deployed.

1. Open the Azure portal to the SignalR service that you provisioned.
2. Navigate to "Keys" under "Settings"
3. Copy the full value under "CONNECTION STRING"
4. Open the local.settings.json file in the PlayFab.SignalRSample project in this repo
5. Find the AzureSignalRConnectionString setting
6. Replace the temporary string with the one copied from the Azure portal

1. Open the Azure portal to the Storage Account you associated with your Function app earlier
2. Navigate to "Access Keys" under "Settings"
3. Copy the full value under "Connection String"
4. Open the local.settings.json file in the PlayFab.SignalRSample project in this repo.
5. Find the AzureWebJobsStorage setting
6. Replace the temporary string with the one copied from the Azure portal

1. Navigate to the PlayFab Game Manager
2. Either create or Select the title you which to use for this sample and copy the (4 or 5 hex digit) title id
3. Open the Program.cs file in the MessagingClient project in this repo
4. Find this line:

        // Title Id from PlayFab. Set this depending on the title you're integrating with.
        private const string TITLE_ID = "XXXXX";

5. Replace the "XXXXX" with the PlayFab title id

Before we can build and deploy our solution, we need to configure a couple of things on our Azure resources.

1. Open the Azure portal to the Storage Account you associated with your Function app earlier
2. Navigate to "Queues" under "Queue service" (you'll probably have to scroll down a bit)
3. Hit the big "+" button to add a queue
4. Name the queue "matchfound" and click OK

1. Open the Azure portal to your Function app
2. Click the "Get publish profile"
3. Save the .PublishSettings file locally
4. Right Click on the PlayFab.SignalRSample project in Visual Studio
5. Choose the "Publish..." option
6. In the Publish Window click on "Start"
7. Click on the "Import Profile..." in the bottom left
8. Select the .PublishSettings file you downloaded earlier

The SignalR Connection String and Web Jobs Connection String that we set locally a few moments ago need to be copied into the Azure Portal (This can sometimes also be done via the later publish process, but it's consistent and easy to do it now via the portal)

1. Open the Azure portal to your Function app
2. Click on "Configuration" in the Settings section
3. Under Application settings, click "New application setting"
4. Provide a Name of AzureSignalRConnectionString
5. For value, use the same value you copied into the local.settings.json file earlier
6. Click OK
7. Repeat steps 3-6 for the AzureWebJobsStorage settings
8. Save your changes to the Application Settings in the Portal

1. Build the PlayFab.SignalRSample
2. It should download packages for SignalR, webjobs, and PlayFab
3. Verify the project builds successfully
4. Choose to publish the project using the publish settings from earlier

Before we can start configuring things in PlayFab, we need to copy a few settings out of Azure.

1. Open the Azure portal to your Function app
2. Under "Function" click on each of the functions in series
3. For each, click on the "Get Function URL" link
4. Copy the URL for each to a scratch pad

MatchFound will not have a URL. It's a Queue Function and isn't invoked by HTTP directly.

1. Open the Azure portal to the Storage Account you associated with your Function app
2. Navigate to "Access Keys" under "Settings"
3. Copy the full value under "Connection String" to a scratch pad

In order to stitch this all together, we also need to configure a few things in PlayFab.

1. Choose Multiplayer from the BUILD section on the left
2. Go to the Matchmaking tab
3. Click the New Queue button in the top right
4. Set the Queue Name to "nr_simple"
5. Set both the Min and Max Match Size to 2
6. Save the Queue

There are four functions to register, so there's a bit of repetition here. Three are standard HTTP functions and one is a Queue function. I'll describe each of these types.

1. Choose Automation from the BUILD section on the left
2. Go to the Cloud Script tab and click on "Functions (Preview)"
3. Click on Register Function
4. Select HTTP as the trigger type
5. Enter "GetSignalRConnection" as the Function name
6. Copy the associated Function URL from your scratch pad
7. Save the Function
8. Repeat steps 3-7 for Function names "PlayerLogin" and "SendChatMessage" as well

1. Choose Automation from the BUILD section on the left
2. Go to the Cloud Script tab and click on "Functions (Preview)"
3. Click on Register Function
4. Choose Queue as the trigger type
5. Enter "MatchFound" as the Function name
6. Enter "matchfound" as the Queue name
7. Copy the Storage Account connection string from your scratch pad

You'll need to create two rules, so just follow these steps twice for the two different rules.

1. Choose Automation from the BUILD section on the left
2. Go to the Rules tab
3. Click on New Rule
4. Set the Name to "Broadcast Friend Login"
5. Set the Event type to com.playfab.player_logged_in
6. Add an Action
7. Set the Type to Execute Azure Function
8. Slect
9. Select "PlayerLogin" as the Cloud Script Azure Function selection
10. Save the rule
11. Repeat steps 3-10 using Name=Matchmaking Notifications, Event type=playfab.matchmaking.match_found, and Function=MatchFound

With all the configuration out of the way, we're free to run the app. The app is designed to run multiple local instances, so once you build it, you'll want to find the local executable to make it easy to launch multiple copies.

The app does these things in sequence

• Login to PlayFab using a unique id based on the local machine name
• Setup a SignalR connection
• Join a matchmaking queue
• Receive a notice via SignalR once matched
• Enter a chat channel with the other player in the match

• The function app will spin down when not in use. That may mean you see delays and timeouts on first use or after idling for a while. This can be mitigated by opting for the Azure Functions Premium plan to avoid cold starts.
• While the app is running, it's listening for broadcasts of additional logins and will display them as soon as they happen.
• Once in chat, you can type lines of text to send to the other player.
• If there are more than two instances, there may be multiple matches, but only 2 players per match.
• To exit after entering chat, just hit enter (send an empty chat line).