Hi Elden, I believe Copilot could help with DO / DON'Ts when deploying Windows Server and roles, as well help to align with best practices from Microsoft techcommunity Windows Server best practices blogposts and PowerShell BPA. This is what I can imagine from the top of my mind. A don't is for example cumulating roles and features on Domain Controllers like AD CS, DHCP (esp. with DNSDHCPProxy enabled). I could imagine that Co Pilot could help admins, eventually with configuring things (would either need WAC extension, BPA is often requested here), or just linking to knowledgeable articles when PowerShell or Server Manager wizard detect a "violation". Not sure if this is at all feasible or technical possible. Just thinking out loud.

I was in a recent discussion with some in the Windows Server community around this idea (What a Windows Server Copilot might look like) and there were suggestions performing queries against Event Viewer event log data and querying Active Directory via natural language copilot type queries. Examples included: "Show me all logon events for this user account in the last week" "Show me all users who were authenticated between 9 and 10am by any DC in the Domain" "Show me all accounts in the domain who haven't signed on in the last 4 weeks" "What does this event indicate and what other events are correlated with it?"

I think the main things would be a way to manage the different CoPilots in our Org as well as ensuring that it is protected to our Domain as default. Having it in the shell would be another bonus too.