Azure Ad connect sync for On-Prem and Azure.

There doesn't appear to be anything attached to your question.

No attachment

My Bad, Please find the error attached.

A top level domain error usually means the account doesn't have a valid domain that can be synced to O365. Any internal-only domain would have this issue, cmsich as dot-local (popular because of SBS, for example.)

You have to change the account UPN to sync those and that can have a user impact so it should be planned and communicated.

How can i effect that change?

Create a UPN suffix that matches an authenticated domain in Azure AD.  Then you can use IDFix to change accounts en-masse.  I'd recommend doing a test account or two and communicating the change to users who may be impacted.

Soinds line you skipped one or more prerequisites so the script is failing.

https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-prerequisites

when i run IdFix i get new less errors,  under ATTRIBUTE i see Proxy Addresses. find below in the screenshot.
0022.PNG

It's increasingly evident to me that you haven't read the documentation for AADConnect and may also not have the experience required for a successful deployment.  You may want to consider hiring a consultant on this project to ensure you have a clean and successful launch.  Forums are good for single one-off "I'm lost" type of sticking points, but are not well suited to advanced in-depth project management that seems to be required here.  Many experts make their living by providing such services and are not inclined to give away such services for free here.

@Mitul Prajapati, Thanks for your help. I have added 300 users to my Azure AD account and its working perfectly. @Cliff Galiher, if you don't have a solution, i advise you keep your coments yo yourself.

I am glad to hear that your problem is fixed now.