Chrome!)Ģ) navigate to (or whatever servername/port you used)ģ) continue to the website and ignore the certificate errorĤ) press at the popup the asks for credentialsĥ) now click on the “Certificate error” in the menu bar and press “View certificates” (I’m serious here, this only works with IE but not with e.g. This can be done by following these steps:ġ) Launch Internet Explorer using “Run as Administrator”
Azure cloudapp ssl install#
In order to make it a trusted certificate you need to install it on the client. What actually happens in the background is that the request to the Power BI OData service gets redirected to the server and the client connects directly to the server:Īnd this is also where our PQ error originates as the certificate used is not a trusted certificate on the client. Until that point I always thought that the data is load through the cloud and there is no direct connection from my client to the server: But here comes the error in my thinking that I was not aware of before talking to Benjamin Tang and Samuel Zhang from the product team. That’s a bit surprising as the DMG is configured correctly using HTTPS and the very same OData feed worked just fine with HTTP. You will find all of them but as soon as you try to load the data you will receive the following error:
![azure cloudapp ssl azure cloudapp ssl](https://rzetelnekursy.pl/wp-content/uploads/2019/04/042819_1850_AzureApplic1.png)
Now you can use Excel and Power Query to search for your data sources that are published via OData.
![azure cloudapp ssl azure cloudapp ssl](https://cloudacademy.com/wp-content/uploads/2017/03/Screenshot-2017-03-14-17.37.23.png)
Once you click it takes some time (~1 Minute) until everything is updated and HTTPS connectivity can be used. Makecert -r -pe -n “CN= ” -b -e -eku 1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp “Microsoft RSA SChannel Cryptographic Provider” -sy 12Īfter you run the command the new certificate is automatically added to your users personal certificates and can be used when setting up HTTPS connectivity for your DMG: Your MakeCert-command should look similar to this: This is very import, otherwise the final connection will not work!
Azure cloudapp ssl full#
The important thing here is to use the full qualified server name: CN= To create a self-signed certificate you can simply follow the steps as described here. You should already be familiar with 1) and 2) as you needed to do the same steps also for your HTTP port of your DMG (default is port 8051 here).
![azure cloudapp ssl azure cloudapp ssl](https://www.returngis.net/wp-content/uploads/2018/06/App-Gateway-Overview-section.png)
This may work in a corporate hybrid environment where everything is set up correctly but for a non-Azure VM this is a bit more complicated and this is what this post is about.īesides the initial setup from my previous post there are some steps you need to do in advance in order for HTTPS connectivity to work:ġ) Open the port that the DMG HTTPS connection uses in your Windows Firewall (default is port 8050)Ģ) Create an Endpoint for your Azure VM for the very same portģ) Create a self-signed certificate to be used to establish a secure connection Finally select your certificate and you are ready to go! Simply open your DMG, go to Settings and change from HTTP to HTTPS.
![azure cloudapp ssl azure cloudapp ssl](https://miro.medium.com/max/1104/1*mNZbJgat89nI24U4thLvTw.png)
So make sure that you have all prerequisites up and running before you continue reading.īasically, the process to switch to HTTPS is pretty straight forward. The final setup is also the starting-point for this post where we will use self-signed certificates to use HTTPS/SSL connectivity to our DMG.
Azure cloudapp ssl how to#
In my previous post I showed how to setup a Power BI Data Management Gateway on a non-domain Azure VM.