The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Here we’d take a simple example of creating an Azure WebJob that will connect to the SQL On-Prem Database.
To start with, create a console application that connects to SQL On-Prem Database and pulls information from a table inside it.
Publish it as Azure WebJob.
Click on Publish to publish the WebJob.
Back in Azure Portal, we’d see our WebJob. Click on Run to start the WebJob. And click on Logs.
As expected we’d get the SQL Exception as Web Job will not be able to connect to the On-Prem Database.
Now let us configure Hybrid Connection to get the WebJob up and running properly. Inside the App Service select Networking and click on Configure your hybrid connection endpoints.
Click on Add hybrid Connection.
Here Endpoint Host will be the name of our OnPrem Machine\Server, Endpoint Port will be the Port for the SQL Server (1433 for the default instance).
Next step is to install and configure Hybrid Connection Manager.
Once installed, open the Hybrid connection manager and click on Add a new Hybrid Connection
Log in with the Azure Subscription Credentials and select the Hybrid Connection created there.
If everything is correct, it should show the status as connected.
*I had to restart the Azure Hybrid Connection Manager Service after adding the connection for the Azure status to show as connected
Now back in our WebJob, let us click on Run.
we’d see the data successful fetched from our SQL On-Prem DB.
In case of named instance of SQL, we need to create a new hybrid connection with the specific TCP Port used by that named instance.
To find the port used by the named instance, open SQL Server Configuration Manager, select the named instance of SQL and copy the value of TCP Dynamic Ports.
This is how our Hybrid Connection string will look like
The other important point to remember is that the connection string used should also specify the port.
Hope it helps..
Business Applications communities