Great video for me starting out.  Thanks.

Did you bounce the call through the Easy API just because or could you have just issued it directly from the device?  I always thought the less hops the better.

{edit} After watching all the way to the end, I see that you are centralizing the Twitter API call in one place, and that makes sense in some cases (like if Twitter changes their API), but I'd still like to know if you could have made the call directly from the device.

{edit-edit} Never mind, I see that the functionality is coming from the

azureMobile.user.getIdentity()

function, which we didn't write and will clearly work against multiple IDP's.  Senior moment.  Sorry.