I found I was getting the error "The table %s could not be found" when using an Azure database and the Report Option "Verify Stored Procedures on First Refresh" was on.
Turning this off and the error no longer occurred. This did not occur with non-Azure databases.
As Scott Pearce mentioned - it's a pain that Crystal Reports, version for Visual Studio simply cannot see Azure stored procs in when setting the datasource location in the designer. The work-around is to copy the database to a non-Azure SQL server and build the report that way - provided you actually have that level of access to the Azure database.