You can create a DDL trigger to keep track of it or prevent this to happen. See the rollback statement below.
CREATE TRIGGER safety
ON DATABASE
FOR DROP_TABLE
AS
PRINT 'Save change on a log'
SELECT EVENTDATA().value('(/EVENT_INSTANCE/TSQLCommand/CommandText)[1]','nvarchar(max)')
ROLLBACK;
Inside the trigger you can run below statement to capture the user that is executing the action.
SET @bd = 'UserName: ' + UPPER(SUSER_NAME())
On this article you will find how to log schema changes with triggers.
In you still want too use Azure SQL Auditing you will find on this article how to track schema changes.