---
title: "Engineering Feedback Frequently Asked Questions (F.A.Q.)"
source: Microsoft Code-With Engineering Playbook
source_url: https://github.com/microsoft/code-with-engineering-playbook
licence: CC-BY-4.0
domain: engineering
subdomain: microsoft-code-with-playbook
date_added: 2026-04-25
---

# Engineering Feedback Frequently Asked Questions (F.A.Q.)

The questions below are common questions related to the feedback process. The answers are intended to help both Microsoft employees and customers.

## When Should I Submit Feedback vs. Creating an Issue on GitHub, UserVoice, or Sending an Email Directly to a Microsoft Employee?

It is appropriate to do both. As a customer or Microsoft employee, you are empowered to create an issue or submit feedback via the medium appropriate for service.

In addition to an issue on GitHub, feedback on UserVoice, or a personal email, Microsoft employees in [CSE](../ISE.md) should submit feedback via CSE Feedback.  In doing so, please reference the GitHub issue, UserVoice feedback, or email by including a link to the item or attaching the email.

Submitting to ISE Feedback allows the ISE Feedback team to coalesce feedback across a wide range of sources, and thus create a unified case to submit to the appropriate Azure engineering team(s).

## How can a Customer Track the Status of a Specific Feedback Item?

At this time, customers are not able to directly track the status of feedback submitted via ISE Feedback.  The ISE Feedback process is internal to Microsoft, and as such, available only to Microsoft employees.  Customers may request an update from their ISE engineering partner or Microsoft account representative(s).

Customers can also submit their feedback directly via GitHub or UserVoice (as appropriate for the specific service), and inform their ISE engineering partner.  The ISE engineer should submit the feedback via the ISE Feedback process, and in doing so reference the previously created issue.  Customers can follow the GitHub or UserVoice item to be alerted on updates.

## How can a Microsoft Employee Track the Status of a Specific Feedback Item?

The easiest way for a Microsoft employee within ISE to track a specific feedback item is to [follow the feedback (a work item)](https://learn.microsoft.com/azure/devops/boards/work-items/follow-work-items?view=azure-devops) in Azure DevOps.

## As a Microsoft Employee Within ISE, if I Submit a Feedback and Move to Another Dev Crew Engagement, how Would my Customer get an Update on that Feedback?

If the feedback is also submitted via GitHub or UserVoice, the customer may elect to follow that item for publicly available updates.  The customer may also contact their Microsoft account representative to request an update.

## As a Microsoft Employee Within ISE, what Should I Expect/Do After Submitting Feedback via ISE Feedback?

After submitting the feedback, it is recommended to [follow the feedback (a work item)](https://learn.microsoft.com/azure/devops/boards/work-items/follow-work-items?view=azure-devops) in Azure DevOps.  If you have configured Azure DevOps notifications to send an email on work item updates, you will receive an email when the feedback is updated.

If more information about the feedback is needed, a member of the ISE Feedback team will contact you to gather more information.

## How/When are Feedback Aggregated?

Members of the ISE Feedback team will make a best effort to triage and review new ISE Feedback items within two weeks of the original submission date.

If there is similarity across multiple feedback items, a member of the ISE Feedback team may decide to create a new feedback item which is an aggregate of similar items.  This is done to aid in the creation of a unified feedback item to present to the appropriate Microsoft engineering team.

On a monthly basis, the ISE Feedback team will review all feedback and generate a report consisting of the highest priority feedback.  The report is presented to appropriate ISE and Microsoft leadership teams.
