In summary, what have we learned?
Well, working as a Microsoft specialist for the last couple of decades at least,
I can attest that historically Microsoft has taken really
good care of its customers as they go slowly from one
version of Windows Server to another.
I mean, not to dig other vendors, but when you think about what Apple does,
where if you get a couple versions behind,
you're liable to lose support immediately,
not just from the first party,
but also from third party because third parties are heavily encouraged,
and I put encouraged in air quotes,
to refactor their software to support the latest
version of Apple operating systems.
Don't get me started on that.
Anyway, I hope that you're comfortable with command‑line tools.
I do my best to include lots of PowerShell in my training because I think
it's a great way to future proof your career as an IT professional. Even if
you don't plan to be a Microsoft specialist,
PowerShell 7 is cross platform, and it appears in non‑Microsoft
context including who incidentally are not Apple,
macOS, and Linux operating systems.
And the other reason why I like to include PowerShell in my
courses, besides helping you with your career, is, and I know
I've mentioned this many times,
most of the associate and expert‑level Azure exams assume that
you have intermediate PowerShell skills,
so almost guaranteed you'll see PowerShell code on those exams.
Now the queue up for the next module is how can we
rehost our IIS‑based web apps, not to another local server,
but we're doing a migration to Azure.
Do we have to set up a VM in Azure?
Do we have to convert the app to containers or can we run it without containers?
These sorts of questions,
very real world and applicable questions that we're going to
answer and more in the next module entitled,
Migrate IIS Workloads to Azure.
Thanks very much. I'll see you then.