If you, like us, have a rather large collection of Azure Active Directory objects (and by large I mean in excess of 100 distinct users and groups total) you might notice that in using this SMO as the data source for a Picker Control that doing an empty search only returns the first 100 objects from AAD and that doing a specific search for an object outside of the first 100 objects will return nothing.

The reason this happens is due to a limitation in how the AAD User SmartObject interfaces with Azure Active Directory itself. A better choice of data source here is the UMUser SMO using the Get Users method. While doing a blank search will only return the first 100 objects, a specific search of any item will return that item (assuming iit is in AAD) no matter where it falls in AAD.