<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Raghavendra BN on Medium]]></title>
        <description><![CDATA[Stories by Raghavendra BN on Medium]]></description>
        <link>https://medium.com/@raghavendra.bagalurnagesha?source=rss-4c530cedd5cf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*O0SxlbBORII58nkyuMaZEg.jpeg</url>
            <title>Stories by Raghavendra BN on Medium</title>
            <link>https://medium.com/@raghavendra.bagalurnagesha?source=rss-4c530cedd5cf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:31:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@raghavendra.bagalurnagesha/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cloud Costs Optimization using INFRACOST]]></title>
            <link>https://medium.com/version-1/cloud-costs-optimization-using-infracost-603b620c2493?source=rss-4c530cedd5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/603b620c2493</guid>
            <dc:creator><![CDATA[Raghavendra BN]]></dc:creator>
            <pubDate>Wed, 10 Jan 2024 15:36:43 GMT</pubDate>
            <atom:updated>2024-01-10T15:36:43.733Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yZDgeIsChf1um3wN" /></figure><p>In today’s world, most applications are cloud-based, offering scalability, efficiency, and flexibility. Managing the costs for these resources or services in the cloud becomes a significant challenge, where the resources not being used efficiently will result in a spike in total cost overnight. Also managing infrastructure efficiently is very crucial. And it becomes easy when <strong>Terraform</strong> is used, an Infrastructure as a Code (IaC) tool that helps provision and manage the infrastructure in a declarative manner.</p><p>In this blog, we will explore how <strong>Infracost, Terraform, </strong>and <strong>Azure DevOps</strong> <strong>YAML </strong>pipelines can be combined to optimize costs and streamline the process.</p><h4><strong><em>What is Infracost?</em></strong></h4><p>For those who are new to <strong>Infracost, </strong>it is a robust tool that enables a shift-left approach for cloud costs by providing cost estimates for <strong>Terraform</strong> before deployment. This allows developers and the DevOps Team to estimate and track costs associated with the infrastructure changes. With <strong>Infracost, </strong>we can gain visibility into the financial implications of our <strong>Terraform </strong>code before applying them, enabling us to make decisions before resource provisioning. It supports popular cloud providers like Azure, AWS, and GCP. <a href="https://www.infracost.io/docs/"><strong>Click<em> </em>here</strong></a> to learn more about the tool.</p><p>We can use the Infracost CLI in a Script YAML task or the extension available in Azure DevOps [<a href="https://marketplace.visualstudio.com/items?itemName=Infracost.infracost-tasks">Marketplace</a>], but I will explain the <strong>Infracost</strong> usage as a customized task in YAML.</p><h4>Pre-Requisites:</h4><ul><li>An <strong>Azure</strong> account (you can use a free trial. If you don’t have one, you can <a href="https://azure.microsoft.com/free/"><strong>create an account for free</strong></a>)</li><li><strong>Azure DevOps</strong> (If you need help getting started, see <a href="https://azure.microsoft.com/en-us/services/devops/?nav=min"><strong>Create </strong></a>one)</li><li>Terraform code within Azure Repo</li><li>Familiarity with Azure DevOps tasks (YAML-based)</li><li>Service Connection in Azure DevOps (that connects to Azure account)</li><li>Sign up to Infracost (<a href="https://login.infracost.io/login?state=hKFo2SBYNWdyNmFsVEY0Wk16SEVlcF8tWHhlb19STzQ0UHFiUqFupWxvZ2luo3RpZNkgdDJEeWxJSTBKb2JlMGxrTmM0aS1Vb2JnamJwVWdXVVijY2lk2SBRVDc3T0pwRm9FOFZLMDdORkFGMXpINkNDVzhYU1ZXUA&amp;client=QT77OJpFoE8VK07NFAF1zH6CCW8XSVWP&amp;protocol=oauth2&amp;audience=https%3A%2F%2Fdashboard.api.infracost.io&amp;icSource=web&amp;redirect_uri=https%3A%2F%2Fdashboard.infracost.io&amp;scope=openid%20profile%20email%20offline_access&amp;response_type=code&amp;response_mode=query&amp;nonce=TXZiNE1vflhjT24wS0g0UzVpbFJXeXJib0RwYjRQYzNpbk5BRHVkX2h5VA%3D%3D&amp;code_challenge=uG4aSg1ewA89g116XdlyIVAgi83ykrCkFNc3pt9JzSg&amp;code_challenge_method=S256&amp;auth0Client=eyJuYW1lIjoiYXV0aDAtcmVhY3QiLCJ2ZXJzaW9uIjoiMS4xMC4yIn0%3D">Sign-up</a>)</li><li>Infracost API Key</li></ul><p><strong>Getting Infracost API Key</strong></p><p>To get the <strong>Infracost API Key, </strong>log in to your Infracost account, and navigate to <strong>Org Settings</strong> on the top bar next to your profile, API Key can be found under the General tab, copy and add it as a value to the “<strong>INFRACOST_API_KEY</strong>” variable within the Variable groups of Library in Azure DevOps.</p><h4><strong>Customizing Tasks in Azure DevOps YAML</strong></h4><p>To integrate Infracost within the Azure DevOps YAML pipelines, we can create a script task that executes the Infracost CLI. I will be using bash whereas we can also use PowerShell Core. We can include this task before the <strong>terraform plan</strong>.</p><p><strong>Installing Infracost</strong></p><p>The below script task downloads and installs Infracost using its installation script from the specified GitHub URL. The environment variables are set to configure the behavior of dotnet CLI during the installation process.</p><pre>- script: |<br>      # Install Infracost<br>      curl -sSL https://raw.githubusercontent.com/infracost/infracost/master/scripts/install.sh | sh<br>    displayName: &#39;Install Infracost&#39;<br>    env:<br>      DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true<br>      DOTNET_CLI_TELEMETRY_OPTOUT: 1</pre><p><strong>Executing Infracost</strong></p><p>The below script task is responsible for running the Infracost analysis on the Terraform code. It extracts the Infracost API key from the environment variable and then executes the <em>infracost breakdown</em>. The primary function of the <em>infracost breakdown </em>command is to analyze the terraform code and provide a detailed breakdown of estimated costs. It considers factors such as resource configurations, service pricing, and usage information to calculate the potential costs associated with each resource. The <em>infracost breakdown </em>command generates an output in JSON format when we point Infracost to a Terraform directory using the --path flag.</p><p>--path specifies the path to the Terraform code directory.</p><p>--show-skipped specifies the resources that are skipped where Infracost considers non-billable or has limitations in costing.</p><pre>  - script: |<br>      infracostApiKey=$(echo &quot;$(INFRACOST_API_KEY)&quot; | tr -d &#39;\r&#39;)<br>      infracost breakdown --path $(Build.SourcesDirectory)/. --show-skipped<br>    displayName: &#39;Run Infracost&#39;</pre><p><strong>NOTE</strong>: We need to pass <strong>Infracost API Key</strong> as an “<strong>INFRACOST_API_KEY</strong>” variable within the Variable groups of Library in Azure DevOps and link this Variable group to the respective pipeline.</p><h4><strong>Leveraging Cost Insights</strong></h4><p>By incorporating Infracost within the Azure DevOps YAML Pipelines, we gain valuable insights into the cost of the resources that will be provisioned/modified. Below is the sample output of the cost breakdown when the Pipeline is run. This output not only provides a quick overview of the estimated costs but also guides approvals on actionable steps for further optimization and understanding of the infrastructure’s financial aspects. Based on the output, we can implement additional steps within the pipeline where we might set up checks for overspeeding against a predefined budget or notify relevant stakeholders.</p><p><strong><em>Summary of Output</em></strong>:</p><pre>Overall Detected Resources: 13<br>Estimated Resources: 9(3 with usage-based costs)<br>Free Resources: 3(eg. azurerm_key_vault, azurerm_resource_group, etc)<br>Not supported yet: 1 (azurerm_storage_table)</pre><p>Explore <a href="https://www.infracost.io/docs/features/usage_based_resources/#usage-profiles">Infracost Usage Profiles</a> for configuring usage-based costs.</p><p>Also, check the <a href="https://github.com/infracost/infracost/issues?q=is%3Aissue+is%3Aopen+label%3A%22new+resources%22">list of unsupported resources</a> to stay informed about upcoming Infracost updates.</p><pre>Project: MyADOV1/Test Platform/IAC<br><br> Name                                            Monthly Qty  Unit                      Monthly Cost <br>                                                                                                     <br> azurerm_app_service_plan.plan                                                                       <br> └─ Instance usage (S1)                                  730  hours                           $91.25 <br>                                                                                                     <br> azurerm_application_insights.appi                                                                   <br> └─ Data ingested                         Monthly cost depends on usage: $2.30 per GB                <br>                                                                                                     <br> azurerm_monitor_action_group.dapx_alert                                                             <br> └─ Email notifications (1)               Monthly cost depends on usage: $0.00002 per emails         <br>                                                                                                     <br> azurerm_storage_account.app_sa                                                                      <br> ├─ Capacity                              Monthly cost depends on usage: $0.0192 per GB              <br> ├─ Write operations                      Monthly cost depends on usage: $0.059 per 10k operations   <br> ├─ List and create container operations  Monthly cost depends on usage: $0.059 per 10k operations   <br> ├─ Read operations                       Monthly cost depends on usage: $0.0047 per 10k operations  <br> ├─ All other operations                  Monthly cost depends on usage: $0.0047 per 10k operations  <br> └─ Blob index                            Monthly cost depends on usage: $0.0376 per 10k tags        <br>                                                                                                     <br> OVERALL TOTAL                                                                                $91.25 <br>──────────────────────────────────<br>13 cloud resources were detected:<br>∙ 9 were estimated, 3 of which include usage-based costs, see https://infracost.io/usage-file<br>∙ 3 were free:<br>  ∙ 1 x azurerm_key_vault<br>  ∙ 1 x azurerm_key_vault_secret<br>  ∙ 1 x azurerm_resource_group<br>∙ 1 is not supported yet, see https://infracost.io/requested-resources:<br>  ∙ 1 x azurerm_storage_table<br><br>┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┓<br>┃ Project                                            ┃ Monthly cost ┃<br>┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━┫<br>┃ MyADOV1/Test Platform/IAC                          ┃ $91          ┃<br>┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┻━━━━━━━━━━━━━━┛<br><br>Finishing: Run Infracost</pre><p>Output of Azure DevOps Pipeline:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*Ls0r4tglKfKhD3tUjVXdvQ.png" /></figure><h4>Conclusion</h4><p>It’s worth considering the Infracost for its ability to provide detailed insights into the resource costs, enabling the individuals to make informed decisions before provisioning.</p><p><strong>Use Cases:</strong></p><ul><li>Cost control - Offering a detailed breakdown of resource costs, allowing users to identify and optimize resources.</li><li>Decision making - Providing insights into potential costs before provisioning or applying changes.</li><li>Continuous Optimization - Integrating Infracost into CI-CD pipelines for ongoing cost management.</li></ul><p><strong>Limitations:</strong></p><ul><li>Incomplete resource support - Infracost does not support all types of resources and there are few exceptions.</li><li>Usage costs - While Infracost helps in analyzing resource costs, but does not factor in usage costs.</li></ul><p><strong>About the Author:</strong></p><p>Raghavendra BN is a DevOps Engineer, currently working in Version 1’s UKDDC practice. Follow Version 1 and Raghavendra BN for more blogs around Microsoft Azure and Azure DevOps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=603b620c2493" width="1" height="1" alt=""><hr><p><a href="https://medium.com/version-1/cloud-costs-optimization-using-infracost-603b620c2493">Cloud Costs Optimization using INFRACOST</a> was originally published in <a href="https://medium.com/version-1">Version 1</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes Version 1 company a great place to work?]]></title>
            <link>https://medium.com/version-1/what-makes-version-1-company-a-great-place-to-work-5417be24c05?source=rss-4c530cedd5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/5417be24c05</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[greatplacetowork]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[job-search]]></category>
            <dc:creator><![CDATA[Raghavendra BN]]></dc:creator>
            <pubDate>Tue, 17 Jan 2023 17:22:50 GMT</pubDate>
            <atom:updated>2023-01-18T10:09:26.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IMNzoFgUM0Y5L43337QjaQ.jpeg" /></figure><p>Most employees will not only look at the salary or perks and benefits while joining the company, instead, employees also look towards the culture, opportunities for upward mobility, job security, and technology. Employees do their best work when they feel like they are part of a company with strong values.</p><p>So what makes <a href="https://medium.com/u/2d7d2784f29a">Version 1</a> company achieve this? Well, the mantra for this lies in two simple words — <strong>Employee Engagement. </strong>Now I know what makes a company a great place to work because I’m part of a company that has been recognized as a “<strong>Great Place to Work</strong>” for many times across Ireland, the United Kingdom, India, and Spain.</p><p>Here are a few reasons from my perspective that made Version 1 create a healthy work environment and sustain work-life balance. I’m proud to say that I’m one of the <a href="https://medium.com/u/2d7d2784f29a"><strong>Version 1</strong></a><strong> Stalwarts</strong>.</p><ol><li><strong>Core Values:<br></strong>Core Values serve to constantly guide both the employee and the company in achieving the goals, in a manner that is based on an ethical and ideological framework. As an organization, <strong>Version 1</strong> has six core values, that are shown below, by which every employee are abiding.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*ASnpwYSCgrfytWd7T2N3pQ.png" /><figcaption>Version 1 Core Values</figcaption></figure><p><strong>2. Performance Appreciation:<br></strong>When an employee does something great or intelligent work, something that delights a customer and it never goes unnoticed at <strong>Version 1</strong>. There will always be recognition or appreciation through <strong>Callout and Excellence Awards </strong>to make sure that the person or team gets their due appreciation so the motivation rubs off on everyone the same.</p><p>I also got an opportunity to travel to Dublin for over a month as a token of appreciation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2vfgHiItgYxZD8kzCnxuA.jpeg" /><figcaption>Recognition Award</figcaption></figure><p><strong>3. Flexibility:<br></strong>Flexible work culture is one of the nice things about <strong>Version 1</strong>. Flexibility and agility in work schedules promote a healthy work-life balance in employees. Since Covid-19, it has been remote work and so far it is not mandatory for employees to return to the office. This makes the offer flexible working hours, and enjoy more time with the family, thereby limiting stress, dissatisfaction, and burnout.</p><p><strong>4. Corporate Social Responsibility (CSR):<br></strong>Giving back to the community is a virtuous circle and <strong>Version 1</strong> has done this for many years. Many <strong>Version 1</strong> employees voluntarily take part in various CSR activities to do the needful for society and people across multiple parts of the globe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XfYbHwqLweAvoCM8SlbRdQ.jpeg" /><figcaption>CSR activities</figcaption></figure><p><strong>5. Share the wealth:<br></strong>Quarterly profit share is offered to the employees based on Individual performance ratings and the company’s earnings within that particular quarter. This is something additional to the actual salary that employees get.</p><p><strong>6. Opportunity:<br></strong>There is always room for opportunity for those who are willing to upskill on different tech-stack. Most of the time employees will be engaged with the work be it either billable or non-billable projects than being on the bench soon after finishing the tagged projects.</p><p><strong>7. Transparent Management:<br></strong>The management hierarchy is transparent in <strong>Version 1</strong>. One can freely talk or share ideas with seniors. The company has introduced the <strong>Shadow Board</strong> concept, where employees aged below the 30s can be part of the <strong>Shadow Board</strong> through the defined process and can pass on their views/ideas to Executive Board members. I’m happy to be part of the <strong>2023 Shadow Board Team</strong>.</p><p><strong>8. 1:1 Conversation with Reporting Manager:<br></strong>Frequent 1:1 conversation with the Line Manager/Reporting Manager helps to gain a deeper insight into the levels of engagement and motivation. These conversations allow for both standardized questioning and free-flowing conversation with the Manager. This also provides regular feedback to see the areas for improvement.</p><p><strong>Conclusion</strong></p><p>There are so many other reasons that make <strong>Version 1</strong> a “<strong>Great Place to Work</strong>”. No doubt that Version 1 is a fun-filled place to work. It organizes so many events for the employee’s benefit. The company also conducts <strong>Employee Survey</strong> every quarter which makes them measure employees&#39; point of view towards the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*McYaBtiCLVgL4Sor3E-UVQ.jpeg" /><figcaption>#insideversion1</figcaption></figure><p><strong>About the Author:<br></strong>Raghavendra BN is a DevOps Engineer, currently working in Version 1’s Foundation’s team. Follow Version 1 and Raghavendra BN for more blogs around Microsoft Azure and Azure DevOps.</p><p>To look at our current vacancies visit our careers page <a href="https://www.version1.com/careers/">here</a>.</p><p>You can also find out more information about the awards we received in 2022 by checking out our <a href="https://www.youtube.com/watch?v=j9jkMYDPNIw">Youtube channel</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5417be24c05" width="1" height="1" alt=""><hr><p><a href="https://medium.com/version-1/what-makes-version-1-company-a-great-place-to-work-5417be24c05">What makes Version 1 company a great place to work?</a> was originally published in <a href="https://medium.com/version-1">Version 1</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build and Deploy Angular Application to Azure Static Web App using Azure DevOps]]></title>
            <link>https://medium.com/version-1/build-and-deploy-angular-application-to-azure-static-web-app-using-azure-devops-264f846d63f5?source=rss-4c530cedd5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/264f846d63f5</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Raghavendra BN]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 12:17:33 GMT</pubDate>
            <atom:updated>2022-10-07T13:37:59.732Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jpzq2pY60JdMFcuP" /></figure><p><strong>Azure Static Web App</strong> is a modern web app service that offers streamlined full-stack development from source code to high global availability. The benefits include a seamless developer experience that includes a Visual Studio Code extension, CICD, and much more.</p><p>Microsoft made the service “GA” (generally available) and currently supports 2 plans. The free plan allows you to get started free while the standard plan includes all of the free features as well as the ability to customize functionality such as authentication and APIs.</p><p>In this post, I will walk you through building and deploying an Angular application to Azure static web app using two separate YAML-based pipelines(Build &amp; Deploy) in Azure DevOps.</p><h4>Pre-Requisites:</h4><ul><li>An <strong>Azure</strong> account (you can use a free trial, If you don’t have one, you can <a href="https://azure.microsoft.com/free/"><strong>create an account for free</strong></a>)</li><li><strong>Azure DevOps</strong> (If you need help getting started, see <a href="https://azure.microsoft.com/en-us/services/devops/?nav=min"><strong>Create </strong></a>one)</li><li>Angular code within Azure Repo</li><li>Familiarity with Azure DevOps tasks</li></ul><h4>Create Static Web App:</h4><p><strong>Step 1</strong>: Navigate to the Azure portal, create a new resource by searching for Static Web apps, and click “create”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*MtMe7H2dan8SmrDjCx6GoQ.png" /></figure><p><strong>Step 2</strong>: Fill out the details by choosing the subscription and resource group. Then go with the Static Web App details: choose the name — “my-first-angular-app” — and stick with the Free plan. Then select your region — mine is “West Europe”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*uChj0Z0MZqSK5lBysu3yLQ.png" /></figure><p><strong>Note</strong>: Since I am going to leverage Azure DevOps as the deployment method, I selected “<em>Other”</em> as the option.</p><p><strong>Step 3</strong>: So, now you’re ready to create your Static Web App. Hit “Review+create” and see what happens. This is the overview of my app:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BFHuW__NbKNuR7I_1wMGMw.png" /></figure><p><strong>Step 4</strong>: Once the deployment is successful, navigate to the newly created Static Web Apps resource and select <em>Manage deployment token </em>from the overview page. Make a note of this value for the next steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TRJ6bqaIYqpayahKN44_vg.png" /></figure><h4>Create the Pipeline task in Azure DevOps:</h4><p>We will be creating two pipelines, one for build and one for deployment using the YAML file. We can have this YAML file within the repo in advance or we can append the same during pipeline creation.</p><p><strong>Note</strong>: Please keep the Angular code within the Azure Repo before creating the pipeline.</p><h4>Build Pipeline:</h4><p><strong>Step 1</strong>: Log into the Azure DevOps project where the angular code is residing. Click on <em>Pipelines</em> on the left.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a3KgV5cuO2irElYlnFQ7lw.png" /></figure><p><strong>Step 2</strong>: Click <em>New Pipeline</em> and select <em>Azure Repos Git</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*q9m6eKF-n6sBLVE50_aCsw.png" /></figure><p><strong>Step 3</strong>: Select the <em>Azure repo name</em> where the angular code is kept.</p><p><strong>Step 4</strong>: Click <em>Starter Pipeline </em>to write the YAML file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*jrmCuDKyyIFJReUYPF58uw.png" /></figure><p><strong>Step 5</strong>: Copy and Paste the below content within the <em>Starter Pipeline</em> section.</p><pre># Build pipeline<br>trigger:<br>  batch: false<br>  branches:<br>    include:<br>     - master<br>  paths:<br>    exclude:<br>     - readme.md</pre><pre>pool:<br>  vmImage: ubuntu-latest</pre><pre>steps:<br> - task: NodeTool@0<br>   displayName: &#39;Use Node 14.x&#39;<br>   inputs:<br>     versionSpec: 14.x</pre><pre> - script: |<br>     npm install -g @angular/cli<br>   displayName: &#39;install angular cli&#39;</pre><pre> - task: Npm@1<br>   displayName: &#39;npm install &#39;<br>   inputs:<br>     workingDir: &#39;$(System.DefaultWorkingDirectory)&#39;<br>     verbose: false</pre><pre> - task: Npm@1<br>   displayName: &#39;npm build&#39;<br>   inputs:<br>     command: custom<br>     workingDir: &#39;$(System.DefaultWorkingDirectory)&#39;<br>     verbose: false<br>     customCommand: &#39;run build&#39;</pre><pre> - task: PublishBuildArtifacts@1<br>   inputs:<br>     PathtoPublish: &#39;dist&#39;<br>     ArtifactName: &#39;app&#39;<br>     publishLocation: &#39;Container&#39;</pre><p>For a better understanding of directory structure visit <a href="https://docs.microsoft.com/en-us/azure/static-web-apps/build-configuration?tabs=github-actions">Build Configuration</a></p><p><strong>Step 6</strong>: Click <em>Save and Run</em>.</p><h4><strong>Deploy Pipeline:</strong></h4><p>Repeat the above Step 1 to Step 4 to create a deploy pipeline.</p><p><strong>Step 5</strong>: Copy and Paste the below content within the <em>Starter Pipeline</em> section.</p><pre># Deploy pipeline<br>trigger:<br> batch: false<br> branches:<br>  include:<br>  - master<br> paths:<br>  exclude:<br>  - readme.md</pre><pre>stages:<br> - stage: Deploy<br>   pool:<br>     vmImage: &#39;ubuntu-latest&#39;<br>   jobs:<br>    - job: DeployWebAppProd<br>      steps:<br>       - task: DownloadPipelineArtifact@2<br>         inputs:<br>           buildType: &#39;specific&#39;<br>           project: &#39;ab43f2c4-cbec-8f34-b6a6-b1b96af2c4bf&#39;<br>           definition: &#39;408&#39;<br>           buildVersionToDownload: &#39;latest&#39;<br>           allowPartiallySucceededBuilds: true<br>           allowFailedBuilds: true<br>           artifactName: &#39;app&#39;<br>           targetPath: &#39;$(Pipeline.Workspace)&#39;</pre><pre>       - bash: cd $(Pipeline.Workspace); echo $(ls)</pre><pre>       - bash: cd $(Pipeline.Workspace)/app; echo $(ls)</pre><pre>       - task: AzureStaticWebApp@0<br>         inputs:<br>           cwd: &#39;$(Pipeline.Workspace)&#39;<br>           app_location: &#39;/&#39;<br>           skip_app_build: true<br>           skip_api_build: true<br>           verbose: true<br>         env:<br>           azure_static_web_apps_api_token: &#39;$(deployment_token)&#39;</pre><p><strong>Note</strong>: Replace the values within the <em>DownloadPipelineArtifact@2</em> task based on your values.</p><p><strong>Step 6</strong>: We need to provide the <strong><em>azure_static_web_apps_api_token </em></strong>value. To do that select <strong><em>Variables</em></strong> in the pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g9F4prTcRfGDk3VlDEw8DQ.png" /></figure><p><strong>Step 7</strong>: Create a new variable named <strong><em>deployment_token</em></strong> (same as the above name mentioned in release YAML). Check the <strong><em>keep this value secret</em></strong> box and click <strong>Ok</strong>. Finally, <strong><em>Save and run.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*kVJ6hS3DdYnqbbdt9IcnlQ.png" /></figure><p>The pipeline will execute and deploy the application to azure static web apps. Now you can access the application using the static web app URL.</p><p><strong>Conclusion:</strong></p><p>I hope this detail has shown how to build and deploy the Angular application using Azure DevOps to Azure static web app with two separate YAML files.</p><p><em>If you found this interesting or have any feedback, please let me know in the comments section.</em></p><p>Happy learning!</p><p><strong>About the Author:<br></strong>Raghavendra BN is a DevOps Engineer, currently working in Version 1’s Foundation’s team. Follow Version 1 and Raghavendra BN for more blogs around Microsoft Azure and Azure DevOps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=264f846d63f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/version-1/build-and-deploy-angular-application-to-azure-static-web-app-using-azure-devops-264f846d63f5">Build and Deploy Angular Application to Azure Static Web App using Azure DevOps</a> was originally published in <a href="https://medium.com/version-1">Version 1</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configuring of Data Gateway in Power BI]]></title>
            <link>https://medium.com/version-1/configuring-of-data-gateway-in-power-bi-f7f95882f19?source=rss-4c530cedd5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7f95882f19</guid>
            <category><![CDATA[power-bi]]></category>
            <category><![CDATA[powerapps]]></category>
            <category><![CDATA[powerplatform]]></category>
            <category><![CDATA[data-gateway]]></category>
            <category><![CDATA[configuration]]></category>
            <dc:creator><![CDATA[Raghavendra BN]]></dc:creator>
            <pubDate>Thu, 26 May 2022 09:26:49 GMT</pubDate>
            <atom:updated>2022-05-26T09:41:07.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/508/0*QnQqHHcfrVRTwtVy" /></figure><p>In order to perform a scheduled refresh, we will need to install the Power BI data gateway.</p><ol><li>From Power BI Online, go ahead and click on the [Downloads] button located on the top right corner &gt;&gt; Select the [Data Gateway].</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*nOdPHQR8IMfSqatS3Gm4fQ.png" /></figure><p>2. Run the installer and select the appropriate Gateway installation type. We will be provided with 2 options:</p><ul><li>Enterprise that can be shared and reused by multiple users, support Power BI, PowerApps, Logic Apps and Microsoft Flow too</li><li>Or Personal mode that can only be used by individual and Power BI</li></ul><p>3. Other factors such as the location of the installation of the gateway, the network that is in place and the policy regarding gateway within our organization might impact which type of installation we will be setting. Note though that if we install the gateway on a personal computer, the gateway will not run when our computer is turn off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*eerkOyzfRrcG0zDqQqCvrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*aTZOzsRQrudUkm-r0MBysw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*bPLlfpvHQy1e_Kr6jbEhpA.png" /></figure><p>4. Once we have completed the installation, go back to Power BI Online and go to the [Manage Gateways]. Select [Add data sources to use the gateway].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*u-9gIAlyRHYdIu_xyqezhg.png" /></figure><p>5. On the next screen, ensure we are selecting the [ODBC] data source type and set up the right Connection String to the Server, Database, Username and password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*ja1GHHe-de9903ZXHRDbrg.png" /></figure><p><strong>Note</strong>: For connection string pass the value in the below format</p><blockquote><strong>database={database name};driver={PostgreSQL Unicode(x64)};port=5432;server={private IP of postgresql};sslmode=require</strong></blockquote><p>6. Once the connection is successfully established, go to the [Users] tab and tick the relevant users to add them to the Data Source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*khrdv6HlE1hyw2CAUf8V6A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*i-Yk2arj7w7mg7uLkzBkMA.png" /></figure><p>7. We need to ensure that the dataset is running the proper gateway connection. In order to do that click on the dataset and select [Schedule Refresh].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Gz9XNbXETC7Av6Y8_lKWfw.png" /></figure><p>8. On the next screen ensure that we are selecting the right [Gateway connection].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*xNOM8sCQHRQyrbE4Y_4ZFg.png" /></figure><p>9. Then turn on the [Scheduled refresh] option to ensure that we can setup the refresh frequency. With the current license of Power BI we are using (Power BI for Office 365) we are only able to schedule for [Daily] refreshes and setup a maximum of 8 time for refresh:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*KGe1ZqeP2I9yWk9dss6Shw.png" /></figure><p>10. Once we click on [Apply] we should be able to see a success message.</p><p>11. We can also now test the manual refresh of the dataset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*SV_OxZZC0OkrfT83OF6CYw.png" /></figure><h3><strong>Conclusion</strong></h3><p>We can see Power BI Service connect managed database through On premise Data Gateway. Some configurations are tricky, but they are not difficult.</p><p><em>If you found this interesting or have any feedback, please let me know in the comments section.</em></p><p><strong>This blog is part four of a four-part series: <br></strong><a href="https://medium.com/version-1/vnet-integratedpostgresql-integration-with-power-bi-app-12950039e687">Part 1 — Creating Virtual Network and PostgreSQL</a><br><a href="https://medium.com/version-1/creating-and-configuring-virtual-network-gateway-point-to-site-using-azure-certification-7a5b61839e54">Part 2 — Creating and Configuring Virtual Network Gateway (Point-to-Site)</a><br><a href="https://medium.com/version-1/installing-odbc-driver-for-remote-connection-to-postgresql-db-9b8d496e50e4">Part 3 — Installing ODBC driver for remote connection to PostgreSQL DB</a></p><p><strong>About the Author:<br></strong>Raghavendra BN is a DevOps Engineer, currently working in Version 1’s Foundation’s team. Follow Version 1 and Raghavendra BN for more blogs around Microsoft Azure and Azure DevOps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7f95882f19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/version-1/configuring-of-data-gateway-in-power-bi-f7f95882f19">Configuring of Data Gateway in Power BI</a> was originally published in <a href="https://medium.com/version-1">Version 1</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing ODBC Driver for Remote Connection to PostgreSQL DB]]></title>
            <link>https://medium.com/version-1/installing-odbc-driver-for-remote-connection-to-postgresql-db-9b8d496e50e4?source=rss-4c530cedd5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b8d496e50e4</guid>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[odbc]]></category>
            <category><![CDATA[dbms]]></category>
            <dc:creator><![CDATA[Raghavendra BN]]></dc:creator>
            <pubDate>Thu, 26 May 2022 09:26:08 GMT</pubDate>
            <atom:updated>2022-05-26T09:41:22.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*lA0LO_nViOG_rIsE" /></figure><p>Open Database Connectivity (ODBC) is a standard API for accessing DBMS. ODBC has been designed to be independent of databases and operating systems.</p><p>To set up a new ODBC data source for PostgreSQL:</p><ol><li>Install the latest PostgreSQL ODBC drivers:</li></ol><blockquote>* Download the latest 64 bit driver installer (zipped msi file) from the <a href="https://www.postgresql.org/ftp/odbc/versions/msi/">psqlodbc download site</a>.</blockquote><blockquote>* Unzip the file.</blockquote><blockquote>* Run the msi installer and accept the defaults.</blockquote><p>2. Open the 64 bit ODBC Administrator:</p><p>Windows 10 (64 bit version) supports 32 and 64 bit ODBC sources — always use the 64 bit ODBC Administrator.</p><blockquote>*Search for ODBC and choose ODBC Data Sources (64 bit):</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*L5p5qE5SDJXHDDuZfJyG5g.png" /></figure><blockquote>*Right Click and choose <strong>Run as Administrator</strong>:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*5wU34qcPUKBCWqm-vSPjIQ.png" /></figure><p>3. Open the <strong>System DSN</strong> tab and click <strong>Add</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*tknZY8emN89msan-Imwl4g.png" /></figure><p>4. Choose the latest PostgreSQL ODBC driver and click <strong>Finish</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*TvYg_iUMe2nZxhLwloAiCg.png" /></figure><p>5. Test the connection by using <strong>Azure Data Studio.</strong></p><p>i) Make sure we are connected to VPN.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*ytoPeHdSVriLCwAiJZG-XA.png" /></figure><p><strong>ii)</strong> Open <strong>Azure Data Studio </strong>and Click on <strong>New Connection.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*VKpRsD2UxIbaZ3JVgWgwDg.png" /></figure><p><strong>iii)</strong> Fill the required details of PostgreSQL which needs to be connected (Enter the <strong>private IP</strong> of postgresql instead of dns name). Click <strong>Connect.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*6j9rMk1axpRv8PAvOe0ulw.png" /></figure><p>iv) Once the <strong>connection</strong> is <strong>successful</strong>, <strong>databases</strong> gets loaded.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*BgOy55KyUcNywtSQArykBw.png" /></figure><p><strong>This is part three of a four-part series that can be viewed below:</strong><br><a href="https://medium.com/version-1/vnet-integratedpostgresql-integration-with-power-bi-app-12950039e687">Part 1 — Creating Virtual Network and PostgreSQL</a><br><a href="https://medium.com/version-1/creating-and-configuring-virtual-network-gateway-point-to-site-using-azure-certification-7a5b61839e54">Part 2 — Creating and Configuring Virtual Network Gateway (Point-to-Site)</a><br><a href="https://medium.com/version-1/configuring-of-data-gateway-in-power-bi-f7f95882f19">Part 4 — Configuring a Data Gateway in Power BI</a></p><p><em>If you found this interesting or have any feedback, please let me know in the comments section.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UexPA8bZyfZ2i8ZyBRPXeQ.jpeg" /></figure><p><strong>About the Author:<br></strong>Raghavendra BN is a DevOps Engineer, currently working in Version 1’s Foundation’s team. Follow Version 1 and Raghavendra BN for more blogs around Microsoft Azure and Azure DevOps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b8d496e50e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/version-1/installing-odbc-driver-for-remote-connection-to-postgresql-db-9b8d496e50e4">Installing ODBC Driver for Remote Connection to PostgreSQL DB</a> was originally published in <a href="https://medium.com/version-1">Version 1</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating and Configuring Virtual Network Gateway (Point-to-Site) Using Azure certification…]]></title>
            <link>https://medium.com/version-1/creating-and-configuring-virtual-network-gateway-point-to-site-using-azure-certification-7a5b61839e54?source=rss-4c530cedd5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a5b61839e54</guid>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[virtual-networks]]></category>
            <category><![CDATA[azure-certification]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Raghavendra BN]]></dc:creator>
            <pubDate>Thu, 26 May 2022 09:24:57 GMT</pubDate>
            <atom:updated>2022-05-26T09:41:55.047Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/509/0*eHTGSHJhYCdofFPM" /></figure><h3><strong>Creating and Configuring Virtual Network Gateway (Point-to-Site) Using Azure Certification Authentication</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*ojMVwXsrnla3xiNgquIcVg.png" /></figure><p>Ensuring secure connectivity to database resource is an important requirement and consideration for customers running an in cloud environment. Today customers want to connect to their <a href="https://docs.microsoft.com/en-us/azure/postgresql/"><strong>Azure Database for PostgreSQL</strong></a> from both inside/outside of Azure, and based on the security and compliance requirements, organizations can choose one of the options provided by Azure Database for PostgreSQL. In this section, we will outline detailed steps on how to connect securely from an On-Premise to Azure Database for PostgreSQL using Point-to-Site Gateway.</p><p>A <a href="https://docs.microsoft.com/en-us/azure/vpn-gateway/point-to-site-about"><strong>Point-to-Site (P2S)</strong></a> VPN gateway connection lets us create a secure connection to our virtual network from an individual client computer. A P2S connection is established by starting it from the client’s computer. This solution is useful for telecommuters who want to connect to Azure VNETs from a remote location, such as from home or a conference.</p><p>Point-to-site native Azure certificate authentication connections use the following items, which we configure in this exercise:</p><blockquote>*A route-based VPN gateway.</blockquote><blockquote>*The public key (.cer file) for a root certificate, which is uploaded to Azure. Once the certificate is uploaded, it is considered a trusted certificate and is used for authentication.</blockquote><blockquote>*A client certificate is generated from the root certificate. The client certificate is installed on each client computer that will connect to the VNet. This certificate is used for client authentication.</blockquote><blockquote>*VPN client configuration. The VPN client is configured using VPN client configuration files. These files contain the necessary information for the client to connect to the VNet. The files configure the existing VPN client that is native to the operating system. Each client that connects must be configured using the settings in the configuration files.</blockquote><p>The virtual network gateway uses a specific subnet called the gateway subnet. The gateway subnet is part of the virtual network IP address range that we specify when configuring our virtual network. It contains the IP addresses that the virtual network gateway resources and services use.</p><p>When we create the gateway subnet, we specify the number of IP addresses that the subnet contains. The number of IP addresses needed depends on the VPN gateway configuration that we want to create. Some configurations require more IP addresses than others. Microsoft recommends that we create a gateway subnet that uses a /27 or /28.</p><ol><li>In <strong>Search resources, services, and docs (G+/)</strong> type <strong>virtual network gateway</strong>. Locate <strong>Virtual network gateway</strong> in the Marketplace search results and select it to open the <strong>Create virtual network gateway</strong> page.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*wd-VjySorwpPNMkp6vhgzQ.png" /></figure><p>2. On the <strong>Basics</strong> tab, fill in the values for <strong>Project details</strong> and <strong>Instance details</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Nt-B-xoKVXSbSJsTdYhJHA.png" /></figure><p>3. Specify the values for <strong>Public IP address</strong>. These settings specify the public IP address object that gets associated to the VPN gateway. The public IP address is dynamically assigned to this object when the VPN gateway is created. The only time the Public IP address changes is when the gateway is deleted and re-created. It doesn’t change across resizing, resetting, or other internal maintenance/upgrades of our VPN gateway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*oaS3ZMU5tjdbTnPUFYDAbw.png" /></figure><p>4. Select <strong>Review + create</strong> to run validation.</p><p>5. Once validation passes, select <strong>Create</strong> to deploy the VPN gateway.</p><p>6. <strong>Generate and export certificates for Point-to-site using Powershell.</strong></p><blockquote>a) Generate a <strong>Self-signed</strong> <strong>root certificate.</strong></blockquote><p>i) From a computer running Windows 10 or Windows Server 2016, open a Windows PowerShell console with elevated privileges.</p><p>ii) Use the following script to create the self-signed root certificate. The following script creates a self-signed root certificate named ‘P2SRootCert’ that is automatically installed in ‘Certificates-Current User\Personal\Certificates’. You can view the certificate by opening <em>certmgr.msc</em>, or <em>Manage User Certificates</em>.</p><p><em>$cert = New-SelfSignedCertificate -Type Custom -KeySpec Signature `</em></p><p><em>-Subject “CN=P2SRootCert” -KeyExportPolicy Exportable `</em></p><p><em>-HashAlgorithm sha256 -KeyLength 2048 `</em></p><p><em>-CertStoreLocation “Cert:\CurrentUser\My” -KeyUsageProperty Sign -KeyUsage CertSign</em></p><p>iii) Leave the PowerShell console open and proceed with the next steps to generate a client certificate.</p><blockquote>b) Generate a <strong>Client certificate</strong>.</blockquote><p>i) Use the following command if PowerShell console is not closed after creating the self-signed root certificate. The client certificate that we generate is automatically installed in ‘Certificates — Current User\Personal\Certificates’ on your computer.</p><p>New-SelfSignedCertificate -Type Custom -DnsName P2SChildCert -KeySpec Signature `</p><p><em>-Subject “CN=P2SChildCert” -KeyExportPolicy Exportable `</em></p><p><em>-HashAlgorithm sha256 -KeyLength 2048 `</em></p><p><em>-CertStoreLocation “Cert:\CurrentUser\My” `</em></p><p><em>Signer $cert -TextExtension @(“2.5.29.37={text}1.3.6.1.5.5.7.3.2”)</em></p><blockquote>c) Export the <strong>root certificate public key</strong> (.cer)</blockquote><p>After creating a self-signed root certificate, export the root certificate public key .cer file (not the private key). We will later upload this file to Azure. The following steps helps to export the .cer file for our self-signed root certificate:</p><p>i) To obtain a .cer file from the certificate, open <strong>Manage user certificates</strong>. Locate the self-signed root certificate, typically in ‘Certificates — Current User\Personal\Certificates’, and right-click. Click <strong>All Tasks</strong>, and then click <strong>Export</strong>. This opens the <strong>Certificate Export Wizard</strong>. If we can’t find the certificate under Current User\Personal\Certificates, we may have accidentally opened “Certificates — Local Computer”, rather than “Certificates — Current User”). If we want to open Certificate Manager in current user scope using PowerShell, we type <em>certmgr</em> in the console window.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*aEPYcG4V0-2OYgbBT9yEaw.png" /></figure><p>ii) In the Wizard, click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*qnLGfirOsfsYMPdKJuzQRw.png" /></figure><p>iii) Select <strong>No, do not export the private key</strong>, and then click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/1*7GcIJR-8zD1LU1pEStoEgQ.png" /></figure><p>iv) On the <strong>Export File Format</strong> page, select <strong>Base-64 encoded X.509 (.CER).</strong>, and then click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*hfmrj5PH334kXsuA2JtH6g.png" /></figure><p>v) On the <strong>File to Export screen</strong>, <strong>browse</strong> to the location to which we want to export the certificate. For <strong>File name</strong>, name the certificate file. Then, click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*WiT5ESz-OFf8BlAjLmQbpw.png" /></figure><p>vi) Click <strong>Finish</strong> to export the certificate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*dX-5VZJVcjFi46NNxpSSpA.png" /></figure><p>vii) Your certificate is successfully exported.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/173/1*dOdVYxpLMsOJCTmBEN_kjA.png" /></figure><p>viii) The exported certificate looks similar to this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/153/1*LwNQnTftuqpTflKQS8zHAQ.png" /></figure><p>ix) If we open the exported certificate using Notepad, we see something similar to this example. The section in blue contains the information that is uploaded to Azure. If we open our certificate with Notepad and it does not look similar to this, typically this means we did not export it using the Base-64 encoded X.509(.CER) format. Additionally, if we want to use a different text editor, understand that some editors can introduce unintended formatting in the background. This can create problems when uploaded the text from this certificate to Azure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/373/1*86i6aGvbwQvl4FKiL4lspQ.png" /></figure><blockquote><strong>d)</strong> Export the <strong>Client certificate.</strong></blockquote><p>When we generate a client certificate, it’s automatically installed on the computer that we used to generate it. If we want to install the client certificate on another client computer, we need to export the client certificate that we generated.</p><p>i) To export a client certificate, open <strong>Manage user certificates</strong>. The client certificates that we generated are, by default, located in ‘Certificates — Current User\Personal\Certificates’. Right-click the client certificate that we want to export, click <strong>all tasks</strong>, and then click <strong>Export</strong> to open the <strong>Certificate Export Wizard</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*CR_tnupaYvCEM3zFSAVveQ.png" /></figure><p>ii) In the Certificate Export Wizard, click <strong>Next</strong> to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*G-XGQhbds8xy_ZFKUJdx2w.png" /></figure><p>iii) Select <strong>Yes, export the private key</strong>, and then click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*kvn_cFDdrpQN7LK0EDeyyQ.png" /></figure><p>iv) On the <strong>Export File Format</strong> page, leave the defaults selected. Make sure that <strong>Include all certificates in the certification path if possible</strong> is selected. This setting additionally exports the root certificate information that is required for successful client authentication. Without it, client authentication fails because the client doesn’t have the trusted root certificate. Then, click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*wL31aSip4CnOCiQ2MrUc4w.png" /></figure><p>v) On the <strong>Security</strong> page, we must protect the private key. If we select to use a password, make sure to record or remember the password that we set for this certificate. Then, click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*6mpXa-3wEG_2WRnuWz53hg.png" /></figure><p>vi) On the <strong>File to Export</strong>, <strong>Browse</strong> to the location to which we want to export the certificate. For <strong>File name</strong>, name the certificate file. Then, click <strong>Next</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*VsZUMkTlVtpVA9cf4hc6pQ.png" /></figure><p>vii) Click <strong>Finish</strong> to export the certificate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/373/1*MkX0SwuKeIElMXttOAzoyg.png" /></figure><p>7. Add the <strong>VPN Client address pool.</strong></p><p>The client address pool is a range of private IP addresses that we specify. The clients that connect over a Point-to-Site VPN dynamically receive an IP address from this range. Use a private IP address range that does not overlap with the on-premises location that we connect from, or the VNet that we want to connect to. If we configure multiple protocols and SSTP is one of the protocols, then the configured address pool is split between the configured protocols equally.</p><p>i) Once the virtual network gateway has been created, navigate to the <strong>Settings</strong> section of the virtual network gateway page. In <strong>Settings</strong>, select <strong>Point-to-site configuration</strong>. Select <strong>Configure now</strong> to open the configuration page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*M7m5PyqsLfoarU1oFhUVDA.png" /></figure><p>ii) On the <strong>Point-to-site configuration</strong> page, in the <strong>Address pool</strong> box, add the private IP address range that we want to use. VPN clients dynamically receive an IP address from the range that we specify. The minimum subnet mask is 29 bit for active/passive and 28 bit for active/active configuration.</p><p>iii) Continue to the next section to configure authentication and tunnel types.</p><p>8. Specify <strong>Tunnel </strong>type and <strong>Authentication </strong>type.</p><p>In this section, we specify the tunnel type and the authentication type. If we don’t see tunnel type or authentication type on the Point-to-site configuration page, our gateway is using the Basic SKU. The Basic SKU does not support IKEv2 or RADIUS authentication. If we want to use these settings, we need to delete and recreate the gateway using a different gateway SKU.</p><blockquote><strong>a) Tunnel type.</strong></blockquote><p>On the <strong>Point-to-site configuration</strong> page, select the <strong>Tunnel type</strong>. When selecting the tunnel type, note the following:</p><p>i) The strongSwan client on Android and Linux and the native IKEv2 VPN client on iOS and macOS will use only the IKEv2 tunnel type to connect.</p><p>ii) Windows clients will try IKEv2 first and if that doesn’t connect, they fall back to SSTP.</p><p>iii) We can use the OpenVPN client to connect to the OpenVPN tunnel type.</p><blockquote><strong>b) Authentication type.</strong></blockquote><p>For <strong>Authentication type</strong>, select <strong>Azure certificate</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*nke5iNyxIutD7mgM62T6mQ.png" /></figure><p>9. Upload <strong>root certificate </strong>public key information</p><p>In this section, we upload public root certificate data to Azure. Once the public certificate data is uploaded, Azure can use it to authenticate clients that have installed a client certificate generated from the trusted root certificate.</p><p>i) Navigate to our <strong>Virtual network gateway -&gt; Point-to-site configuration</strong> page in the <strong>Root certificate</strong> section. This section is only visible if we have selected <strong>Azure certificate</strong> for the authentication type.</p><p>ii) Open the certificate with a text editor, such as Notepad. When copying the certificate data, make sure that we copy the text as one continuous line without carriage returns or line feeds. We may need to modify our view in the text editor to ‘Show Symbol/Show all characters’ to see the carriage returns and line feeds. Copy only the following section as one continuous line:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*fLotprKFRucN77MD6jwoqw.png" /></figure><p>iii) In the <strong>Root certificate</strong> section, we can add up to 20 trusted root certificates.</p><p>iv) Paste the certificate data into the <strong>Public certificate data</strong> field.</p><p>v) <strong>Name</strong> the certificate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*xZsm5Wc99dgdQEnZn14cEw.png" /></figure><p>vi) Select <strong>Save</strong> at the top of the page to save all of the configuration settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*rrgqYZm5jiYlj_3wCi8sJQ.png" /></figure><p>10. Generate and install <strong>VPN client profile</strong> configuration files for certificate authentication.</p><p>When we connect to an Azure VNet using Point-to-Site and certificate authentication, we use the VPN client that is natively installed on the operating system from which we’re connecting. All of the necessary configuration settings for the VPN clients are contained in a VPN client configuration zip file. The settings in the zip file help you easily configure the VPN clients for Windows, Mac IKEv2 VPN, or Linux.</p><p>The VPN client configuration files that we generate are specific to the P2S VPN gateway configuration for the virtual network. If there are any changes to the Point-to-Site VPN configuration after we generate the files, such as changes to the VPN protocol type or authentication type, we need to generate new VPN client configuration files and apply the new configuration to all of the VPN clients that we want to connect.</p><blockquote><strong>a) Generate files using Azure Portal.</strong></blockquote><p>i) In the Azure portal, navigate to the virtual network gateway for the virtual network that we want to connect to.</p><p>ii) On the virtual network gateway page, select <strong>Point-to-site configuration</strong> to open the Point-to-site configuration page.</p><p>iii) At the top of the Point-to-site configuration page, select <strong>Download VPN client</strong>. This doesn’t download VPN client software, it generates the configuration package used to configure VPN clients. It takes a few minutes for the client configuration package to generate. During this time, we may not see any indications until the packet has generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*Y-gfsBc8O5YsYFLHl4528w.png" /></figure><p>iv) Once the configuration package has been generated, our browser indicates that a client configuration zip file is available. It’s named the same name as our gateway. Unzip the file to view the folders.</p><blockquote><strong>b) Install the configuration files.</strong></blockquote><p>i) Select the VPN client configuration files that correspond to the architecture of the Windows computer. For a 64-bit processor architecture, choose the ‘VpnClientSetupAmd64’ installer package. For a 32-bit processor architecture, choose the ‘VpnClientSetupX86’ installer package.</p><p>ii) Double-click the package to install it. If we see a SmartScreen popup, click <strong>More info</strong>, then <strong>Run anyway</strong>.</p><p>11. Test the connection</p><p>i) To connect to our VNet, on the client computer, navigate to VPN settings and locate the VPN connection that we created. It’s named the same name as our virtual network. Select <strong>Connect</strong>. A pop-up message may appear that refers to using the certificate. Select <strong>Continue</strong> to use elevated privileges.</p><p>ii) On the <strong>Connection</strong> status page, select <strong>Connect</strong> to start the connection. If we see a <strong>Select Certificate</strong> screen, verify that the client certificate showing is the one that we want to use to connect. If it is not, use the drop-down arrow to select the correct certificate, and then select <strong>OK</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*IQynAqvq-A7ahpidd4AX2Q.png" /></figure><p>iii) Your connection is established.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*ytoPeHdSVriLCwAiJZG-XA.png" /></figure><p><strong>This is part two of a four-part series that can be viewed below:</strong></p><p><a href="https://medium.com/version-1/vnet-integratedpostgresql-integration-with-power-bi-app-12950039e687">Part 1 — Creating Virtual Network and PostgreSQL</a><br><a href="https://medium.com/version-1/installing-odbc-driver-for-remote-connection-to-postgresql-db-9b8d496e50e4">Part 3 — Installing ODBC driver for remote connection to PostgreSQL DB</a><br><a href="https://medium.com/version-1/configuring-of-data-gateway-in-power-bi-f7f95882f19">Part 4 — Configuring a Data Gateway in Power BI</a></p><p><em>If you found this interesting or have any feedback, please let me know in the comments section.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oCwj8UZknfuwZrdXbIV9Cw.jpeg" /></figure><p><strong>About the Author:<br></strong>Raghavendra BN is a DevOps Engineer, currently working in Version 1’s Foundation’s team. Follow Version 1 and Raghavendra BN for more blogs around Microsoft Azure and Azure DevOps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a5b61839e54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/version-1/creating-and-configuring-virtual-network-gateway-point-to-site-using-azure-certification-7a5b61839e54">Creating and Configuring Virtual Network Gateway (Point-to-Site) Using Azure certification…</a> was originally published in <a href="https://medium.com/version-1">Version 1</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vnet IntegratedPostgreSQL Integration with Power BI App]]></title>
            <link>https://medium.com/version-1/vnet-integratedpostgresql-integration-with-power-bi-app-12950039e687?source=rss-4c530cedd5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/12950039e687</guid>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[virtual-networks]]></category>
            <category><![CDATA[vnet]]></category>
            <category><![CDATA[power-bi]]></category>
            <dc:creator><![CDATA[Raghavendra BN]]></dc:creator>
            <pubDate>Thu, 26 May 2022 09:23:04 GMT</pubDate>
            <atom:updated>2022-05-26T09:42:02.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wRk_kOSWJoWCIpyp" /></figure><p><strong>Case Scenario</strong></p><p>Here is the case scenario, we have a database (PostgreSQL) running on Azure that has VNET integration enabled and we need to access the same database from the Power BI.</p><p><strong>We have summarised the process into four different sections outlined below:</strong></p><p>1.<a href="https://medium.com/version-1/vnet-integratedpostgresql-integration-with-power-bi-app-12950039e687"> Part 1 — Creating Virtual Network and PostgreSQL</a><br>2. <a href="https://medium.com/version-1/creating-and-configuring-virtual-network-gateway-point-to-site-using-azure-certification-7a5b61839e54">Part 2 — Creating and Configuring Virtual Network Gateway (Point-to-Site)</a><br>3. <a href="https://medium.com/version-1/installing-odbc-driver-for-remote-connection-to-postgresql-db-9b8d496e50e4">Part 3 — Installing ODBC driver for remote connection to PostgreSQL DB</a><br>4. <a href="https://medium.com/version-1/configuring-of-data-gateway-in-power-bi-f7f95882f19">Part 4 — Configuring a Data Gateway in Power BI</a></p><h3><strong>Creating Virtual Network and PostgreSQL Flexible Server</strong></h3><p>Azure Database for PostgreSQL Flexible Server supports two types of mutually exclusive network connectivity methods.</p><ul><li>Public access (allowed IP addresses)</li><li>Private access (VNET Integration)</li></ul><p>In this blog, we will focus on the creation of a PostgreSQL Flexible Server with <strong>Private access (VNet integration)</strong> using the Azure portal. With Private access (VNet Integration), we can deploy our flexible server into our own <a href="https://docs.microsoft.com/en-gb/azure/virtual-network/virtual-networks-overview"><strong>Azure Virtual Network</strong></a>. Azure Virtual Networks provide private and secure network communication. With private access, connections to the PostgreSQL server are restricted to our virtual network.</p><p><strong>NOTE:</strong> We can deploy our flexible server into a virtual network and subnet during server creation. After the flexible server is deployed, we cannot move it into another virtual network, subnet or <em>Public access (allowed IP addresses)</em>.</p><ul><li><strong>Create a Virtual Network</strong></li></ul><p>1. Sign in to the Azure portal (<a href="https://portal.azure.com/">https://portal.azure.com/)</a>.</p><p>2. Select <strong>Create a resource</strong> in the upper left-hand corner of the portal.</p><p>3. In the search box, enter <strong>Virtual Network</strong>. Select <strong>Virtual Network</strong> in the search results.</p><p>4. On the <strong>Virtual Network</strong> page, select <strong>Create</strong>.</p><p>5. In <strong>Create virtual network</strong>, enter or select required information in the <strong>Basics</strong> tab:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/1*_oYNyOxpOqOdwfD_uHDBDw.png" /></figure><p>6. Select the <strong>IP Addresses</strong> tab or select the <strong>Next: IP Addresses</strong> button at the bottom of the page.</p><p>7. In <strong>IPv4 address space</strong>, select the existing address space and change it to <strong>10.1.0.0/16</strong>.</p><p>8. Select <strong>+ Add subnet</strong>, then enter an appropriate <strong>Subnet </strong>name (Ex:<strong>MySubnet)</strong> for <strong>Subnet name</strong> and <strong>10.1.0.0/24</strong> for <strong>Subnet address range</strong>.</p><p>9. Select <strong>Save</strong>.</p><p>10. Select the <strong>Security</strong> tab or select the <strong>Next: Security</strong> button at the bottom of the page.</p><p><strong>*BastionHost</strong>: Disable</p><p><strong>*DDoS Protection Standard</strong>: Disable</p><p><strong>*Firewall</strong>: Disable</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*5VpQ1wICa3-nbHKRrux19A.png" /></figure><p>11. Select the <strong>Tags</strong> tab or select the <strong>Next: Tags</strong> button at the bottom of the page.</p><p>12. Select the <strong>Review + create</strong> tab or select the <strong>Review + create</strong> button.</p><p>13. Select <strong>Create</strong>.</p><ul><li><strong>Create Azure Database for PostgreSQL Flexible Server in an already existing virtual network</strong></li></ul><p><strong>Prerequisites:</strong></p><p>*The virtual network and subnet should be in the same region and subscription as our flexible server.</p><p>*<a href="https://docs.microsoft.com/en-gb/azure/virtual-network/manage-subnet-delegation#delegate-a-subnet-to-an-azure-service">Delegate a subnet</a> to <strong>Microsoft.DBforPostgreSQL/FlexibleServers</strong>. This delegation means that only Azure Database for PostgreSQL Flexible Servers can use that subnet. No other Azure resource types can be in the delegated subnet.</p><p>*Add Microsoft.Storage to the service endpoint for the subnet delegated to Flexible servers.</p><ol><li>Select <strong>Create a resource</strong> (+) in the upper-left corner of the azure portal.</li><li>Select <strong>Databases</strong> &gt; <strong>Azure Database for PostgreSQL</strong>. We can also enter <strong>PostgreSQL</strong> in the search box to find the service.</li><li>Select <strong>Flexible server</strong> as the deployment option.</li><li>Fill out the <strong>Basics</strong> form.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Z-XxyRlnhulybBazMHjiYg.png" /></figure><p>5. Go to the <strong>Networking</strong> tab to configure connection options to our server.</p><p>6<strong>.</strong> In the <strong>Connectivity method</strong>, select <strong>Private access (VNET Integration)</strong>. Go to <strong>Virtual Network </strong>and click <strong>Manage selected virtual network.</strong></p><p>7. Select <strong>+ Add subnet</strong>, then enter <strong>psql-subnet</strong> for <strong>Subnet name</strong> and <strong>10.1.1.0/24</strong> for <strong>Subnet address range</strong>. Click <strong>Save.</strong></p><p>8. Under <strong>Private DNS Integration</strong>, by default, a new private DNS zone will be created using the server name. Optionally, we can choose the <em>subscription</em> and the <em>Private DNS zone</em> from the drop-down list.</p><p>9. Select <strong>Review + create</strong> to review our flexible server configuration.</p><p>10. Select <strong>Create</strong> to provision the server. Provisioning can take a few minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*cxhtpUZxuiuf3nvzTx9oVg.png" /></figure><p><em>If you found this interesting or have any feedback, please let me know in the comments section.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EppHHpEiIbVFJ8oHL8X00w.jpeg" /></figure><p><strong>About the Author:<br></strong><em>Raghavendra BN is a DevOps Engineer, currently working in Version 1’s Foundation’s team. Follow Version 1 and Raghavendra BN for more blogs around Microsoft Azure and Azure DevOps.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12950039e687" width="1" height="1" alt=""><hr><p><a href="https://medium.com/version-1/vnet-integratedpostgresql-integration-with-power-bi-app-12950039e687">Vnet IntegratedPostgreSQL Integration with Power BI App</a> was originally published in <a href="https://medium.com/version-1">Version 1</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>