Hello @Saurabh Shukla ,
I tested your experience and noticed similar behavior but I was able to fix it.
Of course, the target table needs to exist before the output can be created.
Notice, rights will be granted so you need enough rights to get the identity assigned:
You can see this in the ADX permissions:
Still, I got the same warning so I checked the output again (I also notice no output messages were created for that output).
For some reason, it tried to connect to another database within the same cluster. And the table name was not correctly spelled (it seems to be case sensitive).
Did I misconfigure it? Anyway, I'm not sure why these settings looked like that but after correcting it, and testing it again, now it works:
And the test messages arrived:
So please check all output settings again.
Or give that page a frown and tell about your experience so the Azure Portal team can take a look:
If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.