Example 1 and Example 3 have issues with the destination, which is the same for both examples (12.61083,56.03292). This is most likely due to incorrect one-way restrictions. When you reverse the coordinates, you get a route because it is able to navigate in that direction. You are able to get a route in the Route Directions API because it considers pedestrian connectivity to the destination, which ignores the road restriction issue. However, the route matrix only uses drivable routes and is not able to snap. I will create a bug to get this fixed in the route matrix.
Example 2 also has issues routing to the destination. In this case, it seems to be missing map data, which prevents the destination from snapping to the closest routable road. As a result, you also don't get a route when you reverse it. It is not due to a ferry connection. I will create a bug for this as well to investigate and get the map updated. I am able to get a route for this example using the Route preview. Could you please give it a try again? I can share the request body if you need.
The matrix should be able to route to/from the routable geocoded coordinates. These appear to be one-off issues with the map data. If you are blocked by these issues, I recommend moving these points to the nearest road for the meantime so you can get the route. If you have more examples of NO_ROUTE_FOUND, please share them with us. I recommend using the latest Route public preview, which resolves most of these issues, and we currently plan to have this service in GA this quarter. You can always reach out to us through Azure support.