GUID vs Identity on a table performance
There are certain situations where a GUID might be needed, but in general I'd advise against it.   The main reason is that GUIDs are, by their nature, random.  So using them as an identity column essentially means you're storing your rows randomly.  With a typical incremental primary key, the data is sequential.   Table scans are usually more efficient, etc.

In the end, there are tradeoffs with either situation.   Brent Ozar has an older article on the topic:  https://www.brentozar.com/archive/2014/08/generating-identities/