The marketing pushes "one platform for SASE, SD-WAN, security." In practice, this means a sprawling, interlinked object model where a trivial change requires navigating five different policy contexts. The promised versatility just means everything is interdependent.
Example: Want to apply a simple QoS rule for a video conferencing app? Not a simple classifier and policy. You're defining an application match profile, a traffic profile, a forwarding profile, and binding them in a service chain—all before touching the actual site policy. The CLI and GUI both reflect this.
```xml
TEAMS-VIDEO
1
microsoft-teams
```
Then you need the traffic profile, the service profile, the service instance... for what should be a 5-line stanza on a traditional platform. The complexity tax is real. It feels like building a house to hang a picture. Anyone else finding the operational overhead negates the feature integration?
Ship it right