Looking at the Azure Portal when configuring reply/redirect URLs for applications, it makes use of the replyUrlsWithType property of the application resource, available with v2.0 of the API. This property is undocumented.
How can we get support for this property, as it's seemingly the only way to create different types of reply/redirect URLs and will fill a large gap in support for different types of applications?
Implementing this would be a _huge_ enabler, as it is currently the canonical way to set the new redirect URIs for applications, given that MS Graph support is currently lagging behind here.





PATCH /myorganization/applications/0ee8ac26-20f5-4da4-abd8-4b504785782b?api-version=2.0
{"id":"0ee8ac26-20f5-4da4-abd8-4b504785782b","replyUrlsWithType":[{"type":"Web","url":"http://unittest.hashicorptest.com"},{"type":"Spa","url":"https://blah-spa"},{"type":"InstalledClient","url":"https://blahnative"}],"logoutUrl":null,"oauth2AllowImplicitFlow":false,"oauth2AllowIdTokenImplicitFlow":false}
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure.
Highly interested in this since its preventing anyone from using terraform to automate the creation & management of single paged AD applications that use the PKCE oauth2 flow.
@armleads-azure any updates?
Bump
@armleads-azure @ArcturusZhang Any updates on this?
Most helpful comment
Highly interested in this since its preventing anyone from using terraform to automate the creation & management of single paged AD applications that use the PKCE oauth2 flow.