now thats some old topic but it seems this issue is still fresh. I have just saw at the connect post that this same behaviour of identity happens on SQL 2014.

https://connect.microsoft.com/SQLServer/feedback/details/739013/alwayson-failover-results-in-reseed-of-identity

does anyone have information if this "problem" is solved in any of recent Service Packs or updates? or even if SQL2016 has it?

I really dont want to put a startup proc in all my instances... sp_FixSeeds2012 🙁