andaryjo

@cmdrootaccess Thanks, this works!

I like the idea of introducing separate fields for a mode's name and it's machine-readable type. However, it even might make sense to decouple the `product` from the `line`, because:...

Going to leave this here in case anyone stumbles over the same problem. Not sure whether that's right, but likely there is no such alias because virtual network links aren't...

You should deploy a policy with a custom policy definition then. Seemingly the built-in policy works as advertised, even though it breaks some Azure built-in functionality. Resources should not be...

As far as I know, no, policies apply to all users and principals.

> Besides the endpoint URL, the HTTP Content-Type header for requests seems to be a relevant parameter (or I just haven't found one yet that works universally). That's my experience...

Another thought: Most TRIAS APIs require authorization and the implementation is proprietary. Some providers use a `RequestorRef` XML tag, some use a header and some require you to include an...

@kiliankoe Thanks for the info, I updated my post. ☺️

@iLazlow The TRIAS documentation does not mention JSON at all. Is this maybe something specific to a single provider?

> For DM Request as example you can use the parameter outputFormat=JSON e.g: {APIBase}/XML_DM_REQUEST?outputFormat=JSON&coordOutputFormat=WGS84[dd.ddddd]&mode=direct&name_dm=de:8212:6&type_dm=stop Unfortunately that's not TRIAS. While I've seen many providers build their TRIAS interface on top of...