Your SlideShare is downloading. ×
  • Like
How it's made - - AzureConf
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

How it's made - - AzureConf



Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Maarten
  • Demo:Show people around in ACS management portal and whos how easy it is to add another identity providerShow Visual Studio and how easy it is to add a federation identity provider in thereStress the fact that the app only know about ONE identity, and that’s the one from ACS. The others are transformed at the ACS level.Show the incoming claims in the accountcontroller
  • Demo:Web.config contains multiple audiences:      <audienceUris>        <add value="http://localhost:1196/" />        <add value="http://localhost:81/" />        <add value="" />      </audienceUris>Realmis the same for every audience, ACS uses the audience to do the home realmdiscoveryDemonstrate a login on prod and one on dev
  • Demo:Demonstrate login via RealDolmen ADFSAgain, demonstrate the audience URI’s and how this should in theory never workShow the dynamic configuration happening on login:                if (TenantContext.Tenant != null)                 {                     signInRequestMessage.Realm = TenantContext.Tenant.Realm;                     var allowedAudienceUris =                         FederatedAuthentication.ServiceConfiguration.AudienceRestriction.AllowedAudienceUris;                     if (!allowedAudienceUris.Contains(new Uri(TenantContext.Tenant.Realm)))                     {                         allowedAudienceUris.Add(new Uri(TenantContext.Tenant.Realm));                     }                 }


  • 1. Over 60 community-led Windows Azure training events worldwide!
  • 2. self promotion: Pro NuGet -
  • 3. NuGet?MyGet?
  • 4. How westarted
  • 5. What wedid notknow…
  • 6. Our firstarchitecture
  • 7. Or not?Speed of light! USA was slow!Sync issues, downtime, …Seems not every ISP follows DNS standards
  • 8. • Syncing data kept being slow• Populating cache was a nightmare• CDN kept having issues• Of 3 instances, only 1 was being used with enoughload (~60%)
  • 9. Our secondarchitecture
  • 10. Windows AzureAccess Control Service
  • 11. production*.customer.myget.orgother domain nameslocalhost:1196 myget-staging.cloudapp.netdevelopmentWindows Azure Access Control Service
  • 12.
  • 13. Tough timesLearning moments
  • 14. Full story at
  • 15. Full story at
  • 16. Full story at
  • 17. Full story at
  • 18.
  • 19. Bonus tip
  • 20. this is why we built username/passwordregistration, seems a lot of people prefer typinginstead of one clickwe must keep investing in Build Servicesfeed discovery is more popular than we imaginedfrom zero reactions on our blog and Twitterthe technical fear we had about “download as ZIP”consuming too much server resources? That thingdoesn’t show up in our stats, that’s how successfulit is…
  • 21. Conclusion
  • 22. Thank you!
  • 23.
  • 24.