Service Fabric

Do you have an idea, suggestion, or feedback based on your experience with Azure Service Fabric? We would love to hear from you.

Please take a few minutes to submit your feedback in one of the forums available on the right or vote up an idea submitted by another Azure Service Fabric customer. All the feedback shared in these forums are being monitored and reviewed by the Microsoft Azure Service Fabric team.

Please remember this forum is for Azure Service Fabric, and if you have feedback on other Microsoft products, services or platforms, please submit your feedback in the appropriate forum (found on the right hand side).

Thanks for your feedback – we look forward to improving your satisfaction with Azure Service Fabric

How can we improve Microsoft Azure Service Fabric?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Open Source Service Fabric

    Following the pattern of many other development resources from Microsoft, it would be amazing to see Service Fabric open sourced, so that others can modify, improve and view it.

    329 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Lower end pricing to get familiar with the framework in Azure

    I was really hoping there would be a low tier option to Develop on for those of us with limited infrastructure. I went to spin up a cluster and start playing today, but the minimum was 5 A1 VMs which would be over $200. Any chance we could get a lower end tier or tone it down to 1 VM to get familiar with the platform with the ability to scale it out?

    256 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Improve deployment speed for ASP.NET 5 projects

    I noticed ASP.NET 5 applications takes a long time to deploy and debug. About 1-2 minutes on my computer on a brand new project. This should be better optimized to load faster

    196 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Totally agree. Waiting for a whole new deployment just to see some quick CSS changes is a huge pain. We’ve introduced a new deployment mode in Visual Studio that let’s you edit projects in place and see updates live as you make them, similar to what you’re used to with ASP.NET Core development outside of Service Fabric. Read more about it on the Service Fabric blog: https://blogs.msdn.microsoft.com/azureservicefabric/2017/04/17/speed-up-service-fabric-development-with-the-new-refresh-application-debug-mode-2/

  4. Dependency Injection in services and actors

    As the heading states. Support DI frameworks in the programming model.

    160 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. End-to-end tutorial from develop to publish, upgrade and monitoring of Fabric services/actors

    The framework looks fantastic, and so documentation that reveals how to do everything properly for an example project that is moderately complex would be appreciated.

    Documentation that explains how to integrate with legacy apps (to slowly migrate partial things to existing apps) as well would be really interesting.

    Basically a few of these big tutorials I think would help explain how all the parts work and the best practices on using Fabric.

    It's a huge undertaking I am sure, but that would be really good to see.

    155 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Windows 7 support

    Add windows 7 support! Because processors i7 are very good and a lot of PCs/Laptops are sold with Win7 Pro already, there are more then a few developers with Win 7 Pro on their dev machines and they are not going to have any real need for hardware/os upgrade any time soon. In our company we develop for Azure for three years now and continue to build upon the platform. It will be great loss of time if every developer has to switch OS now. I suggest that this will not be an isolated case and the problem will be…

    125 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. clear migration path for Web/Worker CloudService roles

    Those of us with existing investments in CloudServices (both Web & Worker Roles) need a clear migration path to Microservices. Especially early on in preview to prep our projects for this upgrade path.

    97 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Provide more control over actor lifetime

    There are scenarios where I can be absolutely certain that a particular actor will never be used again. While I realize that they will be garbage collected from memory after a period of inactivity, I would actually like to remove them from the system altogether. It would be great to have a way to tell the platform which actors can be cleaned up.

    80 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 53 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. enable publishing to azure

    We want to publish this to Azure! :)

    48 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow Inheritance for IActor Interfaces

    Allow Inheritance for IActor Interfaces. So I'm able to make for Example:

    ITestableActor : IActor, which has a Reset Function.

    ISpezificActor : ITestableActor

    ISpezificActor actor = ActorProxy.Create<ISpezificActor>(...);

    Cleanup(actor);

    public void Cleanup(ITestableActor cleanActor)
    {
    cleanActor.Reset();
    }

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Service Fabric

Feedback and Knowledge Base