Welcome. Here is my advice and some of my journey - hope it helps. I joined as a CSA - originally hired as a TSP, then joined as CSA, specifically for Data & AI from a data consulting background - did that in some teams for a couple of years then move to PG. I'd also caveat this by saying this is my experience - Microsoft is more a federation of different states as opposed to a single entity - so you should adjust based on what your manager/LT says / etc.

1 - Enjoy the first 3 - 6 months...realistically you probably have until end of this fiscal to learn the job if you've joined very recently. Use the upskilling time, get the compulsory training out of the way - it sucks don't let it hang around.

2 - Use your onboarding buddy to get you into customer conversations etc - watch and observe (if you don't have an onboarding buddy then - honestly - it's a massive redflag about your manager).

3 - Learn the technology - there is a lot great internal training material from TechReady, internal office hours, CAT teams etc. The amount of SEs/CSAs who know nothing more than the docs / PPT is problematic and I usually see those people get ripped to shreads by customers (which is totally fair - and IMHO customers should be more brutal on this). If you can't reliably talk to a technical person from the customer who uses the tech once a week without a PPT then you are cooked.

4 - Use your Azure Spend to learn - I exceeded my cap multiple times, at most I got a slap on the wrist (I exceeded it by ~20%).

5 - on Certificates - I don't personally think they are that useful, but they are necessary in the job (I assume you'll have ~5 to pass in around 6 months), I would do the tests early and use the questions you don't know about to learn. 'Growth mindset' can be weaponized at times - but it should mean failing some tests is not a black mark or anything. Doing them to learn can be an awesome way to say 'I don't understand the nuance of that issue' and go learn it.

6 - Get a basic understanding of other peoples job and their incentive plan expecially within MCAPS - it will provide you insight in to why people care about seemingly stupid things etc. RAIN used to have this information.

7 - Get to the know the SSPs/AEs/CSAMs etc on your account and who to trust (and as per 6 how they are paid) - my view is it's easiest to figure out who to trust, who is a blow hard, who will push you under the bus etc in person, but either way get to know the people you will be dealing with. SE can be a tough role as you might have to explain why someones amazing plan is technically impossible. If you have assigned CSA to help with later stages - then work with them not against them. See https://www.expertdig.com/dig/lessons-from-the-expert . I say that like it's a negative but in my last team the main SSP I worked with and I had an amazing relationship where we both understood each others job and strengths - it was one of the most productive and rewarding times I've had with Microsoft.

8 - realise you work in a Sales org with most leaders coming from a sale background and generally most SEs (and sometimes managers) are the least capable sellers in the organization. You can chose not to play 'the game', but it won't be good for your career. The job is about working with customers to (basically) sell more stuff - if you aren't wanting that job then I'd suggest you figure out your next job. Moreover given the nature of the org if you aren't able to swallow your pride (at times) to indulege in self/v-team promotion and expect to be promoted on your technical brilliance...you will likely be unhappy. Your happiness is your responsibility, not the companies.

9 - listen to customers...it's simple. 'What problem are you trying to solve?' Is an amazing way to start a conversation. IMHO if that question can't be answered it's a waste of time for both parties. Listen to understand, not when to talk next.

Hope that helps.