<?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 David Robertson on Medium]]></title>
        <description><![CDATA[Stories by David Robertson on Medium]]></description>
        <link>https://medium.com/@robertsondavid92?source=rss-8037ea7e55e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xUfFzcWfSURCDUZ6</url>
            <title>Stories by David Robertson on Medium</title>
            <link>https://medium.com/@robertsondavid92?source=rss-8037ea7e55e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:50:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@robertsondavid92/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[Self-Taught Route into a Career in Software Engineering]]></title>
            <link>https://medium.com/capgemini-microsoft-team/self-taught-route-into-a-career-in-software-engineering-3e0acb9f934?source=rss-8037ea7e55e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e0acb9f934</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[apprenticeship]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[David Robertson]]></dc:creator>
            <pubDate>Tue, 16 Mar 2021 12:03:44 GMT</pubDate>
            <atom:updated>2021-03-16T12:03:44.694Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrmCfvaE94UOYOVUtkJoTg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cdx2?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">C D-X</a></figcaption></figure><p>For several years now, software engineering has been and remains one of the most popular career aspirations for people around the world. While the traditional route of entry for many, into this field has primarily been through a university degree or formalised instructor-led courses, effective alternatives such as the “<em>self-taught</em>” route do exist. As I have personally leveraged the self-taught option, this post is intended to signpost how I have and continue to use this learning option. The aim is that it will inspire you to achieve your dreams.</p><p>The IT industry is a continuously changing one and this change has even increased with the advent of cloud computing. As a result, many of the traditional formalised training options have curricula that are lagging behind what the industry demands.</p><p>While this does not in any way invalidate the knowledge obtained from such training institutions, it does place a requirement on the individuals obtaining such training to compensate for this skill/knowledge gap.</p><p>So, it is therefore no surprise that self-paced learning is gaining a lot of traction on the internet. The breadth of material available on the internet is so vast that it caters even for those with little or no experience in IT and as such many have been able to develop very robust software engineering capabilities from their bedrooms, leading to actual employment in the IT industry.</p><p>I am one such individual.</p><h4><strong>The Journey</strong></h4><p>A few years ago, I decided I wanted to pursue a career in software engineering, as I discovered I had a passion for automation and enjoyed finding smarter and easier ways to do things.</p><p>With no formal training in computer science, software engineering and no “<em>industry experience</em>”, I took an IT apprenticeship position as a Microsoft cloud technical support engineer. From this position, I eventually moved into a Dynamics 365 administrator position and while in this role, I continued to leverage several internet resources (such as MSDN, StackOverflow, W3Schools, etc) to self-train starting with JavaScript and eventually moved onto C#.</p><p>Here are some of the resources which I used in my journey towards a career in software engineering (remember this list is not exhaustive!):</p><ul><li><a href="https://www.youtube.com/playlist?list=PLlrxD0HtieHhW0NCG7M536uHGOtJ95Ut2">Beginner’s Series to: JavaScript</a></li><li><a href="https://dotnet.microsoft.com/learn/csharp">Learn C#</a></li><li><a href="https://docs.microsoft.com/en-us/learn/modules/get-started-with-powerapps/">Get started with Power Apps</a></li><li><a href="https://www.goodreads.com/book/show/3735293-clean-code">Clean Code: A Handbook of Agile Software Craftsmanship</a></li></ul><p>The primary driver for me then and now has been the understanding that the future is going to be software-driven and whatever leverage I can apply to my existing knowledge will pay off. This served as a push to keep the self-training routine going.</p><p>Initially joining a small but ambitious software company was ideal for me as most of their software development was done in-house. This offered a unique opportunity for me to put into practice the skills I acquired from the online resources and as the saying goes, <em>“practice makes perfect”</em>.</p><p>Eventually, I was able to transition into a managed service consultant role which brought further software development opportunities. Here, many of the skills which I have developed over the years during my self-learning routines became indispensable.<strong> </strong>Since then, I have taken up various roles within the software engineering industry.</p><h4><strong>Why do this?</strong></h4><p>In my experience, with no university degree in software engineering or computer science, the odds are stacked against you — one of the first lessons I learnt. However, not everyone is able to take this route especially in terms of the cost and flexibility which the self-taught option brings to the table.</p><p>Virtually anyone with the drive can leverage self-learning — even those with little or no knowledge about computers. I was fortunate to have a broad spectrum of knowledge on technology which helped my journey into software engineering.</p><p>The primary key to success when taking the self-taught route is personal sacrifice and finding/creating opportunities to put the things you have learnt into practice. This point cannot be emphasised enough!</p><h4><strong>Challenges</strong></h4><p>While self-learning offers several of the previously mentioned benefits, it also presents challenges — for example, you will have to invest evenings and weekends, especially when you already have a 9–5 job. What I have done is to try and weave self-learning activities into my regular 9–5 job. This might be 10 minutes here and there dedicated to the short basic concepts. While this does not eliminate the need to do the evenings and weekend, it minimises it.</p><p>One of the biggest challenges I faced when I “<em>officially</em>” entered the engineering space as a self-taught individual, was that while I have learnt a lot on how to “<em>get things to work</em>”, the enterprise space required more than this. The robust enterprise solutions, require you to think about best practices, i.e., the best way to do things and understand why things are done in a particular way. I had to learn concepts such as <strong><em>SOLID principles,</em></strong> <strong><em>clean code</em></strong> etc. To be honest, learning never really stops, and I am still learning!</p><p>Looking back, I would recommend focusing your self-taught routines on technologies, where there are opportunities and then spend time mastering these technologies. For example, if you work for a company that uses Power Platform or Dynamics 365 you could choose to focus on the technology where Microsoft provides a lot of free resource such as the Power Platform which by its nature caters to the Citizen Developer— remember that it is easier to concentrate on one thing at a time. After this, seek out opportunities to put this knowledge into practice and as such gain experience and confidence!</p><h4><strong>Conclusion</strong></h4><p>In our world today, there are many people who are either aspiring to be software engineers or mindful about how to remain relevant in a fast-changing IT industry. The self-taught route, while not a silver bullet offers a lot of opportunities to address these situations. In this post, I have used my personal experience to show how I have leveraged these training options and hope it has inspired you.</p><p>If you are considering entering the software engineering space, I would highly recommend considering joining an apprenticeship programme such as <a href="https://www.capgemini.com/gb-en/careers/your-career-path/apprenticeships/">the one offered by Capgemini</a>.</p><p>Please note, there are other such programmes — you must search and identify the programme that best suits your needs and ambitions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e0acb9f934" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capgemini-microsoft-team/self-taught-route-into-a-career-in-software-engineering-3e0acb9f934">Self-Taught Route into a Career in Software Engineering</a> was originally published in <a href="https://medium.com/capgemini-microsoft-team">Capgemini Microsoft Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Infrastructure as code deployments — Azure Cli VS ARM templates]]></title>
            <link>https://medium.com/capgemini-microsoft-team/azure-infrastructure-as-code-deployments-azure-cli-vs-arm-templates-1dedd6a7d285?source=rss-8037ea7e55e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dedd6a7d285</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[arm-templates]]></category>
            <category><![CDATA[cli]]></category>
            <dc:creator><![CDATA[David Robertson]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 08:09:43 GMT</pubDate>
            <atom:updated>2019-09-25T09:27:52.908Z</atom:updated>
            <content:encoded><![CDATA[<h3>Pros and Cons of Azure CLI and Arm templates for Deployments</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ieRR9xx2g1JTRGQYwTURjA.png" /></figure><p>Cloud infrastructure enables managing infrastructure such as VMs, web servers, etc, in a repeatable, programmatic way, this is known as infrastructure as code.</p><p>One of the benefits of infrastructure as code is that you can automate the creation, updates, etc, of different resources/environments, giving only slight changes should need to be changed by human operators. Automating the creating of resources reduces manual changes, accidental mistakes and speeds up the process. Some of the other potential benefits can include:</p><p>• Schedule automated deployment — less out of hours work for operations staff</p><p>• Automate deployment smoke testing — its deployed are our components working, if not what is not working</p><p>• Self-healing on known potential errors</p><p>• If cannot be self-fixed, could auto roll to last known good configuration on critical errors</p><p>• Can notify on call of failures / or auto — rollback if required</p><p>Azure can help you implement infrastructure as code by providing resource deployment automation options; the commonly adopted tool is “Arm templates”, one of the other options is Azure CLI. For the two examples, I’ll be deploying both via Azure DevOps.</p><h3>The example scenario:</h3><p>There is a requirement to create an API app on Azure, this API app will receive requests from different client applications for authenticated users (web, mobile, etc). Once this API app has received a request from these clients, it will talk to different systems and collect the data requested (per the user’s permissions) and return that data to the user.</p><p>The API has to authenticate to different systems using different credentials (key/value pairs such as username/password and client/secret), we host the API app on an Azure app service and to store the API app credentials in an Azure Key Vault, the API app must be able to request and read values from the key vault which is achieved by giving the Api app a “system assigned identity” and creating a read access policy on the Keyvault for that identity.</p><p>For both examples in the Azure DevOps release pipeline each stage/environment will have the following 5 variables:</p><p>· apiapp</p><p>· appservice</p><p>· keyvault</p><p>· location</p><p>· resourceGroupName</p><p><strong>ARM templates example</strong></p><p>To deploy these resources to Azure via Azure DevOps using arm templates inside an Azure DevOps release can be achieved using 3 Azure DevOps task, 5 files and library variables (keep in mind we will one this to be repeatable for future environments with minimal differences, ideally only slight name changes for the resources).</p><p>The library variables used for this are:</p><p>· apiapp = demoapiapparm</p><p>· appservice = demoappservicearm</p><p>· keyvault = demokeyvaultarm</p><p>· location = UK South</p><p>· resourceGroupName = demoarm</p><p>1. Task one — Azure Resource group deployment, deploy/create the API APP with app service and a system identity then output the system identity (setting the tasks deployment outputs to “armoutputs”</p><p>a. File one resource template</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/40250c14d25fba81742c35bd83386ce1/href">https://medium.com/media/40250c14d25fba81742c35bd83386ce1/href</a></iframe><p>b. Parameters file</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7aa50bf651178e46240cc725087c7adc/href">https://medium.com/media/7aa50bf651178e46240cc725087c7adc/href</a></iframe><p>2. Task two — PowerShell to convert outputted “identity” to a release variable</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/31470c816b784c591415446d0e2b43ce/href">https://medium.com/media/31470c816b784c591415446d0e2b43ce/href</a></iframe><p>3. Task three, deploy/create the KeyVault with a read access policy for the API app’s system identity</p><p>a. File one resource template</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f90c86de0c5226a09cf4b12bbed7b061/href">https://medium.com/media/f90c86de0c5226a09cf4b12bbed7b061/href</a></iframe><p>b. Parameters file</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f53129f09ab428fda2d882b5bcd47cc/href">https://medium.com/media/9f53129f09ab428fda2d882b5bcd47cc/href</a></iframe><p><strong>Azure CLI example</strong></p><p>To deploy these resources to Azure via Azure DevOps using Azure CLI, inside an Azure DevOps release can be achieved using 1 Azure DevOps task, 1 file and library variables. Note, with the Azure CLI, it’s one line of code per resource, however, a lot less of the resource’s properties are defined.</p><p>The library variables used for this are:</p><p>· apiapp = demoapiappcli</p><p>· appservice = demoappservicecli</p><p>· keyvault = demokeyvaultcli</p><p>· location = UK South</p><p>· resourceGroupName = democli</p><p>Task one — Azure CLI;</p><ol><li>Create the resource group</li><li>Create the app service</li><li>Create the API app with the above app service</li><li>Assign the API app a system identity then</li><li>Create the Keyvault</li><li>Give the API App access to the Keyvault (get permissions for keys and secrets)</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e18844350fd3c75ee747ce91a9fc2ac9/href">https://medium.com/media/e18844350fd3c75ee747ce91a9fc2ac9/href</a></iframe><p><strong>Comparison</strong></p><p>Both are additive/non-destructive, which can allow idempotent deployments however this means changes manually after creation which are not defined by either of these approaches, will not be reset on future deployments (unless the resource is deleted by some other method)</p><p>· <strong>ARM templates</strong> /<em>Azure CLI</em></p><p>· <strong>Declarative /</strong><em> Imperative</em></p><p>· JSON<strong>(JavaScript object notation) for defining ideal state — easier to read/understand objects and used to define what</strong>/<em>Batch/shell for defining implementation — easier to read/understand order of events/logic and define HOW</em></p><p>· <strong>Can download template after manual creation of resources </strong>/ easier <em>understand and implement logic developers are familiar with for code efficiency, such as iterative code (for each loop)</em></p><p>· <strong>Potentially lots of lines of code and files</strong> / <em>Potentially long lines of code</em></p><p>I started with ARM templates, which are deployed via Azure DevOps using one template file per resource and a parameters file per resource per environment (dev, test, prod) etc.</p><p>It ended up for one resource across environments would require many JSON files, you would need to manually change each one for each environment which is counter-intuitive to automation.</p><p>I changed the releases to need one parameter file for all environments and remove standard settings for our resources, then using Azure DevOps I used the override template parameters function to supply the environment-specific variables.</p><p>Often Azure resources need to work together to give the managed system identity of the app access to the key vault, I took the outputs from the deployment and used PowerShell to set the identity as a variable, then did a new resource deployment task to deploy the key vault giving access to the app.</p><p>Azure CLI can use a few simple lines of codes to create your resources and use logic all from one task/script, its easier to read and understand the order,however I soon realized just using Azure CLI does have its downsides when you need to define a lot of properties for your “desired state” of your resources.</p><p><strong>Maybe the best of both worlds?</strong></p><p>Since my initial experience and time to getting around to write this I have discovered the following article <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-deploy-cli">Deploy resources with Resource Manager templates and Azure CLI</a></p><p>To deploy ARM templates using Azure CLI, potentially you can abstractly define objects/resources using arm templates and define your logic/specific implementation of these arm objects/resources using Azure CLI.</p><p>For the above example, you could use Azure CLIs “ az group deployment create” providing the template and parameters for your resources, get the system identity and add it to the key vault access policies. The benefit is you can use these in the most advantageous ways.</p><p>az group deployment create \</p><p>— name ExampleDeployment \</p><p>— resource-group ExampleGroup \</p><p>— template-file storage.json \</p><p>— parameters storageAccountType=Standard_GRS</p><p><strong>Summary:</strong></p><p>As with other tools/technology you should use the best tool for the job and although these two different tools can in most cases be used to start your infrastructure as code journey, if used together appropriately can make that goal a lot easier to achieve.</p><p><strong>Join the Capgemini Microsoft team, open roles </strong><a href="https://www.capgemini.com/gb-en/careers/job-search/?search_term=microsoft&amp;show_posts=50&amp;utm_source=medium_blog&amp;utm_medium=referral&amp;utm_content=countryorganic_link_blog_medium_blog&amp;utm_campaign=other"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dedd6a7d285" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capgemini-microsoft-team/azure-infrastructure-as-code-deployments-azure-cli-vs-arm-templates-1dedd6a7d285">Azure Infrastructure as code deployments — Azure Cli VS ARM templates</a> was originally published in <a href="https://medium.com/capgemini-microsoft-team">Capgemini Microsoft Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TDGi Hack for Education, Team White, Red and Blue Hats experience]]></title>
            <link>https://medium.com/capgemini-microsoft-team/tdgi-hack-for-education-team-white-red-and-blue-hats-experience-b41e550ee2f4?source=rss-8037ea7e55e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b41e550ee2f4</guid>
            <category><![CDATA[powerapps]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[capgemini]]></category>
            <category><![CDATA[hack4good]]></category>
            <dc:creator><![CDATA[David Robertson]]></dc:creator>
            <pubDate>Thu, 19 Sep 2019 11:30:59 GMT</pubDate>
            <atom:updated>2019-10-23T08:08:52.625Z</atom:updated>
            <content:encoded><![CDATA[<h3>TDGi Hack for Education - Team White - Red and Blue Hats experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aYO_iFy732M35GHz3IIHiQ.jpeg" /></figure><p>On the 7th of September, together with several teammates, I went to the TDGi Hack for Education as “Team White, Red and Blue Hats”.</p><p>My first challenge was to find teammates — luckily, I know people who are passionate about Microsoft technology, who were eager to give this is a go even though most of us have little to no experience of these kind of events, so thank you to:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*rntyUK-VX-nzZwPZt74vLw.jpeg" /></figure><p>Jackie Walker</p><p>Aidan O’Leary</p><p>Samm Hitches</p><p>Kieran Holmes</p><p>Darren Tang</p><p>Josh Vicente</p><p>Read below the team’s perspective of the events (and a massive thank you to Those Dynamics Guys for starting and organising these amazing events):</p><p><strong>Samm:</strong></p><p>Overall the day was a resounding success, with lots of learning, fun and the <em>occasional</em> beverage. I will try to convince you<strong> </strong>why <strong>you</strong> should be representing your team at the next event…</p><p>Obvious reasons to attend:</p><ul><li>Do something good to benefit others</li><li>Collaborate and learn</li><li>Get outside your comfort zone</li><li>Have a ton of fun</li></ul><p>The hackathon is designed to push you outside your comfort zone by giving you a seemingly impossible task within the time limit. The trial by fire approach is a sure-fire way to learn hard and fast, and it allows you to understand the areas you may be lacking in knowledge.</p><p>I look forward to seeing <strong>you</strong> at the next one.</p><p><strong>Darren:</strong></p><p>The hackathon was a great experience and I would highly recommend whoever can spare their weekend for a couple of hours to join in and get involved in something great! The best part of the event was the team bonding. In these types of quick solution events, you must be able to communicate and work with your team on all fronts.</p><p>Our team worked well together to create the solution and communication was always at the core of what we did that day. It was great to work on a project which helped the educational sector with our truancy solution. Hopefully, some ideas can be taken from our solution to have a greater impact on the educational industry.</p><p><strong>Joshua:</strong></p><p>What an experience! My first time at an event like this, I was very excited (and more than a bit nervous) to get stuck in and build something fresh with what I know whilst also learning new things along the way.</p><p>As it turns out, I did not need to be nervous at all; not only was my entire team warm and welcoming to a newcomer such as myself, but the gracious hosts and friendly competitors treated us like colleagues. I felt at home in a working environment of like-minded individuals; it was an excellent experience that I will very happily repeat.</p><p>We had a lot of good internal discussions before beginning development. We wanted to create a portal to allow parents to monitor their child’s attendance and academic progress (objective 1).</p><p>The ability for a parent to mark their child as absent for the day and provide a reason to create a paper trail for both the home and the school. Linking this to an attendance monitor to be used in the classroom would allow teachers to see authorized absences as soon as they are reported (objective 2). As the team’s industry expert, I gave input where I could on how things should be structured to make the most sense for both teachers and parents to use.</p><p>There were a few technical issues which we attempted to circumvent but ultimately, the team collaborated and decided to reduce the scope of our project by rethinking the portal concept and switching to PowerApps. Unfortunately, we ran out of time before we were able to produce results but we had a functional backend which I was very pleased with. Coming away with what I’ve learned from this experience (and what I hope to learn over the next 12 months), I’m excited to try again next year and produce something truly exceptional with the team.</p><p>Go Red White and Blue Hats!</p><p><strong>Jackie:</strong></p><p>The hackathon for me was a great day however it was also a day for lots of lessons learned.</p><p>Our experience started with us being on the back foot slightly as we never received the objectives the day before, when it seems all other teams had.</p><p>However, I did still really enjoy the day and would love to take part in another hackathon, only making sure all the lessons learned from this experience were applied</p><ul><li>Meet earlier</li><li>More planning of the design, taking into consideration the skill-set of team members involved.</li><li>Only start building once a full process design mapped out and a task list created of all steps required to achieve the design.</li><li>Ensure everyone knows and understand what we are trying to achieve so we can work more cohesively together.</li></ul><p>This was my first hackathon so was not sure what to expect and was quite nervous, however, everyone we met from the other teams was friendly and we all enjoyed it, and would all do it again.</p><p><strong>Aidan:</strong></p><p>On a sunny Saturday morning, I decided to spend the day inside by attending the TDGi Hack for Education. The day started with the team meeting beforehand and discussing ideas of what we think the event will be like. We then made our way to the event.</p><p>When it kicked off, we were given the option to choose from a few different aspects related to the education industry. Our team decided to work on a system where a teacher could log into Microsoft Dynamics 365 and update information about their students and how they were doing. It included a service to notify parents when their children are absent from class, and a portal for parents to log into to view their children’s progress.</p><p>We started by designing the data model on paper. At the end of the event we completed the backend teacher system, although the power portal didn’t get finished (this was mainly due to me trying to learn most of how it works during the event).</p><p>I had a great time and thoroughly enjoyed it. The event was a good team-building exercise and gave us all a chance to get to know each other better while working on a common goal.</p><p>The event gave us the chance to network with and meet a lot of other people that are part of the Dynamics 365/Power Platform industry. Another positive aspect of the event was that I was given the chance to work with Power Portals which I don’t usually use so it was a good learning experience. Next time it would be nice to explore and maybe include the new AI Builder in our solution.</p><p>Overall the event was a fun experience and I will be attending the next one.</p><p><strong>David:</strong></p><p>This was my second time going to this type of event and first as team captain. We faced some challenges, however, after gaining some experience and having fun, we’re all raring to go for the next one!</p><p>Join the Capgemini Microsoft team, open roles <a href="https://www.capgemini.com/gb-en/careers/job-search/?search_term=microsoft&amp;show_posts=50&amp;utm_source=medium_blog&amp;utm_medium=referral&amp;utm_content=countryorganic_link_blog_medium_blog&amp;utm_campaign=other"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b41e550ee2f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capgemini-microsoft-team/tdgi-hack-for-education-team-white-red-and-blue-hats-experience-b41e550ee2f4">TDGi Hack for Education, Team White, Red and Blue Hats experience</a> was originally published in <a href="https://medium.com/capgemini-microsoft-team">Capgemini Microsoft Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dynamics 365-integrate without requiring a licensed user]]></title>
            <link>https://medium.com/capgemini-microsoft-team/dynamics-365-application-users-no-additional-license-required-and-no-limit-on-quantity-4bdc49f8ce2d?source=rss-8037ea7e55e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bdc49f8ce2d</guid>
            <category><![CDATA[webapi]]></category>
            <category><![CDATA[azure-active-directory]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[dynamics-365]]></category>
            <dc:creator><![CDATA[David Robertson]]></dc:creator>
            <pubDate>Thu, 04 Apr 2019 13:48:42 GMT</pubDate>
            <atom:updated>2019-10-21T14:31:43.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*4hYksppDIz8RDvh-WcBWbg.jpeg" /></figure><h3>Introduction</h3><p>The goal of this blog post is to inform you about the benefits of application users, an approach of authenticating and interacting with Dynamics 365 online for your application/s without requiring a licensed user account. This approach is particularly useful for larger projects where you exceed the 5 non-interactive user accounts.</p><p>**Updated October 2019 for new API limitations introduced</p><p>̶T̶h̶i̶s̶ ̶a̶p̶p̶r̶o̶a̶c̶h̶ ̶b̶e̶c̶o̶m̶e̶s̶ ̶m̶o̶r̶e̶ ̶b̶e̶n̶e̶f̶i̶c̶i̶a̶l̶ ̶a̶s̶ ̶M̶i̶c̶r̶o̶s̶o̶f̶t̶ ̶h̶a̶s̶ ̶r̶e̶c̶e̶n̶t̶l̶y̶ ̶a̶n̶n̶o̶u̶n̶c̶e̶d̶ ̶a̶ ̶n̶e̶w̶ ̶A̶P̶I̶ ̶t̶h̶r̶e̶s̶h̶o̶l̶d̶ ̶ ̶i̶n̶ ̶t̶h̶e̶ ̶a̶r̶t̶i̶c̶l̶e̶ ̶i̶t̶ ̶s̶t̶a̶t̶e̶s̶:̶<br>̶“̶W̶e̶ ̶l̶i̶m̶i̶t̶ ̶t̶h̶e̶ ̶n̶u̶m̶b̶e̶r̶ ̶o̶f̶ ̶A̶P̶I̶ ̶r̶e̶q̶u̶e̶s̶t̶s̶ ̶m̶a̶d̶e̶ ̶b̶y̶ ̶e̶a̶c̶h̶ ̶u̶s̶e̶r̶,̶ ̶p̶e̶r̶ ̶o̶r̶g̶a̶n̶i̶z̶a̶t̶i̶o̶n̶ ̶i̶n̶s̶t̶a̶n̶c̶e̶,̶ ̶w̶i̶t̶h̶i̶n̶ ̶a̶ ̶f̶i̶v̶e̶ ̶m̶i̶n̶u̶t̶e̶ ̶s̶l̶i̶d̶i̶n̶g̶ ̶w̶i̶n̶d̶o̶w̶.̶ ̶“̶<br>̶A̶c̶c̶o̶r̶d̶i̶n̶g̶ ̶t̶o̶ ̶t̶h̶e̶ ̶e̶r̶r̶o̶r̶ ̶m̶e̶s̶s̶a̶g̶e̶ ̶t̶h̶e̶ ̶n̶e̶w̶ ̶l̶i̶m̶i̶t̶ ̶i̶s̶ ̶“̶N̶u̶m̶b̶e̶r̶ ̶o̶f̶ ̶r̶e̶q̶u̶e̶s̶t̶s̶ ̶e̶x̶c̶e̶e̶d̶e̶d̶ ̶t̶h̶e̶ ̶l̶i̶m̶i̶t̶ ̶o̶f̶ ̶4̶0̶0̶0̶,̶ ̶m̶e̶a̶s̶u̶r̶e̶d̶ ̶o̶v̶e̶r̶ ̶t̶i̶m̶e̶ ̶w̶i̶n̶d̶o̶w̶ ̶o̶f̶ ̶3̶0̶0̶ ̶s̶e̶c̶o̶n̶d̶s̶.̶”̶<br>̶T̶h̶e̶ ̶a̶p̶p̶l̶i̶c̶a̶t̶i̶o̶n̶ ̶u̶s̶e̶r̶ ̶m̶i̶g̶h̶t̶ ̶a̶l̶l̶o̶w̶ ̶y̶o̶u̶ ̶t̶o̶ ̶b̶e̶t̶t̶e̶r̶ ̶s̶e̶g̶m̶e̶n̶t̶ ̶y̶o̶u̶r̶ ̶a̶p̶p̶l̶i̶c̶a̶t̶i̶o̶n̶\̶s̶ ̶a̶n̶d̶ ̶h̶a̶n̶d̶l̶e̶ ̶l̶o̶a̶d̶(̶f̶u̶r̶t̶h̶e̶r̶ ̶t̶e̶s̶t̶i̶n̶g̶ ̶r̶e̶q̶u̶i̶r̶e̶d̶)̶ ̶w̶i̶t̶h̶o̶u̶t̶ ̶r̶e̶a̶c̶h̶i̶n̶g̶ ̶t̶h̶i̶s̶ ̶l̶i̶m̶i̶t̶a̶t̶i̶o̶n̶.̶N̶o̶t̶e̶ ̶t̶h̶i̶s̶ ̶s̶h̶o̶u̶l̶d̶ ̶n̶o̶t̶ ̶b̶e̶ ̶u̶s̶e̶d̶ ̶b̶y̶ ̶n̶o̶r̶m̶a̶l̶ ̶u̶s̶e̶r̶s̶ ̶a̶s̶ ̶t̶h̶e̶s̶e̶ ̶a̶c̶c̶o̶u̶n̶t̶s̶ ̶a̶r̶e̶ ̶n̶o̶t̶ ̶s̶u̶p̶p̶o̶s̶e̶d̶ ̶t̶o̶ ̶a̶c̶c̶e̶s̶s̶ ̶t̶h̶e̶ ̶U̶I̶.̶</p><p>Per the article <a href="https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations">here</a> on the additional API limits:</p><p><em>Effective October 2019, to help ensure service levels, availability, and quality, there are entitlement limits to the number of requests users can make each day across model-driven apps in Dynamics 365 (such as Dynamics 365 Sales and Dynamics 365 Customer Service) PowerApps, and Microsoft Flow.</em></p><p>for example:</p><p><strong>User licenses</strong></p><p><strong>Number of API requests / 24 hours</strong></p><p>Dynamics 365 Enterprise applications:20,000</p><p>Dynamics 365 Professional :10,000</p><p><em>Common Data Service also provides the ability to have identities that do not require any user license to interact with the service. There are three types of these users:</em></p><p><em>· </em><a href="https://docs.microsoft.com/dynamics365/customer-engagement/admin/create-users-assign-online-security-roles#create-an-application-user"><em>Application users</em></a></p><p><em>· </em><a href="https://docs.microsoft.com/dynamics365/customer-engagement/admin/create-users-assign-online-security-roles#create-a-non-interactive-user-account"><em>Non-interactive users</em></a></p><p><em>· </em><a href="https://docs.microsoft.com/dynamics365/customer-engagement/admin/create-users-assign-online-security-roles#create-an-administrative-user-account"><em>Administrative users</em></a><em>.</em></p><p><strong>These non-licensed users have a base pool larger than the comparative licensed user for example</strong> “<em>If a tenant has at least one Dynamics 365 enterprise subscription, they will get 100,000 requests per 24 hours”</em></p><p><strong>So what happens if this is exceeded and what can be done about it?</strong></p><p>Per the FAQ</p><p><strong><em>Will my Integrations stop working if application users exceeds Base Request capacity?</em></strong></p><p><em>Integrations will not be stopped for occasional and reasonable overages at this point of time. Administrators would be notified about overages and will be able to add PowerApps and Microsoft Flow request capacity to be compliant.</em></p><p>and per the document <a href="https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations#powerapps-and-microsoft-flow-capacity-add-on">here</a></p><p><strong><em>PowerApps and Microsoft Flow capacity add-on</em></strong></p><p><em>PowerApps and Microsoft Flow capacity add-on allows customers to purchase additional requests which can be assigned to any user who has a PowerApps/Microsoft Flow license as well as Dynamics 365 license. These can be assigned to an application, and administrative and non-interactive users.</em></p><p><em>Each capacity add-on provides an additional 10,000 requests/24 hours which can be assigned to any user. Multiple capacity add-ons can also be assigned to the same user.</em></p><h3>Non-interactive user account</h3><p>First thing to look at is something called a non-interactive user account:</p><p>According to Microsoft</p><p><em>“It is used for programmatic access to and from Dynamics 365 for Customer Engagement apps between applications. A non-interactive user account lets these applications or tools, such as a Dynamics 365 for Customer Engagement apps to ERP connector, authenticate and access Dynamics 365 for Customer Engagement apps (online), without requiring a Dynamics 365 for Customer Engagement apps (online) license. For each instance of Dynamics 365 for Customer Engagement apps (online), you can create up to five non-interactive user accounts.”</em></p><p>More information on this can be found here: <a href="https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/create-users-assign-online-security-roles#create-a-non-interactive-user-account">https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/create-users-assign-online-security-roles#create-a-non-interactive-user-account</a></p><p>The downside to (non-interactive user accounts) is you are limited to 5 per instance.</p><h3>Application user</h3><p>The 5 limitation of service user accounts can be too limiting, you can use application user licences, Microsoft describe as:</p><p><em>“Introduced in December 2016 Update for Dynamics 365 (online), you can use server-to-server (S2S) authentication to securely and seamlessly communicate with December 2016 update for Dynamics 365 (online) with your web applications and services. S2S authentication is the common way that apps registered on Microsoft AppSource use to access the Dynamics 365 (online), version 8.2 data of their subscribers. All operations performed by your application or service using S2S will be performed as the application user you provide rather than as the user who is accessing your application.</em></p><p><em>All application users are created with a non-interactive user account, however they are not counted towards the five non-interactive user accounts limit. In addition, there is no limit on how many application users you can create in an instance.”</em></p><p>More info on this can be found here: <a href="https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/create-users-assign-online-security-roles#create-an-application-user">https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/create-users-assign-online-security-roles#create-an-application-user</a></p><p>So great there is a way of authenticating and accessing Dynamics 365 data that:</p><p>· Does not require a license</p><p>· You can create as many of these application accounts as you like</p><p>· If you want an app to share a user account as they have the same permission requirements you can give them each their own security key which can have its own expiry date or can be revoked as required</p><p>· For each application you can give least possible permissions to do what is required (IE the app can have its own user account and security role which only has access permissions required to do its job)</p><h3>How do we set this up?</h3><p>1. Follow these steps by Microsoft to Register a Dynamics 365 for Customer Engagement app with Azure Active Director <a href="https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/walkthrough-register-dynamics-365-app-azure-active-directory">https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/walkthrough-register-dynamics-365-app-azure-active-directory</a> and take note of the “Application ID” of the application you just created</p><p>2. Follow the instructions here for creating a security key for the app you registered the step before and note down the generated “security key” <a href="https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#get-application-id-and-authentication-key">https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#get-application-id-and-authentication-key</a></p><p>3. On your Dynamics 365 instance you want this to access go to Settings &gt; Security &gt; Users</p><p>4. On the view selector, select “Application Users”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*2Pm8Rfid54YkvyeIDveS2A.png" /></figure><p>5. Select “New”</p><p>6. On the create new user form, if not already selected change the form used to “User:application user”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*g-vr7JU_MHZx9D-k3IXHDA.png" /></figure><p>7. Create the new user</p><p>a. User Name: give it a username</p><p>b. Application ID: this will be the application id of the Azure app you registered and took note of earlier</p><p>c. Full Name: give it a full name</p><p>d. Primary Email: give it an email address</p><p>8. After the user is created, like normal user accounts it will need to be given a security role, this can be either one of the out of box security roles or my recommendation is to create a security role that just has the permissions required for the app to function as required.</p><h3>Code example using an application account</h3><p>I will show you the method of authentication using the Dynamics 365 web API and a C# console app: Note, this uses “Microsoft.IdentityModel.Clients.ActiveDirectory” which I added via NuGet</p><pre>using System;</pre><pre>using System.Threading.Tasks;</pre><pre>using System.Net.Http;</pre><pre>using System.Net.Http.Headers;</pre><pre>using Microsoft.IdentityModel.Clients.ActiveDirectory;</pre><pre>namespace ConnectToDynamics365CE</pre><pre>{</pre><pre>class Program</pre><pre>{</pre><pre>static void Main(string[] args)</pre><pre>{</pre><pre>//enter in the url for your Dynamics 365 online instance below, for the way i’ve coded it make sure it ends with “.com/” also you will probably want to store this as a variable (not in the code) rather than hard coding these in for deployment automation purposes</pre><pre>string D365URL = “https://yourinstance.crm11.dynamics.com/&quot;;</pre><pre>//this will be the query you will be submiting to the API, for the instance defined by the URL above for example purposes I am just querying top 3 contacts</pre><pre>string query = “contacts?$top=3”;</pre><pre>//create a string for your applicationID and Secret key you will probably want to store this as a variable (not in the code) rather than hard coding these in for security and deployment automation purposes</pre><pre>string applicationId = “applicationID”;</pre><pre>string secret = “Secretkey”;</pre><pre>// create a string which calls the Dynamics 365 api using the above variables and stores the response: you don’t need to store it as as a string you could deserialise the response json to an object ect</pre><pre>string D365response = QueryDynamics365API(D365URL, query, applicationId, secret).Result;</pre><pre>// this is just writing out the response body either to prove it works or give you an indication of why it failed</pre><pre>Console.WriteLine(D365response);</pre><pre>}</pre><pre>public static async Task&lt;string&gt; QueryDynamics365API(string D365URL, string query, string applicationId, string secret)</pre><pre>{</pre><pre>// this is taking the Dynamics 365 URL and adding the API url bits</pre><pre>string api = D365URL + “api/data/v9.1/”;</pre><pre>//This thing I found is quite cool, you send a request to get the authorisation URL from the Dynamcs 365 instance API you want to connect to, although it does have an issue which I will explain in next comment</pre><pre>AuthenticationParameters ap = await AuthenticationParameters.CreateFromResourceUrlAsync(new Uri(api));</pre><pre>//The ADAL (Azure Active Directory Authentication Libraries) this uses (V4) is much stricter in regards to authentication url you can use, the request to get the auth url done just before returns the url with “/oauth2/authorize”appended which if you send a request for a access token using v4 with this appended it will return an error, hence the below line of code removing “/oauth2/authorize” from the url</pre><pre>ap.Authority = ap.Authority.Replace(“/oauth2/authorize”, “”);</pre><pre>//creates Client credentials using the applicationId and Secret</pre><pre>ClientCredential creds = new ClientCredential(applicationId, secret);</pre><pre>// Authenticate the registered application with Azure Active Directory.</pre><pre>AuthenticationContext authContext = new AuthenticationContext(ap.Authority);</pre><pre>AuthenticationResult authResult = await authContext.AcquireTokenAsync(ap.Resource, creds);</pre><pre>//stores the token from the authResult</pre><pre>string token = authResult.AccessToken;</pre><pre>// instantiating the request status and giving default value, this will change if request succeeds. only used for demo purposes</pre><pre>string requestStatus = “error: “;</pre><pre>// creates a new http client to send api request</pre><pre>using (HttpClient httpClient = new HttpClient())</pre><pre>{</pre><pre>//adds authorisation using the token generated earlier</pre><pre>httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue(“Bearer”, token);</pre><pre>//awaits for response from the HTTP request</pre><pre>HttpResponseMessage response = await httpClient.GetAsync(api + query);</pre><pre>//if the response is a success</pre><pre>if (response.IsSuccessStatusCode)</pre><pre>{</pre><pre>//I’m just setting the request status to success, this can be changed per your requirements such as deserialising into a object ect</pre><pre>requestStatus = “success =”;</pre><pre>}</pre><pre>//this is returing the request status text + the content of the request response</pre><pre>return requestStatus + await response.Content.ReadAsStringAsync();</pre><pre>}</pre><pre>}</pre><pre>}</pre><pre>}</pre><h3>Conclusion</h3><p>After using application accounts, any application I build that needs to interact with Dynamics 365 this will be my first choice. Software vendors who provide applications which integrate with Dynamics 365 should consider providing this way of authenticating for their application. This decrease the total cost of ownership of their software as it would not require a Dynamics 365 license for the application whilst possibly making it more secure.</p><p>Image from <a href="https://blogs.technet.microsoft.com/uspartner_learning/2016/10/16/introduction-to-microsoft-dynamics-365-licensing/">here</a></p><p><strong>Join the Capgemini Microsoft team, open roles </strong><a href="https://www.capgemini.com/gb-en/careers/job-search/?search_term=microsoft&amp;show_posts=50&amp;utm_source=medium_blog&amp;utm_medium=referral&amp;utm_content=countryorganic_link_blog_medium_blog&amp;utm_campaign=other"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bdc49f8ce2d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capgemini-microsoft-team/dynamics-365-application-users-no-additional-license-required-and-no-limit-on-quantity-4bdc49f8ce2d">Dynamics 365-integrate without requiring a licensed user</a> was originally published in <a href="https://medium.com/capgemini-microsoft-team">Capgemini Microsoft Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>