IMPORTANT: This is an update of an article where I have explained pairing Windows Azure Workflow Beta (how it was previously called), with SP 2013 Preview. Since the story has not changed much with the RTM bits, instead of writing a new post, I’ll just update existing one. Updated places will be marked properly.
After you have installed Windows Azure Workflow Manager 1.0, you need to pair it with SharePoint 2013 Server, in order to use new workflows in your solutions.
Since the official MSDN documentation is a bit dry on this process, I decided to write here a short overview with some screenshots.
The easiest way to install Windows Azure Workflow is through Platform Installer (although there are other ways to do it). If you get the access denied (401) error while configuring the Workflow, please look at my previous blog post.
Once it’s installed, we need to pair it with SharePoint.
First we need to find out HTTP and HTTPS ports the Workflow has been installed to. To find that out, go to the IIS manage, open Workflow Management site, and look at the bindings:
For you PowerShell freaks out there, you can achieve the same with bit more typing 
– open the Workflow PowerShell console, and execute the following commands (for HTTP and HTTPS ports):
Get-WFFarm | ft WFMgmtHttpPort Get-WFFarm | ft WFMgmtHttpsPort
(previous two commands were used in the beta 1 version of Workflow Manager).
Get-WFFarm | ft HttpPort
Get-WFFarm | ft HttpsPort
Now when we know the ports, we can pair the Workflow with SharePoint. We will need SharePoint PowerShell for this – open the SharePoint Management Shell (PowerShell) console, and, depends if you want to use HTTP, or HTTPS – depends how your server is configured – execute the following command:
Register-SPWorkflowService –SPSite "http://server/sitecollection" –WorkflowHostUri "http://WorkflowHost:PORT" –AllowOAuthHttp
Please replace the SPSite, WorkflowHostUri and PORT with appropriate values. SPSite is your site collection where you want to use Workflow, WorkflowHost is the server where you have installed the Workflow, and PORT is the port number, determined in the previous step, depending if you want to use HTTP or HTTPS.
NOTE 1: PREVIOUS POWERSHELL COMMAND MUST BE EXECUTED ON THE SHAREPOINT SERVER. SHAREPOINT FOUNDATION IS NOT SUPPORTED IN WORKFLOW SCENARIOS.
NOTE 2: IF WORKFLOW IS INSTALLED ON A SEPARATE SERVER, WHICH IS NOT PART OF THE SHAREPOINT FARM, YOU NEED TO DOWNLOAD AND INSTALL THE “WINDOWS AZURE WORKFLOW MANAGER CLIENT” ON THE SHAREPOINT SERVER WHICH YOU ARE CONFIGURING TO USE WORKFLOW
You can download Workflow Manager Client here: http://go.microsoft.com/fwlink/?LinkID=251617
After you have executed the previous PowerShell command, you need to give it some time to run. It’s a silent command, you will not see any progress indicator, or status message that the pairing has been successful.
To prove if everything’s all right, go to the Central Administration, Service Applications, and look for the “App Fabric Workflow Service Application Proxy”
It should be started, and when you click on it, you should get the Workflow Service status.
Yep, it’s running 
