HomeFor professionals
Show the work behind your skills.
Help us understand your experience, your contribution and the work you want to do next. Start with a concise introduction to your professional background.
Prepare a useful professional introduction
Keep your examples relevant to the work you want to do.
Your responsibilities
Explain what you owned, the decisions you made and who depended on your work.
Your project contribution
Describe the problem, your contribution and the result. Use examples you have permission to share.
Your skills and credentials
List the tools you use and relevant credentials, with dates and supporting details where available.
Your next step
Explain the work you want to do, your availability and where you want to develop.
Connect your experience to a role area
Choose the closest fit, then explain your own responsibilities and level of experience.
Business Central functional
Describe the finance or operations processes you supported in Business Central, your role in setup or testing, and the users you worked with.
Business Central development
Explain the AL extensions, integrations or upgrades you contributed to, including testing, version control and ongoing maintenance.
Fabric and Power BI
Summarise a data or reporting project: preparation, modelling, DAX, visualisation and the decisions the reporting supported.
Azure and security
Describe the Azure services, identity controls or monitoring you worked with and the operational responsibilities you held.
Microsoft 365 and automation
Explain your Microsoft 365 administration, collaboration or Power Platform work, with examples of the workflows you improved.
Copilot and AI agents
Describe an AI use case, the knowledge or tools involved, how you evaluated results and the safeguards you helped apply.
Start with a clear introduction
Share enough to begin the discussion. Do not send confidential client data, credentials or private project materials.
Describe your current role, technology experience and the work you are seeking.
Prepare brief project summaries and credentials you are permitted to share.
Confirm relevant options and any further information needed with INFOC.
Turn a project into a clear professional story
A useful portfolio explains your judgement as well as the finished output. One relevant, well-explained example can say more than a long list of tools.
Describe the business task, the users and the starting problem. For a Power BI example, explain who needed the report and which decision it supported. State whether the work was a personal lab, academic project or professional assignment.
Explain what you personally designed, configured, built or tested, and what was already provided. Name the tools that mattered and the constraints you worked within. Make team contributions clear so the reader can assess your own experience.
Describe a test or reconciliation and an issue you found. Explain what you changed and how you knew the correction worked. For an automation, include an exception; for a report, validate a measure; for an extension, show an invalid-input test.
Close with the outcome, limitations and one improvement you would make. Include only material you are permitted to share. A synthetic example or redacted explanation can demonstrate your thinking without disclosing a customer dataset or internal system.
Choose evidence that fits your Microsoft role
Your sample should help another person understand the responsibility you are ready to discuss.
Functional and business applications
Prepare a process map, configuration summary and a small test record. Explain the finance or operational requirement, how the standard process addresses it and which decisions belong to the business owner.
Development, data and AI
Use a small code sample, model, report or agent evaluation with a readable explanation. Show inputs, expected outputs, failure cases and your own contribution. Explain permissions and data boundaries where they affect the design.
Cloud, workplace and operations
Prepare an architecture sketch, access model or operational runbook. Walk through a routine task and an incident scenario. Explain the monitoring signals, recovery checks and escalation decisions you would use.
Preparing your introduction
You do not need to have the same background as every other professional. You do need to describe yours clearly.
What if I am a student, fresher or changing careers?
State your starting point and target role directly. Use a learning project, lab or transferable experience to show how you solve problems and explain your work. Label practice as practice. If you need a stronger technical foundation before pursuing a role, explore the Academy learning paths alongside your professional introduction.
What if I have experience but no recent certification?
Lead with relevant work: the responsibilities you owned, the technology you used and a permitted example of the result. Include credentials accurately where you have them. Explain how you keep your knowledge current and identify any areas where you would need additional preparation for the target role.
What should my first message include?
Send a short professional summary, your Microsoft technology focus and the responsibility you want next. Add your location, work preferences and availability where relevant. Link only to material you are authorised to share. An introduction starts a conversation; it is not an application to an advertised vacancy unless a specific vacancy is identified.
Discuss your professional background
Share a short introduction, your areas of experience and your preferred next step. An enquiry is not a placement guarantee.
