The 11cents total is over several days, and the breakdown shows it's almost entirely bandwidth costs - which doesn't have a free bucket. My AzureFunctions don't exceed the allowed free tier, so I'm not paying for any compute time.
Where do we go from here?
What can you do with PowerShell? Desired State Configuration? Download lists to CSV? Synchronize and fix metadata? Locate orphaned or misplaced documents and fix that? Improve and merge user profile properties? Provision users and sites and what else do you fancy?
Does this give you wild ideas?
Azure Functions is Serverless
When we say Azure Functions is Serverless - it always seems we are saying we don't need servers (and thus don't need IT Pros). This isn't strictly the truth - which is that the server is maintained by professionals, and developers could focus on writing code.
But after working on these PowerShell for the last two weeks - actually, I'm beginning to wonder whether there will be a day we don't need Developers.
An analyst says to a Bot - I want this System A to connect to this System B and put result in this System C. The bot arranges three connections and suggest how the parameters will be connected. Offers to perform a trial run. Analyst checks it and approves it. The code goes into production.
Think about this. Everyone needs to evolve. IT Pros - you have a huge opportunity here to use your PowerShell skills to provide huge business value. Developers - you should use the best tools to enable your users and do more, this is really easy to get into.
Tell me what you think
I really want to know what you think - if you can spend a bit of time and leave a comment below. Where are we going as developers, where are we going as IT Pros? What kind of PowerShell-AzureFunction are you going to build? Does PnP need a repository for PowerShell recipes?
It's so nice to see the pieces fit together well.