Generally you shouldn't put duplicate locations into a route request. In many cases it won't matter, but in some situations it could become an unrouteable request. The routing service takes your locations and snaps them to the nearest logical road, within a few limitations. It will often take the last snapped coordinate into consideration. This could result in a situation where your duplicate location is snapped to a point behind where the first coordinate was, and would require a U-turn, but if the road is a one-way road, may not be an option. Sure a much longer route could potentially be calculated but the routing service likely notices that something isn't right and stops.
That said, there is a newer route service that will likely make it to Azure Maps in the next year or so that would likely handle this situation much better.