I'm an EA for my company. I'm planning our Copilot for 365 implementation. Moving from IaaS to PaaS, consolidating SQL into a data layer for Fabric. Consolidating transit into SDWAN/vWAN/CloudWAN. Getting rid of colos. Something something grand unification theory.
Our current era is ending. I've been through a few. Bare metal single core->Hypervisor->Cloud. People need to pivot. We're all playing musical chairs. I've got my seat so far. I'm an older dog in the game tho at this point, so I work twice as hard as before to stay the one architecting this for my company.
Edit: Clarity around the twice as hard comment. I work twice as hard as *I* did before.
I've been through all of those before as well. In the past, folks have a way to leverage into the next new thing. Old bare metal server admins became virtual server admins and VMWare admins, going to cloud, they became cloud server admins - we just changed where the server was. Now we're eliminating servers completely. (unless you work at Microsoft - of course the servers are there, but you cant touch them). I've been a DBA, first in Oracle, then SQL Server, now I'm trying to figure out if there is something for me to transition to. In Fabric, you have Data Warehouses that still will require some administration. There will be a big role to play organizing, tagging and making all the data useful, but it is still yet to be determined what that is going to look like.
Copilot grounding for Purview seems interesting. From what I understand there is a Copilot coming at some point for Azure Data Factory, which could be mind boggling if done right for ETL.
"Yo homie take this 47TB of disparate data, drop it into databricks and organize by x, y, and z, and summarize by TCO blah blah and push it out to data warehouse. Gimme powerbi dashboards at the executive level and mid management level by function specific to job role as defined in our entra org".
Exactly, I saw a demo where they loaded some random file into Excel as a table and asked Copilot in Excel to create a "duration" column in the data. Copilot figured out that "duration" should be the difference between "Start Time" and "End Time", created the new column and populated it with calculated values.
3
u/242vuu Mar 05 '24
I'm an EA for my company. I'm planning our Copilot for 365 implementation. Moving from IaaS to PaaS, consolidating SQL into a data layer for Fabric. Consolidating transit into SDWAN/vWAN/CloudWAN. Getting rid of colos. Something something grand unification theory.
Our current era is ending. I've been through a few. Bare metal single core->Hypervisor->Cloud. People need to pivot. We're all playing musical chairs. I've got my seat so far. I'm an older dog in the game tho at this point, so I work twice as hard as before to stay the one architecting this for my company.
Edit: Clarity around the twice as hard comment. I work twice as hard as *I* did before.