topic Re: Not able to register or sign in to Partner Academy in Training offerings

Not able to register or sign in to Partner Academy

NeonLight — Thu, 11 Jul 2024 08:19:18 GMT

My company has become a Databricks Partner. My colleagues have successfully registered for Databricks Partner Academy, but I can't get in.

I have followed the following steps for Partner Academy Registration till step 5:

Open https://partner-academy.databricks.com/learn in your web browser.
Click on Sign In.
Click Login or Register.
Enter your company email address. You are prompted to enter an OTP to verify your identity.
Enroll a passkey. (Optional)
Fill in all required fields and click on Register.
You are logged into Partner Academy after accepting the terms and conditions.

After step 5, I encounter a window prompting me to "Confirm & Reset password." Since I have never registered for the Partner Academy before, I am unsure which password to enter. There is no option to select "forgot password," and the password I use for the customer-academy portal does not work here.
I have attached a screenshot of the "Confirm & Reset password" window that appears after step 5.

I have submitted a ticket to Training Team. But last time I didn't receive any reply on my ticket. So, I'm not sure about what to do.

Thanks,
Neon

Re: Not able to register or sign in to Partner Academy

NeonLight — Thu, 11 Jul 2024 19:06:08 GMT

My issue has been resolved.

Re: Not able to register or sign in to Partner Academy

vsuday14 — Fri, 12 Jul 2024 02:53:57 GMT

Hi NeonLight/support team,

I am facing the same issue of step5 to change the password, how to reach to Support Team to resolve the issue.

Thanks
Vsuday

Re: Not able to register or sign in to Partner Academy

NeonLight — Fri, 12 Jul 2024 06:24:21 GMT

Hi Vsuday,

I submitted a ticket at: https: https://help.databricks.com/s/contact-us?ReqType=training. If you don't receive a response, reply to the same email. They usually get back within 24 hours.

I received a reply and tried signing in again, and it worked. It seems they fixed the issue on the backend.

Thanks,
Neon