expose cloud service client from scheduler package


<!---@tfsbridge:{"tfsId":2310159}-->
Is this going to be published ?

- If it is, then we are already locking into a name right ?
- If it's not, are you planning on navigating into the guts of the azure module with the require ? If so, that's probably a bad idea and instead we should expose thsi with a "private" accessor as it is the typical pattern ?