{"id":13699,"date":"2023-05-03T08:30:46","date_gmt":"2023-05-03T15:30:46","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=13699"},"modified":"2023-05-02T11:23:35","modified_gmt":"2023-05-02T18:23:35","slug":"microsoft-graph-early-adopter-recognition-program","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-early-adopter-recognition-program\/","title":{"rendered":"Announcing the Microsoft Graph Early Adopter recognition program"},"content":{"rendered":"

Show off your Microsoft Graph tools and SDKs early adopter status with a digital badge<\/strong> certifying your hard work and curiosity!<\/p>\n

Your feedback is critical to us<\/h2>\n

We strive to build products that delight and empower you to achieve more. Hearing from you early and often about what\u2019s working and where we could do better plays a critical role in our development process. Your feedback improves Microsoft products benefiting customers and ecosystem developers \u2013 thank you.<\/p>\n

In collaboration with the Microsoft 365 & Power Platform community<\/a>, we\u2019re launching the Microsoft Graph Early Adopter recognition program<\/strong>, where we award everyone who provided us with valuable feedback with a digital badge as our way of recognizing your contributions.<\/p>\n

\"\"<\/p>\n

This badge will be visible along with your other digital badges for Microsoft certifications. You can share it publicly as proof of your curiosity, expertise, and passion to improve our products.<\/p>\n

How to get awarded<\/h2>\n

When using Microsoft Graph tools and SDKs, and you notice something that isn\u2019t working as expected, if you have an idea for improvement, or you come across something that delights you\u2014let us know. Our product managers review all feedback and pull requests, and if it meets the criteria, you\u2019ll get awarded with the digital early adopter badge. The more constructive and detailed, the better. It can be a bug report, a feature request, a pull request, or a story on how our products help you in your work but make it detailed.<\/p>\n

We\u2019re looking forward to learning from you and appreciate your help!<\/p>\n

FAQ<\/h2>\n

What type of feedback qualifies for a badge?<\/h3>\n

We\u2019re looking for meaningful product feedback. We consider feedback meaningful when it describes what you\u2019re trying to achieve (scenario), how you’re using our products and what\u2019s (not) working. Meaningful feedback can refer to an existing feature or something that we don\u2019t support (yet). For example:<\/p>\n

\u274c \u201cFluent APIs are cool!\u201d (Why? What’s the benefit?)<\/p>\n

\u2705 \u201cUsing fluent APIs we get design-time feedback for calling Microsoft Graph and can catch errors earlier.\u201d<\/p>\n

How to submit feedback?<\/h3>\n

Submit your feedback by creating an issue on the GitHub repository of the corresponding Microsoft Graph product (see the list below).<\/p>\n

Which Microsoft Graph products participate in the program?<\/h3>\n

We\u2019re starting with the following Microsoft Graph tools and SDKs:<\/p>\n