![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 7.000000000000001%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESU%3C/text%3E%3C/svg%3E)
1,934 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 56.00000000000001%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
App Services are for web applications only. Depending on your solution you could host an API as an app service for your Windows application. The Windows Application itself cannot be hosted as an app service. If your solution is required to be a Windows Application, you could try hosting it as an Azure Virtual Machine and use a remote desktop to connect to the VM. However, if you have the freedom to migrate the solution, you could consider migrating the frontend part to Blazor. In the long run, and of course, depending on the number of users for your application, this can be more cost-effective.
