Also, during all this time, I have seen program evolve and change. When I was accepted, I was a \u201cSharePoint MVP\u201d. It is still stunning how many of my MVP colleagues still write \u201cSharePoint MVP\u201d on their resumes, even if that category has not been called like that for ages. It was first merged into a big \u201cOffice 365 MVP\u201d category, which was then renamed into \u201cOffice Servers and Services MVP\u201d and finally into \u201cOffice Apps and Services MVP\u201d category. That sticking to the \u201cSharePoint MVP\u201d label, however, shows the pride that former SharePoint MVPs still have in being SharePoint MVPs – that\u2019s a very special bunch of people. And, in all honesty, nobody can create communities like us, SharePoint MVPs. Don\u2019t even start me about parties that we make.<\/p>\n\n\n\n Since I am a developer, few years ago my former MVP lead has suggested me to be additionally awarded with \u201cOffice Development MVP\u201d, when that award category was first introduced. I liked the idea – I am a dev after all. And since 2015, when multiple award categories became possible, I was one of the first 10 MVPs in the world who were awarded in two categories (Office Apps and Services, Office Dev).<\/p>\n\n\n\n And while that was nice, and I felt honored, me and Office Dev category were drifting more and more apart since then. Office Dev focuses nowadays on SPFx, and related technologies, which is neither bad nor wrong, but it is not what I do. I probably wrote 5 modern webparts and one extension in the past few years, and none of them was for production (all of them were for demos and showcases). While I make my point on following what is going with SPFx, and I always try to have the latest version installed on my machine, it is not what I do daily. And everyone who knows me is probably aware of my special \u201clove\u201d for JavaScript (which, btw, I use since 1998, and I am unfortunately very proficient in it).<\/p>\n\n\n\n What I do when I develop \u2013 heavily influenced by my work \u2013 is Azure AppService, to the largest degree. Azure Functions. Azure Active Directory. Sure, I use lot of Office 365 related APIs within those services (Graph, CSOM\u2026), but honestly, it could be any API. If I look at my dev sessions in the past two years, all of it was about Azure dev. Architecture sessions, OAuth flows within AAD, using WebJobs and Functions as SharePoint Timer replacements, etc. This Saturday, in Vianen\/Netherlands, I delivered a session on using Azure Cognitive Services for automated metadata extraction within SharePoint. Azure Again. <\/p>\n\n\n\n I was talking to my MVP lead recently about this, and the conclusion was that it makes the most sense to switch my second category from Office Dev into Azure, because it fits much more to what I actually do. So, that happened. From today, I am officially an Azure MVP as well. I am definitely not dissing my original SharePoint MVP award \u2013 I will want to keep that one as long as they want to have me. It is the probably the best community that ever existed in the IT world, and I am so proud to be a part of it. But I am also really looking forward to be a member of the Azure MVP community in the future.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.sharedove.com\/adisjugo\/wp-content\/uploads\/2019\/02\/MVP_Horizontal_BlueOnly.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/blog.sharedove.com\/adisjugo\/wp-content\/uploads\/2019\/07\/office-365-logo-1.png\"){kind=logo}
<\/figure><\/li>![\"\"](\"https:\/\/blog.sharedove.com\/adisjugo\/wp-content\/uploads\/2019\/07\/azurelogo-1.png\")
<\/figure><\/li><\/ul>\n