• Update:

    We had a live meeting session with microsoft support where they have debugged this behavior. There is no resolution yet, and might be a bug on their side.