Chase Wilson

@dbradish-microsoft, can you review this before merge? :)

> The majority of our short-summary values are in the active voice with an understood "you". So " Manage ..." or " Configure...". Our short-summary values will all be standardized...

Hey @martinprikryl thanks for the feedback here. This is a fair point. We don't have an article talking about concurrency specifically realated to PowerShell but have an [issue open here](https://github.com/MicrosoftDocs/PowerShell-Docs/issues/5097)...

Hey @Hanifff, thanks for commenting here. This Item is to track the request and interest for these features in Azure CNI Powered by Cilium. Right now there isn't a timeline...

> This would be really good to have. Which portion of this are you most interested in? The Cilium Specific policies or the L7 capabilities?

@lieberlois thanks for the input here. Would you mind clarifying in what scenario Isovalent was planning L7 support? From our side, we currently have support for [hubble relay with self-managed...

@lieberlois sorry for the confusion 😆. I was meaning, did they say specifically [Azure CNI Powered by Cilum](https://learn.microsoft.com/en-us/azure/aks/azure-cni-powered-by-cilium), The [enterprise marketplace offering](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/isovalentinc1662143158090.isovalent-cilium-enterprise?tab=overview) they have, or the OSS Cilium support?

@lieberlois thanks for the clarification. As of right now, we're not on L7 yet as we've had more requests (though L7 is highly requested as well) for FQDN and will...

> What exactly are you referring to then? Layer 7 network policies leverage FQDNs so what is missing then? Good question. Cilium L7 policies and FQDN policies both work at...

@lieberlois aaahhh gotcha ok and I'm referring to L7 as application operations traffic. PUTs, GETs, etc.