I'm having a heck of a time trying to connect our local network with azure for AD. Why are the VPN settings so inflexible? IPSEC vpn's have been around forever. The cradlepoint mbr1200's i have deployed don't support IKE2 so i tried to setup a policy-based
ipsec vpn which uses ike1. If it's policy based where do you set the policy settings? Why are so many things that are so simple on-prem so complicated in azure? I convinced my client to move to the cloud and now i'm going to have to tell him to wait until
i can do in the cloud what i can do onprem. It's really a shame. I'm amazed that msft released the new portal before it can do what the old one can do. I've spent the last week reading all the documentation i could find and all of it is for the classic portal
or Powershell. I would just use the classic interface but i can't move resources to the new portal when it's fully baked. Very frustrating! I've been working with windows server/clients for 10 years. Surely i'm not the only one with problems.
Scott