<?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 Sourabh Yadav on Medium]]></title>
        <description><![CDATA[Stories by Sourabh Yadav on Medium]]></description>
        <link>https://medium.com/@sourabh_yadav?source=rss-2a031aa72afd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Z7OwnWDo8w_AlpmXiAnBZQ.png</url>
            <title>Stories by Sourabh Yadav on Medium</title>
            <link>https://medium.com/@sourabh_yadav?source=rss-2a031aa72afd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:10:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sourabh_yadav/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[Building Azure Deployment Pipeline — Business Central]]></title>
            <link>https://medium.com/@sourabh_yadav/building-azure-deployment-pipeline-business-central-d57ac0ec5771?source=rss-2a031aa72afd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d57ac0ec5771</guid>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[d365-business-central]]></category>
            <dc:creator><![CDATA[Sourabh Yadav]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 17:42:47 GMT</pubDate>
            <atom:updated>2026-10-24T17:42:47.878Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome back to the series.</p><p>Today we will be looking at how to configure a deployment pipeline for Business Central Deployment. Here are the previous part of this series go through them this will provide you with better understanding of Azure Devops.</p><p><a href="https://medium.com/@sourabh_yadav/what-is-azure-devops-why-bc-developers-should-care-a8221cdc830c">What is Azure Devops &amp; Why BC Developers Should Care?</a></p><p><a href="https://medium.com/@sourabh_yadav/code-repository-setup-for-business-central-development-using-azure-devops-213c6077d324">Code Repository Setup for Business Central Development using Azure DeVops.</a></p><p>…..</p><p>Let’s Begin</p><h3>Overview of Deployment Pipeline</h3><p>So this is how our Deployment will work.</p><ol><li>A developer creates a pull request to merge in the production branch.</li><li>A reviewer reviews the pull request and merge it.</li><li>Deployment Pipeline gets triggered.</li><li>Build the .app file using AL compiler and app.json</li><li>Automation APIs install .app file in the Business Central Environment.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGoIdZmB-j2mNbxwtlP5vw.png" /></figure><h3><strong>Azure App Registration</strong></h3><p>First we would register an azure application so that we can use Business Central Automation APIs. (<a href="https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/itpro-introduction-to-automation-apis">Check them out</a>)</p><p>Login to <a href="https://portal.azure.com/">Azure portal</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4K2gf73k0uuqzxvivP6d2g.png" /><figcaption>Azure portal</figcaption></figure><p>Look for App Registrations inside your Azure portal.</p><p>Click on New registration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vwXlu9XPHolze36xffDmUw.png" /><figcaption>New App Registration</figcaption></figure><p>Follow these steps to create a App in Azure</p><p>a. Enter the name for your app</p><p>b. Select your tenant name</p><p>c. Enter the Redirect URI — <a href="https://businesscentral.dynamics.com/OAuthLanding.htm">https://businesscentral.dynamics.com/OAuthLanding.htm</a></p><p>d. Click on Register</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yWAUM7NkhIKc-LiNsOKV5g.png" /></figure><p>Once your app is registered you will be redirected to the homepage of the Azure App.</p><p>In the left pane look for <strong>Manage</strong>, under <strong>Manage </strong>click on <strong>Certificates &amp; Secrets. </strong>Click on <strong>+New Secret.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YxdTbhsHdGyeYtyGOtKxqw.png" /></figure><p>This will open a <strong>Client Secret</strong> dialog to create a new <strong>client secret</strong>. Enter the Description of your <strong>client secret</strong> and the timeframe after which your client secret will expire.</p><p>Once done click on <strong>Add</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/771/1*gAPoO77Nqyhh1ByLH6f2eQ.png" /></figure><p>Upon creation you will get your secret value and secret Id. Note them down and keep them secure.</p><p><strong>Note</strong>: secret value will be masked upon page refresh so note it down immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jW56lxINbjFNA5XsuFs6ig.png" /></figure><p>Now lets assign some permission to our App to access our Business Central.</p><p>In the left pane under Manage look for API permissions and click on it. Click <strong>+Add a permission</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fLOxBZ_H4RYWnNpZzYGyuw.png" /></figure><p>This will open up <strong>Request API permissions</strong> dialog. Under <strong>Microsoft APIs </strong>look for <strong>Dynamics 365 Business Central </strong>and select it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Imz5EaQVpJwQuApfEZnmqQ.png" /></figure><p>Select <strong>Application permissions</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*ffS3mkobI9Vy6evbWSFyiw.png" /></figure><p>Select the following API permissions and click on <strong>Add permissions</strong></p><p>i. app_access</p><p>ii. API.ReadWrite.All</p><p>iii. Automation.ReadWrite.All</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PAWTPxV_-wRNk4u7ISy6_w.png" /></figure><p>Now we need to provide admin consent for the use of the following permissions. So make sure you are logged in with Business Central Administrator account.</p><p>Click on grant Consent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PXWvJfIiltfaXIn1bgrKCw.png" /></figure><p>Login to Business Central environment and search for <strong><em>Microsoft Entra Applications</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awh7eWGkK6K-W_TulM5_lg.png" /></figure><p>Click +New and create a new Entra Application. Provide the following permissions to it and click on Grant Consent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*keCvRjbRzDAoTQZYO8tFzA.png" /></figure><h3>Configuring Deployment Pipeline</h3><p><strong>Install Azure CLI</strong></p><p>First we need to install Azure CLI in order to connect Azure Devops Artifacts directly through our desktop and upload the AL Compiler as an artifact into our Azure Devops as an artifact. This will help in compiling our code in Devops. <br>You can download and install Azure CLI from the below URL. <br><a href="https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest&amp;pivots=msi">https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest&amp;pivots=msi</a></p><h4>Uploading AL compiler</h4><p>Now we need to upload AL compiler as an artifact into Azure Devops. AL compiler will be used to build the AL package during the deployment which will further be uploaded into Business Central Environment using Automation APIs.</p><ol><li>Open Azure Devops, open the respective project and then select the Artifacts and click + Create Feed.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-HBOd-HCCQrfo_ulQ00xww.png" /></figure><p>2. A dialog will open inside dialog provide the name of your feed, and the access level for it (I am keeping the default access level). Click on Create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*lu1BzAE-86QTFM4Ssh_BKw.png" /></figure><p>3. Click on Create Feed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EMXxoOrShMKk_Gyf8NBOsg.png" /></figure><p>4. Select <em>Universal Packages.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dcQpcj-oo8MYHNzXseThfA.png" /></figure><p>5. You will get the code to publish packages inside your artifacts. Copy the Publish packages code</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AYoyNgasu_87SOAj0g4fOg.png" /></figure><p>6. Open your system and search and command prompt there and open it.<br> 6.1 Paste the following command in the command prompt and hit enter.</p><pre>az login --allow-no-subscriptions</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FogXfvAlAi4ctIkGR78Qbw.png" /></figure><p>6.2 You will be asked to login make sure to login with your Work or school account with which you have logged into devops.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*we7XIwYu1YYWWcdDDzTTYg.png" /></figure><p>6.3 Upon login it might ask you to select which apps you want to login with this account select <strong><em>No, this app only.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*Wu4p1xyY_cdcXFIFD0BwrA.png" /></figure><p>6.4 You will get a list of azure subscription available against this account. Select the one you have used for Devops. For selection enter the No of that subscription like for my case I have just 1 subscription and its No is also 1 so I will enter 1 as command and will press enter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ueOrPwiBvCy-IDYQvmjQsg.png" /></figure><p>6.5 copy the <strong><em>Publish Package </em></strong>command from the above and paste in the command prompt. We need to update the name and path parameter of this command. name would be the name of the package that will uploaded into your artifact and path is folder path of the al-compiler inside your system that you want to upload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a9hBkcYYwi1dNzWq2NPUqg.png" /></figure><p>You can find the your al-compiler in the following location inside your system.</p><pre>C:\Users\&lt;your-host-name&gt;\.vscode\extensions\ms-dynamics-smb.al-17.0.2273547\bin\win32</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t9GUS4Oz28UwlFpAONwrig.png" /></figure><p>Copy the path and replace in your command like below and hit enter.</p><p><strong>Note: Make sure any of your VS Code instances are not running in your system while you are doing this activity as it will cause error in uploading your al-compiler.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tS2fl_xK15Rz83YjqF_Cqg.png" /></figure><p>It will start uploading of your al-compiler inside into your artifact as a package.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fae6fSgok-yZduMq-sibaA.png" /></figure><p>Upon successful completion you will see your package inside your feed in Devops Artifact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vcmXdgd-VCQgu_7NnSagVg.png" /></figure><h4>Configuring CI/CD Pipeline</h4><p>Open the VS Code add the following yaml file in your AL extension name it as per your convenience.</p><pre>trigger:<br>  branches:<br>    include:<br>      - main<br> <br># ============================================================<br># VARIABLES<br># ============================================================<br> <br>variables:<br> <br> <br># Main / Production<br>- ${{ if eq(variables[&#39;Build.SourceBranchName&#39;], &#39;main&#39;) }}:<br>  - group: Pipeline-CREDS<br> <br> <br># ============================================================<br># PARAMETERS<br># ============================================================<br> <br>parameters:<br> <br>- name: mainVersion<br>  type: string<br>  default: &#39;1.0.0.0&#39;<br> <br>- name: Schema<br>  type: string<br>  default: &#39;Add&#39;<br> <br>- name: agentPool<br>  type: string<br>  default: &#39;Azure Pipelines&#39;<br> <br> <br># ============================================================<br># STAGES<br># ============================================================<br> <br>stages:<br> <br># ============================================================<br># BUILD<br># ============================================================<br> <br>- stage: Build<br> <br>  displayName: &#39;Build Business Central Extension&#39;<br> <br>  jobs:<br> <br>  - job: Compile<br> <br>    displayName: &#39;Compile AL Extension&#39;<br> <br>    pool:<br>      name: ${{ parameters.agentPool }}<br>      vmImage: &#39;windows-latest&#39;<br> <br>    steps:<br> <br>    # --------------------------------------------------------<br>    # Checkout source code<br>    # --------------------------------------------------------<br> <br>    - checkout: self<br> <br> <br>    # --------------------------------------------------------<br>    # Download ALC Compiler<br>    # --------------------------------------------------------<br> <br>    - task: DownloadPackage@1<br>      displayName: &#39;Download AL Compiler&#39;<br> <br>      inputs:<br>        packageType: &#39;upack&#39;<br>        feed: &#39;&lt;your-feed-id&gt;&#39;<br>        view: &#39;@local&#39;<br>        definition: &#39;&lt;your-package-name&gt;&#39;<br>        version: &#39;&lt;your-package-version&gt;&#39;<br>        downloadPath: &#39;$(Pipeline.Workspace)/&lt;your-feed-name&gt;&#39;<br> <br> <br>    # --------------------------------------------------------<br>    # Set Version<br>    # --------------------------------------------------------<br> <br>    - powershell: |<br> <br>        $appJsonPath = &quot;$(Build.SourcesDirectory)\app.json&quot;<br> <br>        $json = Get-Content -Raw $appJsonPath | ConvertFrom-Json<br> <br>        $branch = &quot;$(Build.SourceBranchName)&quot;<br> <br>        if ($branch -eq &quot;main&quot;) {<br>            $version = &quot;${{ parameters.mainVersion }}&quot;<br>        }<br>        else {<br>            throw &quot;Unsupported branch: $branch&quot;<br>        }<br> <br>        Write-Host &quot;======================================&quot;<br>        Write-Host &quot;Branch  : $branch&quot;<br>        Write-Host &quot;Version : $version&quot;<br>        Write-Host &quot;======================================&quot;<br> <br>        $json.version = $version<br> <br>        $json |<br>          ConvertTo-Json -Depth 10 |<br>          Set-Content $appJsonPath<br> <br>        Write-Host &quot;##vso[task.setvariable variable=publisher]$($json.publisher)&quot;<br> <br>        Write-Host &quot;##vso[task.setvariable variable=name]$($json.name)&quot;<br> <br>        Write-Host &quot;##vso[task.setvariable variable=version]$version&quot;<br> <br>      displayName: &#39;Set App Version&#39;<br> <br> <br>    # --------------------------------------------------------<br>    # Compile AL Project<br>    # --------------------------------------------------------<br> <br>    - powershell: |<br> <br>        $alc = Get-ChildItem `<br>          &quot;$(Pipeline.Workspace)\&lt;your-feed-name&gt;&quot; `<br>          -Recurse `<br>          -Filter alc.exe |<br>          Select-Object -First 1<br> <br>        if (-not $alc) {<br>            throw &quot;ALC compiler not found&quot;<br>        }<br> <br>        Write-Host &quot;AL Compiler found at:&quot;<br>        Write-Host $alc.FullName<br> <br> <br>        $outDir = &quot;$(Pipeline.Workspace)\App&quot;<br> <br>        New-Item `<br>          -ItemType Directory `<br>          -Force `<br>          -Path $outDir |<br>          Out-Null<br> <br> <br>        $outFile = &quot;$(publisher)_$(name)_$(version).app&quot;<br> <br>        $outPath = Join-Path $outDir $outFile<br> <br> <br>        Write-Host &quot;Output file:&quot;<br>        Write-Host $outPath<br> <br> <br>        &amp; $alc.FullName `<br>          /project:&quot;$(Build.SourcesDirectory)&quot; `<br>          /out:$outPath `<br>          /packagecachepath:&quot;$(Build.SourcesDirectory)\.alpackages&quot;<br> <br> <br>        if ($LASTEXITCODE -ne 0) {<br>            throw &quot;AL compilation failed&quot;<br>        }<br> <br> <br>        Set-Content `<br>          (Join-Path $outDir &quot;appFileName.txt&quot;) `<br>          $outFile<br> <br>      displayName: &#39;Compile AL Extension&#39;<br> <br> <br>    # --------------------------------------------------------<br>    # Publish APP artifact<br>    # --------------------------------------------------------<br> <br>    - publish: $(Pipeline.Workspace)/App<br>      artifact: App<br> <br>      displayName: &#39;Publish APP Artifact&#39;<br> <br> <br># =========================<br># DEPLOY<br># =========================<br>- stage: Deploy<br>  dependsOn: Build<br><br>  jobs:<br>  - job: Deploy<br>    pool:<br>      name: ${{ parameters.agentPool }}<br><br>    steps:<br>    - download: current<br>      artifact: App<br><br>    - powershell: |<br>        $name = Get-Content &quot;$(Pipeline.Workspace)\App\appFileName.txt&quot;<br>        Write-Host &quot;##vso[task.setvariable variable=appFileName]$name&quot;<br>      displayName: &quot;Read App&quot;<br><br>    - powershell: |<br>        $body = @{<br>          client_id     = &quot;$(client_id)&quot;<br>          client_secret = &quot;$(client_secret)&quot;<br>          scope         = &quot;$(scope)&quot;<br>          grant_type    = &quot;client_credentials&quot;<br>        }<br><br>        $response = Invoke-RestMethod `<br>          -Uri &quot;https://login.microsoftonline.com/$(tenant_id)/oauth2/v2.0/token&quot; `<br>          -Method Post `<br>          -Body $body<br><br>        Write-Host &quot;##vso[task.setvariable variable=token]$($response.access_token)&quot;<br>      displayName: &quot;Get Token&quot;<br><br>    - powershell: |<br>        $url = &quot;https://api.businesscentral.dynamics.com/v2.0/$(tenant_id)/$(env_name)/api/microsoft/automation/v2.0/companies($(company_id))/extensionUpload&quot;<br><br>        $response = Invoke-RestMethod -Uri $url -Method Post -Headers @{<br>          Authorization = &quot;Bearer $(token)&quot;<br>          &quot;Content-Type&quot;=&quot;application/json&quot;<br>        } -Body (@{<br>          schedule = &quot;Current version&quot;<br>          schemaSyncMode = &quot;${{ parameters.Schema }}&quot;<br>        } | ConvertTo-Json)<br><br>        Write-Host &quot;##vso[task.setvariable variable=extension_id]$($response.systemId)&quot;<br>      displayName: &quot;Create Upload&quot;<br><br>    - powershell: |<br>        Invoke-RestMethod `<br>          -Uri &quot;https://api.businesscentral.dynamics.com/v2.0/$(tenant_id)/$(env_name)/api/microsoft/automation/v2.0/companies($(company_id))/extensionUpload($(extension_id))/extensionContent&quot; `<br>          -Method Patch `<br>          -Headers @{<br>            Authorization = &quot;Bearer $(token)&quot;<br>            &quot;If-Match&quot;=&quot;*&quot;<br>          } `<br>          -InFile &quot;$(Pipeline.Workspace)\App\$(appFileName)&quot;<br>      displayName: &quot;Upload&quot;<br><br>    - powershell: |<br>        Invoke-RestMethod `<br>          -Uri &quot;https://api.businesscentral.dynamics.com/v2.0/$(tenant_id)/$(env_name)/api/microsoft/automation/v2.0/companies($(company_id))/extensionUpload($(extension_id))/Microsoft.NAV.upload&quot; `<br>          -Method Post `<br>          -Headers @{<br>            Authorization = &quot;Bearer $(token)&quot;<br>          }<br>      displayName: &quot;Install&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*llqjT4lvhgkwC5z34LC0lQ.png" /></figure><p>You need to modify few details in this code as per your devops setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*uJD4ShU7Ahtgw6N2UzCisw.png" /></figure><p>For getting project id you can get it from your feed. Follow below steps.</p><p>Click on the package name and copy the project id.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hAAXNKmOE12YVsEyZ2R-EA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*3GwrqBRoS7-_o0CBO2JVFw.png" /></figure><p>Now we need to get the Feed Id.</p><p>For getting feed id you need to follow given steps in the command prompt.</p><p>Open command prompt and paste the following command. Replace {YourOrganization} — with the name of your Devops organization and {YourFeedName} with your feed name. Click Enter.</p><pre>az devops invoke --http-method GET --area packaging --resource feeds --organization &quot;https://dev.azure.com/{YourOrganization}&quot; --query &quot;value[?name==&#39;YourFeedName&#39;].id&quot; --output tsv</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V3FXP-3hfgvqU34eR9n84g.png" /></figure><p>In response you will get feed id in response note it down.</p><p>Now in your yaml file update the feed details like below —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*x2XsM_HkqICmR_yM51PpiQ.png" /></figure><p>In feed it should be &lt;project-id&gt;/&lt;feed-id&gt;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*Fl5Gsjmx4-uP1l2amoyIiA.png" /></figure><p>Now sync your changes to Azure Devops.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FLsyxSJcsgT6vTTxRXNvCg.png" /></figure><p>Few things you need to note is that</p><ol><li>I am using main branch for this pipeline so in my yaml file you will find code based on that. You can add other branches as per your need.</li><li>Once you configure the pipeline it will be triggered for every commit you make in the main branch. So Ideally, you should have a separate branch for your deployment environment wise and nobody should have direct commit access to it. One should create Pull request in that branch which should be reviewed by someone and once it is merged then your deployment pipeline will trigger.</li><li>For every new deployment you need to update following things in your yaml file.<br>Version — should be your extension version like how you update in your app.json<br>Schema — It is similar to schemaUpdateMode in your launch.json. It can have 2 values.<br>Add =&gt; schemaUpdateMode “Synchronize”<br>Force =&gt; schemaUpdateMode “ForceSync”</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*c2mB_PAzmU68k7XxOqmwbQ.png" /></figure><p>Now open your Azure Devops. In the left pane select Pipelines -&gt; Create Pipeline</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g6W-pheifqwi8337jZxFWg.png" /></figure><p>Select Azure Repos Git</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-994Bh4064UEWg2SH7v5Q.png" /></figure><p>Select your extension name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIc8FOCyCqzhucAgJsq5Ig.png" /></figure><p>Select “Existing Azure Pipelines YAML file”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jv6C5cGxEd3TWHF-p0-wTw.png" /></figure><p>Select the branch to initialize the pipeline I am selecting main branch and then select the path to your yaml file. Click on Continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*L55MZDQM_dgTqKOb5lpImA.png" /></figure><p>Click on dropdown beside Run and click Save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0esWPHMoJ5FQvy_qIfqTgw.png" /></figure><p>Now we need to configure Pipeline variables which will be used by our Yaml file to target the environment for deployment of your extension.</p><p>Under Pipelines select Library. (<em>Make sure the names of variable group and variables are similar to what I am defining as they are used in the yaml file with the same name</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FDoD9xxn8XxXYBjyYZYdpQ.png" /></figure><p>Click on + Variable group, add the below defined variables and click Save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*br42AgOrTi2FI6MKK9-KYg.png" /></figure><p>Fill the value for the variables shown below from azure app registration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G6NqvJ3F2v-d4Q4QeDvGmw.png" /></figure><p>Now click on Pipeline Permissions and select your pipeline to grant permission to use variable group by your pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PwAk3eCm82QjJ2UV4vvN1w.png" /></figure><p>Select the extension and close the dialog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*weTiQb4qI7RvWbmlWXmIQQ.png" /></figure><p>Now we need to validate the configuration of our pipeline. Open your pipeline and click on Edit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XqWGIuhlJIvK6bj69oV-Uw.png" /></figure><p>Click on 3 dots and select Validate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eviuBIuhuOTvuf0wb3dUxw.png" /></figure><p>You will get a message that pipeline is valid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*TutQqfgivgJ_VoG5oSN6-Q.png" /></figure><p>Click on Run to run the pipeline manually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E38lHgBLsoNFg2Aevva_KQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*rJafV9qonc7lctmLzDCL5Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*5YgotiC70beVgua0mHnyYA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g14xtNiJ4ZJfw6mu1lQE2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8GZxIbSQb5n6IQqpP3DjBQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*mh0i8pgohpuyFKIM0P2hHQ.png" /></figure><p>Upon successful completion of deployment. Open Business Central and Check Installation Status you will find that the extensions is getting installed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nevre-ebQ8gmthZDyHy2RQ.png" /></figure><p>As of now we have run manual deployment pipeline but this will get auto triggered for every commit in the given branch.</p><p>Hope you like it. Cheers!!❤️</p><ul><li><a href="https://medium.com/@sourabh_yadav/what-is-azure-devops-why-bc-developers-should-care-a8221cdc830c">What is Azure DevOps &amp; Why BC Developers Should Care?</a></li><li><a href="https://medium.com/@sourabh_yadav/code-repository-setup-for-business-central-development-using-azure-devops-213c6077d324">Code Repository Setup for Business Central Development using Azure DevOps</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d57ac0ec5771" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code Repository Setup for Business Central Development using Azure DevOps]]></title>
            <link>https://medium.com/@sourabh_yadav/code-repository-setup-for-business-central-development-using-azure-devops-213c6077d324?source=rss-2a031aa72afd------2</link>
            <guid isPermaLink="false">https://medium.com/p/213c6077d324</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Sourabh Yadav]]></dc:creator>
            <pubDate>Sun, 21 Jun 2026 17:00:24 GMT</pubDate>
            <atom:updated>2026-06-21T17:00:24.910Z</atom:updated>
            <content:encoded><![CDATA[<p>(Part 2 of Azure DevOps + Business Central CI/CD Series)</p><p>Part 1 - <a href="https://medium.com/@sourabh_yadav/what-is-azure-devops-why-bc-developers-should-care-a8221cdc830c">What is Azure DevOps &amp; Why BC Developers Should Care?</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LkzxOZ-HNC3uzZQS8QbQqQ.png" /></figure><h3>Welcome Back to the Series</h3><p>How have you been!! In the previous part of this series, we explored why Azure DevOps is becoming an essential part of modern Business Central development and how it helps bridge the gap between traditional ERP practices and modern engineering workflows.</p><p>Now it’s time to move from concepts to implementation.</p><p>Because before we can build CI/CD pipelines, automate deployments, or implement enterprise-grade DevOps practices, we first need to establish one critical foundation:</p><blockquote><strong><em>A properly structured source control setup for Business Central development.</em></strong></blockquote><p>And this is where many teams struggle.</p><p>From overwritten AL changes and inconsistent environments to unmanaged branches and deployment confusion, poor repository practices often become the root cause of larger development and release issues later in the project lifecycle.</p><p>In this blog, we’ll take a practical, Business Central–focused approach to setting up and working with repositories using Azure DevOps and Git. We’ll start by creating an Azure DevOps organization and project, understand how repositories are structured, and then connect our local AL projects through Visual Studio Code. Along the way, we’ll also explore essential Git concepts such as commits, pull, push, fetch, branching strategies, pull requests, and merge workflows — all from the perspective of real-world Business Central development scenarios.</p><p>Whether you are completely new to Git or already working with repositories in your projects, this guide is designed to help you understand not just <em>how</em> these workflows operate, but <em>why</em> they are important in modern collaborative development.</p><p>By the end of this blog, you will have a strong foundation for managing Business Central source code professionally and will be ready to move into the next stage of the series — building automated CI pipelines for AL projects.</p><h3>Prerequisites for Azure DevOps Access</h3><p>Before setting up repositories or working with source control, the first step is ensuring that you have the correct access to Azure DevOps.</p><p>For Azure Pricing Check this — <a href="https://azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/">Pricing for Azure Devops</a>.</p><p><strong>To access Azure DevOps, a user primarily needs:</strong></p><ul><li>A Microsoft account or organizational Microsoft Entra ID account</li><li>Access to an Azure DevOps organization.</li><li>An assigned Azure DevOps access level/license</li></ul><p><strong>Key Access Options for Azure DevOps:</strong></p><ul><li><strong>Free Tier</strong> <strong>(First 5 Users)</strong>: Any M365 user can be added and assigned “Basic” access for free (up to 5 users).</li><li><strong>Stakeholder Access</strong> <strong>(Free)</strong>: Unlimited users can be added with “Stakeholder” access, suitable for non-technical users to manage work items/backlogs.</li><li><strong>Paid Basic Access</strong>: Additional users ($6/user/month) for access to Repos, Pipelines, and Boards.</li><li><strong>Visual Studio (VS) Subscription</strong>: Users with VS Professional or Enterprise subscriptions automatically get Basic or Advanced access (Test Plans) in any organization.</li><li><strong>GitHub Enterprise</strong>: If users have a GitHub Enterprise license, they can get free Basic access to Azure DevOps</li></ul><h3><strong>Setting up your first Azure Devops Project</strong></h3><p>To setup your first Devops Project login to <a href="https://dev.azure.com/">https://dev.azure.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*XVihMSRIX3f7kIw05ecQqg.png" /></figure><p>Next you need to provide the name of your organisation.</p><p>Select the region where you want your repos to be hosted in.</p><p>Select the Azure Subscription at the bottom. Once you have done this you are good to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*xEwwmGV2_GFbPqovpsjByw.png" /></figure><p>Your organisation will be created for you.</p><p>Next you will be prompted to create a Project inside your organisation. You can create multiple projects inside a given organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*SY1PtF9UrnJi59UWVaxGKg.png" /></figure><p><strong><em>Suggestion</em></strong>: You can create Organizations for your entire team if you have enough licenses devops licenses for your team. Inside a given organisation you can create Projects as per the Business Central projects you have one for each. Then you can control which Developer / Functional have access to a given project. If a given User does not have access to a given Project they will not be able to see it. We will take a look into that as well how to control user wise accesssibility.</p><h4>User-wise Accessibility</h4><p>Inside your organization you will find Organization settings. Click on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ad3TYr9atUtJ-OfE3V06_Q.png" /></figure><p>Navigate to Users and this will show the list of Users you have in your organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QR-9ViSjr7Mlxm6ZRWxo0Q.png" /></figure><p>If you want to add more users Click on Add Users and then you can search the name of users available in your Microsoft Entra. During Adding you can manage their accessibility for different projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*ziRJ_2457rs_7fwpAYFmAA.png" /></figure><p><strong>Azure DevOps has two layers of permissions</strong>:</p><ol><li><strong>Access Level (Stakeholder, Basic, Basic + Test Plans, Visual Studio Subscriber)</strong> → determines what Azure DevOps features a user can use.</li><li><strong>Security Groups (Project Readers, Contributors, Administrators, etc.)</strong> → determines what actions a user can perform within a project.</li></ol><p>The <strong>Project Readers</strong> group is designed for users who primarily need visibility into the project but are not expected to contribute changes. A Project Reader can typically: View repositories, Browse source code, View work items, View pipelines and build results, View pull requests.</p><p>The <strong>Project Contributors</strong> group is where most Business Central developers spend their time. Contributors can typically: Clone repositories, Create branches, Commit and push code, Create pull requests, Modify work items, Queue builds, Use pipelines (subject to permissions).</p><p>The <strong>Project Administrators</strong> group has extensive control over the entire Azure DevOps project. These users can: Manage project settings, Create and delete repositories, Configure branch policies, Manage permissions, Configure pipelines, Manage service connections, Create teams and areas, Modify security settings.</p><h4>Setting up Repos</h4><p>Click on your Project to create Repos. Once inside click on Repos. By default Azure Devops creates a default blank Repo with the name of the project. You can either use this one or create a fresh Repo for yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mxr_PmX5cjJGyg7puRWabA.png" /></figure><p>At the top Click on the name of the Repo and click on New Repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eC8JvUrHnmyorzC2L8w7dQ.png" /></figure><p>It will take you to the Dialog box where you will need to provide the name of your repo. This Repo is basically where your Business Central Extension App code will live. The name of the Repo can be anything but it is better if you keep it similar to your Extension App name to avoid any confusion.</p><ol><li>Add the name of the Repo</li><li>Uncheck add Readme. This option is essential for easeness of setting up the Repo we can add the file later on in the Repo.</li><li>By default a main branch will be created for your Repo.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yA-fdCzsz20If0bBcavAKA.png" /></figure><p>This is how your created Repo will look like. It is currently blank and you would need to add the code in it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FHQolGzRWHs67aVVcoyEKw.png" /></figure><p>In order to add some code to your repo there are multiple ways. Now you need to understand how Version management works, before you start working you will need to create a copy of this cloud Repo into your local system and so will the other developers will do. Every developer will have their local version of Cloud Repos living in their system. All the developers need to merge their code to this cloud Repo to make his/her changes available to other developers. Other developers will pull your changes from this cloud Repo. So this cloud Repo is the source of truth, everyone will work in their local system and later on send their changes to Cloud from where others can pull the changes. All the version of your code is tracked and managed by Git.</p><p>Open your VS code and open the Extension which you want to add to your repository. You would require to Install <a href="https://git-scm.com/install/windows">git</a> to your system and also download the win-ca extension into your VS Code. Once you do these things Reopen your VS Code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*1fjd79Ncdq5dafeQ2IkJjA.png" /></figure><p>Now in your VS code on the left hand side Activity Bar you will be able to see source control option click on that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*6b6Le_kkMbEJ5boXgSwFWw.png" /></figure><p>Click on Initialize Repository this will make git to track the changes inside your repository and allow you to connect your local repo with a remote (cloud) repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*ifTKLBIxzsBQr-papKmVRQ.png" /></figure><p>As you can see git will go through all the files in your extension which are not tracked in Source Control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*IGVdtZXjnSgjsPfY2a6dMw.png" /></figure><p>In Azure Devops Now copy the URL of your repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1CYoGaEA7jbFOjtRCRNtA.png" /></figure><p>Go back to VS Code under Source Control. Click on 3 dots -&gt; Remote -&gt; Add Remote.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N5HsvUTPLp3wUunCxbF4Ag.png" /></figure><p>And in the prompt paste the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/827/1*e25yyc6DkgPQzxKR6N73xg.png" /></figure><p>Provide a name to this remote Repo in your local system. You can add anything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*ot2wwtFBADNgMii1mQxrZA.png" /></figure><p>Navigate to Source Control you need to add all your changes by clicking on <strong>+ </strong>icon to add all your changes to staging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*Xghzk-PiWhp3VLAPEy0cjA.png" /></figure><p>Now you are required to input a commit message before commiting your changes. Commit will create a local snapshot of the changes you are doing at the given moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*Yicc1Ptsi4rjtgMvp5HYpg.png" /></figure><p>Now you can pubish your changes to the remote (cloud) repo. This will sync your changes to the cloud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*_pqVqoyKEKBY07jgeveXXQ.png" /></figure><p>Sometimes publish can give you error and this is can be due to missing credentials. This can be handled using a bit of code. Open the Terminal in VS Code. Keyboard shortcut to this is Ctrl + ` .</p><p>Click on +powershell in the terminal and change it to Git Bash.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5OisIT1Aqbt0eEqWLF40w.png" /></figure><p>Enter following command in the Git Bash Terminal and press enter. Replace your_name with your actual name.</p><pre>git config user.name your_name</pre><p>Next past this command and replace your_devops_email with your devops userid and hit enter.</p><pre>git config user.email your_devops_userid</pre><p>While publishing your branch for the first time you might be prompted to login with your devops account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*bVMKRazz9O6DhNkfIlf9og.png" /></figure><p>Once the changes are published. Navigate to your Azure Devops Repo and refresh the browser you will see your code copied to the repo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o0jys_y7066KwLyXUVP1mg.png" /></figure><h4>Branching Strategy</h4><p>Now lets discuss the branching strategy that we will be using for this project. There are various ways to create branches in git and there are lots of recommended approaches to do so. For this setup I will be following the approach which I believe suits the Business Central. <br>We will create Environment wise branches and will promote our changes across these branches using pull requests.</p><p>Inside your Project under Repos navigate to Branches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4uYJVs7rUD6x88ASo79-g.png" /></figure><p>You can create 1 branch for Production, 1 for Development and 1 others as well depending upon the no of environments you have configured in Business central and your project e.g SIT or UAT.</p><p>Just click on New Branch. Give the branch a name, select the branch you want to copy your code from. Click Create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*o8WSQO3kA6gK6Kgl9UknGw.png" /></figure><p>So these are the primary levels of branches I have created. We can create secondary level of branches as well as per our convenience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8-vN9uQQjDDc-Q1cNOnQg.png" /></figure><p>Depending upon your development requirement you can have following kind of branch hierarchy.</p><pre>Dev - <br>    | - Developer001<br>    | - Developer002<br>    | - Hotfix001<br>    | - Feature001<br>SIT -<br>UAT - <br>main (Production) - </pre><p>The idea of this branching strategy is that all the development will take place in Development branch. Using Dev branch we will create multiple secondary branches either developer wise, feature wise or in case some hotfixes are there for production. Once a given development is completed for a given branch and it is no longer needed we can merge it back to the Dev branch and delete it. Then create a pull request to merge the changes from Dev branch to SIT, UAT and Production branches.</p><p>There are few differences between a normal software development with that of Business Central extension development due to which not all of the best practices of software development could be incorporated into Business Central. Like Object no series, field no series, extending the same object by multiple developers, restriction of number of environments so if one developer publish his/her changes others changes might be removed. All of this can create issues while merging the code and during development. So for BC more real-time the changes of individual developers are the better it is.</p><p>Branching strategy are always debatable and someone might have better idea than mine I am happy to be aligned with that strategy if it works better. Let me know what you think is a good branching strategy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=213c6077d324" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[D365 Business Central and SharePoint Integration]]></title>
            <link>https://medium.com/@sourabh_yadav/d365-business-central-and-sharepoint-integration-096264186a8f?source=rss-2a031aa72afd------2</link>
            <guid isPermaLink="false">https://medium.com/p/096264186a8f</guid>
            <category><![CDATA[dynamics-365]]></category>
            <category><![CDATA[d365-business-central]]></category>
            <category><![CDATA[microsoft-entra-id]]></category>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[sharepoint]]></category>
            <dc:creator><![CDATA[Sourabh Yadav]]></dc:creator>
            <pubDate>Wed, 06 May 2026 16:04:16 GMT</pubDate>
            <atom:updated>2026-11-10T14:22:25.678Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nt5FzrsXJDamSGfdes9Abw.png" /></figure><h3>Overview</h3><p>Modern businesses rely heavily on seamless document management and collaboration. Integrating Microsoft Dynamics 365 Business Central with SharePoint enables organizations to securely store, manage, and access files directly from Business Central while leveraging the collaboration capabilities of SharePoint.</p><p>In this guide, we will walk through the complete setup process for configuring SharePoint integration in Business Central using a Microsoft Entra ID App Registration and the built-in Business Central SharePoint Connector.</p><h3>Prerequisites</h3><p>Before starting the setup, ensure the following prerequisites are met:</p><ul><li>A SharePoint site exists within the same Microsoft tenant as your Dynamics 365 Business Central environment</li><li>An active Azure subscription exists in the same tenant</li><li>You have administrator permissions in Microsoft Entra ID:</li><li>Global Administrator, or</li><li>Dynamics 365 Business Central Administrator</li></ul><h3>What We’ll Cover</h3><p>In this article, we will cover:</p><ul><li>Integrating Business Central with SharePoint using a Microsoft Entra ID Application</li><li>Using the built-in SharePoint Connector available in Business Central</li><li>Configuring OAuth 2.0 authentication using Client Secret</li><li>Testing and validating the SharePoint connection</li></ul><h3>Step 1: Register an Entra ID Application</h3><p>To allow Business Central to securely communicate with SharePoint, we first need to create an Entra ID App Registration.</p><h3>Create the App Registration</h3><ol><li>Log in to the Azure Portal using an account with Dynamics 365 Administrator or Global Administrator permissions.</li><li>Search for <strong>App Registrations</strong>.</li><li>Click <strong>New Registration</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*c6QB9akxJ3Z1eRlP7ZSdDw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*I888nfgtS0tHRfZtABQ1FA.png" /></figure><p>On the <strong>Register an Application</strong> page:</p><ul><li>Enter an application name</li><li>Select:</li><li><strong>Supported Account Types</strong> → <em>Accounts in this organizational directory only (Single Tenant)</em></li><li>Configure the Redirect URI:</li><li><strong>URI:</strong><br> <a href="https://businesscentral.dynamics.com/OAuthLanding.htm">https://businesscentral.dynamics.com/OAuthLanding.htm</a></li><li>Click <strong>Register</strong>.</li></ul><h3>Step 2: Configure API Permissions</h3><p>Once the application is created, configure the required SharePoint permissions.</p><h3>Add SharePoint Permissions</h3><ol><li>Navigate to <strong>API Permissions</strong> from the left menu.</li><li>Click <strong>+ Add a Permission</strong>.</li><li>Select <strong>SharePoint</strong>.</li><li>Choose <strong>Delegated Permissions</strong>.</li><li>Expand the All <strong>Sites</strong> section.</li><li>Select:<br>AllSites.Read <br>AllSites.Write</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*GkKvYYRxTRfukmA1YvrItQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOraIeBykpzXhjVb7chnGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*e_HX_vlsYveVMPSUTfOLfg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*EzWaEtk1gXuzbO9xeAeMWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*167eS_65cxxn3EKdXpce3A.png" /></figure><p>This permission is sufficient for:</p><ul><li>Reading files</li><li>Uploading files</li><li>Creating folders and directories within SharePoint</li><li>Click <strong>Add Permissions</strong>.</li></ul><h3>Grant Admin Consent</h3><p>After adding permissions:</p><ol><li>Click <strong>Grant Admin Consent</strong></li><li>Confirm the action</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-eKMxpSKcIi_BLe8a4pGg.png" /></figure><p>Once completed, the status should display:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyM1vp6lXLQcAFrQtJsx2A.png" /></figure><blockquote><em>Granted for &lt;Your Tenant Name&gt;</em></blockquote><blockquote><strong><em>Note:</em></strong><em><br> You must have administrator privileges to grant tenant-wide consent.</em></blockquote><h3>Step 3: Generate Client Secret</h3><p>Business Central will use OAuth 2.0 authentication with a Client Secret to connect securely.</p><h3>Create Client Secret</h3><ol><li>Navigate to <strong>Certificates &amp; Secrets</strong></li><li>Click <strong>New Client Secret</strong></li><li>Enter:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*b7szXMu3DWCNRm0nI_Phgw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*mximQEmdB3X1hecBG5HlpA.png" /></figure><ul><li>Description</li><li>Expiration period</li><li>Click <strong>Add</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*KdKxG-shnRyuowgvmS5H_w.png" /></figure><blockquote><strong><em>Important:</em></strong><em><br> Copy the </em><strong><em>Client Secret Value</em></strong><em> immediately after creation.<br> It will not be visible again once you leave the page.</em></blockquote><p>At this stage, your Entra ID App Registration is fully configured.</p><h3>Step 4: Configure SharePoint in Business Central</h3><p>Now let’s configure the SharePoint connection inside Business Central.</p><h3>Open External File Account Setup</h3><ol><li>Log in to Business Central</li><li>Search for:<br> <strong>Setup External File Accounts</strong></li><li>Open the setup wizard</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*qvoVEkcT2ogbkT6rLtTjGQ.png" /></figure><h3>Configure the Connection</h3><p>Follow the wizard steps:</p><ol><li>Click <strong>Next</strong></li><li>Select <strong>SharePoint</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*_rp9xYIJBWaLbM-_Es8G2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*iZipOMeyuCnKHytH2CQfwA.png" /></figure><p>You will now be prompted to provide the Entra App and SharePoint details.</p><h3>Enter the Following Information</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*PVFkNGI-ncClZSeXSK7IZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*3S1HRcToHn5f6ACsxZH0og.png" /></figure><h3>Configure SharePoint Site Information</h3><h3>SharePoint URL</h3><ol><li>Open your SharePoint site in the browser</li><li>Copy the site URL</li><li>Paste it into the SharePoint field in Business Central</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Ig_hIArH8azqJMPA9lkvsw.png" /></figure><h3>Base Relative Folder Path</h3><p>Specify the target folder path inside your SharePoint document library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*zHGUMQKKtugxVZzwOgPv6Q.png" /></figure><p>Example:</p><pre>Shared Documents/Invoices</pre><p>Format:</p><pre>Shared Documents/&lt;Folder-Name&gt;</pre><h3>Step 5: Complete the Setup</h3><ol><li>Click <strong>Next</strong></li><li>Optionally set the account as the default File Account</li><li>Click <strong>Finish</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*ai7a6jJgsRTUjJtWql-0pQ.png" /></figure><p>Your SharePoint integration setup is now complete.</p><h3>Step 6: Validate the Connection</h3><p>To confirm the integration is working correctly:</p><ol><li>Search for:<br> <strong>External File Accounts</strong></li><li>Open the created account</li><li>Navigate to:<br> <strong>Home → Storage Browser</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*PZd80RAsr9-94sAKaXc03g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*CZir3Wdy6QrQ6r-Li9d2pw.png" /></figure><p>If the Storage Browser opens successfully without errors, the connection has been established successfully.</p><h3>Testing the Integration</h3><p>Once connected, you can:</p><ul><li>Upload files from Business Central to SharePoint</li><li>Create directories and folders</li><li>Access existing SharePoint files</li><li>Manage documents directly from Business Central</li></ul><p>Any changes made in Business Central will reflect in SharePoint and vice versa.</p><h3>Conclusion</h3><p>Integrating SharePoint with Dynamics 365 Business Central provides a secure and scalable approach for centralized document management. By leveraging Microsoft Entra ID authentication and Business Central’s built-in SharePoint Connector, organizations can simplify file handling while maintaining enterprise-grade security and collaboration capabilities.</p><p>This setup is especially useful for:</p><ul><li>Invoice storage</li><li>Document attachments</li><li>Shared project files</li><li>Vendor and customer documentation</li><li>Internal collaboration workflows</li></ul><p>With the integration in place, teams can work more efficiently while keeping documents organized and accessible across Microsoft’s ecosystem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=096264186a8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Azure DevOps & Why BC Developers Should Care?]]></title>
            <link>https://medium.com/@sourabh_yadav/what-is-azure-devops-why-bc-developers-should-care-a8221cdc830c?source=rss-2a031aa72afd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8221cdc830c</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[dynamics-365]]></category>
            <category><![CDATA[business-central]]></category>
            <dc:creator><![CDATA[Sourabh Yadav]]></dc:creator>
            <pubDate>Sun, 12 Apr 2026 15:45:19 GMT</pubDate>
            <atom:updated>2026-04-12T15:46:48.382Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l90g7oGmmv0H8oWtK1eMfw.png" /><figcaption>Azure Devops for Business Central Developers</figcaption></figure><p>If you’ve worked on a <strong>Business Central implementation</strong>, you’ve likely faced this:</p><ul><li>Manual deployments through VS Code</li><li>Last-minute production issues</li><li>Small customizations breaking something else</li><li>“It was working in sandbox, why not in production?”</li></ul><p>Sound familiar?</p><p>This is the reality of many traditional ERP workflows — <strong>slow, error-prone, and stressful</strong>.</p><p>But the industry is changing.</p><p>We are moving from:</p><blockquote><strong><em>Traditional ERP Development → Modern DevOps-Driven Engineering</em></strong></blockquote><h3>What This Series is About</h3><p>This is Part 1 of a complete series where we’ll go from basics → advanced CI/CD pipelines for Business Central.</p><p>In the upcoming blogs, we’ll cover:</p><ul><li>Repositories &amp; branching strategies</li><li>CI/CD pipelines for AL projects</li><li>Automated deployments</li><li>Real-world enterprise setups</li></ul><h3>Who This Series is For</h3><p>This series is designed for:</p><ul><li><strong>Business Central developers/consultants</strong> who want to modernize delivery</li><li><strong>DevOps beginners</strong> looking for real-world ERP use cases</li><li><strong>Students</strong> exploring practical DevOps implementation</li><li><strong>Professionals</strong> aiming for global engineering standards</li></ul><h3>What You’ll Learn in This Series</h3><p>By the end of this series, you’ll understand:</p><ul><li>End-to-end <strong>CI/CD for Business Central</strong></li><li>Managing code using <strong>Git &amp; Azure Repos</strong></li><li>Automating deployments using pipelines</li><li>Using Boards for Agile project management</li><li>Real-world architecture &amp; best practices</li></ul><h3>What is Azure DevOps?</h3><h4>🔹 Overview of Azure DevOps</h4><p>At its core, Azure DevOps is a comprehensive platform that brings together everything required to plan, build, test, and deliver software in a structured and efficient way. Rather than being a single tool, it is a tightly integrated suite of services that covers the entire development lifecycle — from managing source code and tracking work items to automating build and deployment processes.</p><p>What makes Azure DevOps particularly powerful is the way these capabilities are connected, code changes can automatically trigger validation pipelines, development tasks can be directly linked to business requirements, and deployments become consistent, traceable, and repeatable. In essence, it provides a unified environment where teams can collaborate seamlessly while maintaining full visibility and control over how software is developed and delivered.</p><p>Think of it as a <strong>one-stop platform for the entire software lifecycle</strong>.</p><h4>🔹Core Components:</h4><p>One of the biggest strengths of Azure DevOps lies in how its core components are designed to work as a <strong>connected ecosystem rather than isolated tools</strong>. Each service plays a specific role in the software lifecycle, but their real power comes from how seamlessly they integrate with one another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*klIW-nDSskfg1rZkJT8piw.png" /><figcaption>Azure Devops Components</figcaption></figure><p><strong>Azure Repos :</strong></p><p>At the foundation is <strong>Azure Repos</strong>, which provides Git-based version control for managing your source code. For Business Central developers, this means every AL change is tracked, versioned, and linked to a specific requirement or bug, eliminating the uncertainty of “which version is correct.”</p><p><strong>Azure Pipelines :</strong></p><p>Closely tied to this is <strong>Azure Pipelines</strong>, which acts as the automation engine of the platform. The moment code is committed, pipelines can automatically build, validate, test, and even deploy your application, ensuring that issues are caught early and releases become predictable rather than stressful.</p><p><strong>Azure Boards :</strong></p><p>On the planning side, <strong>Azure Boards</strong> brings structure to project management by allowing teams to organize work into epics, features, and user stories. This ensures that development is always aligned with business goals, and every piece of code has a clear purpose.</p><p><strong>Azure Test Plans :</strong></p><p>Complementing Azure Boards is <strong>Azure Test Plans</strong>, which helps teams manage both manual and automated testing efforts, making quality assurance a continuous process rather than a final checkpoint.</p><p><strong>Azure Artifacts :</strong></p><p>Finally, <strong>Azure Artifacts</strong> supports dependency and package management, allowing teams to securely share and reuse components across projects. While it may seem less visible compared to pipelines or repos, it plays a crucial role in maintaining consistency and reliability in larger implementations.</p><p>What truly differentiates Azure DevOps is not just these individual components, but how they come together to create a <strong>single, traceable flow</strong> — from planning a requirement to deploying it in production. This interconnected approach is what enables teams, including those working on Business Central, to move from fragmented processes to a streamlined, end-to-end delivery model.</p><h3>Key Benefits of Azure DevOps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BD3UnBMDHJwpJlQVZBrNKQ.png" /></figure><h3>Why Business Central Developers Should Care</h3><h4>🔹Traditional Business Central Development Challenges</h4><p>Let’s be honest — many BC teams still operate like this:</p><ul><li>Manual deployments via VS Code</li><li>Limited or inconsistent version control</li><li>Difficulty managing <strong>Dev / UAT / Production environments</strong></li><li>Risk of overwriting changes</li><li>Minimal automation in release cycles</li></ul><p>How Azure DevOps Fits into the Business Central Lifecycle</p><p>Traditionally, Business Central projects follow a <strong>straight-line lifecycle</strong>:</p><blockquote><em>Development → Testing → UAT → Production</em></blockquote><p>On paper, it looks structured. In reality, it’s a loop of last-minute fixes, repeated deployments, and constant back-and-forth between teams.</p><ul><li>A feature goes to UAT, something breaks.</li><li>A hotfix is pushed to production, something else stops working.</li><li>And suddenly, you’re asking the same question again:</li></ul><blockquote>“Which version is actually deployed?”</blockquote><h4>🔹Planning with Context, Not Chaos</h4><p>In many Business Central projects, planning often lives in scattered formats — Excel sheets, emails, or meeting notes.</p><p>But ask yourself:</p><blockquote><strong><em>How often have you struggled to trace a piece of code back to its original requirement?</em></strong></blockquote><p>With Azure DevOps, planning becomes structured through Boards. Every feature — say, a customization in the Finance module — is broken down into trackable work items.</p><p>For example, in a real-world implementation:</p><ul><li>An Epic could represent <strong>Finance Automation</strong></li><li>A Feature could be <strong>Vendor Payment Optimization</strong></li><li>A User Story could be <strong>Auto-apply vendor ledger entries</strong></li></ul><p>Now when development begins, it’s not just coding — it’s executing a clearly defined objective.</p><h4>🔹Development with Traceability</h4><p>In traditional setups, developers often work in silos. Code is shared, overwritten, or deployed without full visibility.</p><p>This leads to a common and frustrating question:</p><blockquote>“Who changed this, and when?”</blockquote><p>With Azure DevOps Repos, every change is version-controlled and linked back to a work item.</p><p>Imagine working on a Business Central extension where multiple developers are modifying posting logic. Without version control, conflicts are inevitable. With Azure DevOps:</p><ul><li>Each developer works on a separate branch</li><li>Changes are reviewed before merging</li><li>Every commit has context</li></ul><p>Development becomes not just faster — but <strong>auditable and reliable</strong>.</p><h4>🔹Build &amp; Validation: Catching Issues Early</h4><p>One of the biggest pain points in Business Central projects is discovering issues <strong>too late</strong> — often during UAT or worse, in production.</p><p>Azure Pipelines changes this dynamic completely.</p><p>The moment code is committed, an automated process:</p><ul><li>Compiles the AL code</li><li>Validates dependencies</li><li>Packages the extension</li></ul><p>So instead of asking:</p><blockquote>“Will this work after deployment?”</blockquote><p>You already know the answer <strong>before it even reaches testing</strong>.</p><h4>🔹Testing as a Continuous Process</h4><p>Testing in many ERP projects is still treated as a final phase.</p><p>But here’s a critical thought:</p><blockquote><strong><em>Why should testing only begin after development is “complete”?</em></strong></blockquote><p>With Azure DevOps, testing becomes part of the flow, not a checkpoint at the end.</p><p>In a real scenario:<br> A team working on warehouse management enhancements integrates test codeunits into their pipeline. Every build automatically validates key processes like item tracking and posting.</p><p>The result?</p><ul><li>Issues are caught earlier</li><li>Regression risks are reduced</li><li>Confidence in releases increases</li></ul><h4>🔹Deployment Without the Stress</h4><p>Let’s talk about one of the most stressful moments in any Business Central project:</p><blockquote><strong><em>Production deployment day</em></strong></blockquote><p>Manual steps, last-minute fixes, uncertainty — this is where things often go wrong.</p><p>Azure DevOps replaces this with structured release pipelines.</p><p>Instead of directly pushing changes, deployments move through controlled stages:</p><ul><li>Sandbox for validation</li><li>UAT for business approval</li><li>Production with checks and approvals</li></ul><p>A real-world example:<br> In an enterprise BC implementation, deployments to production are blocked unless:</p><ul><li>All pipelines pass</li><li>Required approvals are completed</li><li>No critical bugs are open</li></ul><p>This transforms deployment from a <strong>risk event → a controlled process</strong></p><h4>🔹Feedback: The Missing Piece Most Teams Ignore</h4><p>Here’s something many teams overlook:</p><p><em>Deployment is not the end of the lifecycle — it’s the beginning of feedback.</em></p><p>Users interact with the system, issues arise, improvements are suggested.</p><p>Without structure, this feedback becomes noise.</p><p>With Azure DevOps:</p><ul><li>Bugs are logged and tracked</li><li>Linked to specific releases</li><li>Fed back into the backlog</li></ul><p>This creates a <strong>closed-loop system</strong> where every release improves the next.</p><h3>Key Takeaways</h3><p>If there’s one thing to take away from this discussion, it’s this: modern Business Central development is no longer just about writing AL code — it’s about how efficiently, reliably, and consistently you deliver it. Azure DevOps plays a critical role in making that possible by bringing structure, automation, and visibility into what is otherwise a fragmented process.</p><p>More importantly, it acts as a bridge between two worlds. On one side, you have traditional ERP practices — manual deployments, reactive fixes, and siloed workflows. On the other, you have modern engineering standards — automated pipelines, continuous delivery, and collaborative development. Azure DevOps connects these worlds, enabling Business Central teams to evolve without completely reinventing their processes overnight.</p><p>And in today’s global job market, this shift is not optional — it’s expected. Organizations are no longer just looking for developers who can build solutions; they are looking for professionals who understand <strong>end-to-end delivery, automation, and scalability</strong>. Adopting DevOps practices is what positions you not just as a Business Central developer, but as a <strong>modern, globally competitive engineer</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8221cdc830c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>