Content Expiration Date Bug? RRS feed

  • Question

  • I have observed an issue pertaining to the AD RMS policy “Content Expiration”. Even though we specified a date the Exchange Online kept sending a year of “9999” in the sync response. It was only once the date had passed that it send down a valid date which would always be the current day. According to the protocol documentation (MS-ASRM) the server should only send the 9999 year when no date had been specified (which doesn’t seem possible via the Azure Mgmt portal).

    <u5:p>Because of this the client we are developing cannot know if the content has expired without internet connection. It seems odd that this would be the design so i'm wondering if there is a bug or anything I can try on my end. </u5:p>

    *I've tried this with our paid account and made a trial account completely separate to verify the issue exists there as well.

    Friday, December 5, 2014 11:47 PM