{"push_id":2698522797,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"6f1580aaea6dcc066067f4bebf4ebd23ce8779c1","before":"f5bbf43ad9f2090e5ca537008390243bae76620d","commits":[{"sha":"d40ec28ff8de399318b78894c28f8da603b5bddd","author":{"name":"Steve Whitcher","email":"9ce5770b3bb4b2a1d59be2d97e34379cd192299f@whitcher.org"},"message":"Updated example scenario for DEM\n\nThe old wording implies that a DEM account is created and the supervisor somehow 'added to' that account, giving the supervisor DEM rights.  The way it actually works is a new DEM account is created, and the supervisor can use that account to enroll devices.  It's not like adding an existing user to a group to grant the user DEM permissions, it's a second account for that user which is used only for DEM purposes.","distinct":true,"url":"https://api.github.com/repos/MicrosoftDocs/IntuneDocs/commits/d40ec28ff8de399318b78894c28f8da603b5bddd"},{"sha":"6f1580aaea6dcc066067f4bebf4ebd23ce8779c1","author":{"name":"Erik Kjerland","email":"d84a568747ef269fdaaa50a949c6d1cc5a82668d@microsoft.com"},"message":"Merge pull request #1213 from NeighborGeek/patch-1\n\nUpdated example scenario for DEM","distinct":true,"url":"https://api.github.com/repos/MicrosoftDocs/IntuneDocs/commits/6f1580aaea6dcc066067f4bebf4ebd23ce8779c1"}]}
{"actor":{"display_login":"ErikjeMS"}}