·
3 min read

From Office 365 to Azure to Minecraft, connected with Flow

This week, read about a fun scenario from John Liu about how he automated Minecraft with Microsoft Flow. This article was orignally posted here.

Background

  1. Minecraft Windows 10 edition in the latest 1.2 (better together update) included web sockets previously only in the Minecraft Education version. Web Sockets lets you connect to a Minecraft game, and remotely execute Minecraft commands.
  2. Minecraft Code Connection is an external application that hosts a friendly REST API and translates JSON to web socket. Previously this was only for Minecraft Education Edition. An update in early October allows this to work with Minecraft Windows 10. https://makecode.com/blog/minecraft/10-18-2017
  3. Microsoft Data Gateway allows Flow, PowerApps, PowerBI to talk to on-premises environments. It also recently gained the ability to execute custom connections. It is essentially, an enterprise data gateway / reverse proxy that connects your local environment to an Azure Service Bus. The ability to call your custom local REST endpoint was released in September. https://flow.microsoft.com/blog/q3-2017-update/
  4. Cloud based services like Flow/LogicApps, PowerApps, and PowerBI can talk to this connection online, via the magic of Azure Service Bus.
  5. And because I’m a SharePoint MVP – we are triggering this Flow from SharePoint Online. Because the world needs this.

Setting up Minecraft & Code Connection

Code Connection uses Minecraft commands – the option is called “activate cheats” – do this in a creative world.

Code Connection is a separate executable. Run it outside of Minecraft – it’ll ask you to enter the command into Minecraft.

Use Postman to test your localhost:8080 and send a REST request. You’ll see your agent bot move.

Congrats – you now have a REST endpoint that can send game commands to your Minecraft game.

At this point – there is a bunch of integration you can already do – any home IOT or webapplication can send REST to this endpoint – you just need to do a CORS (cross-origin-resource-sharing) call.

Setting up Flow Data Gateway

https://flow.microsoft.com/documentation/gateway-reference/ – The data gateway also calls your local REST endpoints via a custom connector. This was a feature that was silently released in the deluge of news from MSIgnite. I need to thank @pratapladhani (PowerApps PM) for sending me the link of the announce: https://flow.microsoft.com/blog/q3-2017-update/

“On-premises connectivity to any HTTP API – Finally, users can now connect their own on-premises APIs with Custom Connectors – leveraging the On-Premises Data Gateway. For example, if you have a service that’s only available on your local network, you can now author a custom connector that can read data from or push data to that local service.”

Congrats – this is your reverse proxy.

Setting up custom connection via this Swagger File I’ve prepared for you

https://github.com/johnnliu/flow/blob/master/mc-cc.swagger.json – Grab this swagger.json and add a custom connection to Flow.

Note the host is localhost:8080. Tick: Connect via on-premise data gateway.

Note the custom connection swagger file points to localhost:8080 – this will work if your data gateway is on the same machine as the Code Connection exe.  Otherwise, you should use the LAN IP Address of the Code Connection server. Add a connection, and select On-Premises data gateway.

Note the connection type is “On-premises”:

Write the Flow

These wonderful methods with dropdowns are defined in Swagger file. Please add pull requests if you add more methods.  

Trigger it from Office 365 / SharePoint

At this point your flow should have run successfully.

I want to especially emphasize, all these steps are done without me writing a single line of C# or JavaScript.

Cost

Office 365 E3+ license allows you to have:

  • 2000 Flow runs per user
  • 1 Custom Connection
  • On-Premises data gateway allowed
  • Read more at: https://flow.microsoft.com/pricing/

So there’s no extra cost for an Office 365 customer E3+

Summary of Key Points

  • (Buy) Minecraft Win10 has websockets
  • (Free) Code Connection does JSON to websocket
  • (Free) Data Gateway is amazing, also calls your local REST endpoints
  • (O365 E3 license) Microsoft Flow just unlocks it to the rest of the world, if you like, LogicApps will work just as well.
  • You can have a PowerApp calling the function via the Custom Connection, without Flow.
  • Extremely code-less

Where do we go next?

Well, when I detect an Active Directory User deletion via webhook – I’m going to teleport this Zombie Villager into lava.

Final thoughts

So, some people have commented to me directly – John this is very cute, but there’s no business use case for this.

  • Minecraft has REST endpoint – yay
  • Data Gateway allows Flow to reach inside your internal network. Since Flow can be a webservice, you can run this as a reverse proxy exposing internal REST methods via an external Flow.
  • The entire solution is extremely low-code.

I really enjoyed working this out. Have fun and let me know how you go.