Creare un token SAS

PeopleSphere sta lanciando una promozione a tempo per gli iscritti alla newsletter. Hanno chiesto un modo per archiviare in modo sicuro i contenuti promozionali in Blob Storage e concedere l’accesso solo in orari specifici. Per farlo, puoi generare una Shared Access Signature (SAS) che limita l’accesso ai contenuti all’interno della finestra temporale definita. In questo modo solo il pubblico previsto potrà vedere la promozione al momento giusto.

Questo esercizio fa parte del corso

Implementare Azure Security per sviluppatori

Visualizza il corso

Esercizio pratico interattivo

Passa dalla teoria alla pratica con uno dei nostri esercizi interattivi

Inizia esercizio

Questo esercizio fa parte del corso

Implementare Azure Security per sviluppatori

IntermediárioNível de habilidade

4.7+

45 reviews

Inizia il corso gratis

In this chapter, you’ll first get hands-on with Microsoft Entra ID to manage users, groups, and roles in a secure, centralized way. Then, you’ll build a solid foundation in identity management, exploring how authentication, authorization, and service principals work together to control access. Finally, you’ll learn to use Shared Access Signatures to grant limited, time-bound access to storage without exposing sensitive credentials.

Exercise 1: Introduzione alla sicurezza in Azure Exercise 2: Panoramica di Microsoft Entra ID Exercise 3: Scegliere lo strumento di sicurezza giusto Exercise 4: Autenticazione e autorizzazione in Entra ID Exercise 5: Creare utenti in Entra ID Exercise 6: Accesso sicuro Exercise 7: Autenticazione vs. autorizzazione Exercise 8: Piattaforma di identità Microsoft Exercise 9: Application object vs service principal Exercise 10: Scenario di accesso solo app Exercise 11: Shared Access Signatures (SAS)Exercise 12: Scegliere la SAS giusta Exercise 13: Creare un token SAS

Esercizio in corso

Exercise 14: Pratiche SAS sicure vs. non sicure

In this chapter, you'll build a strong foundation in securing app settings and sensitive data using Azure App Configuration and Key Vault. You’ll explore how to manage configurations, enable feature flags, and safeguard settings using encryption, private endpoints, and managed identities. Moving into Key Vault, you’ll learn how it stores secrets, keys, and certificates, and how to apply authentication and authorization best practices. Finally, you'll examine advanced protections like Soft Delete and Purge Protection to ensure your critical data remains safe and recoverable.

Exercise 1: Azure App configuration Exercise 2: Deploying App Configuration Exercise 3: Storing settings in App Configuration Exercise 4: Classify feature management components Exercise 5: Getting started with Key vault Exercise 6: Classifying keys, secrets, and certificates Exercise 7: Retrieve Key Vault secrets in Logic App Exercise 8: Managing secrets in Key Vault Exercise 9: Advanced Key vault settings Exercise 10: Choosing the right authorization model Exercise 11: Soft delete & purge protection

In this part of the course, you’ll begin with Azure Managed Identities, seeing how they let applications access resources securely without managing credentials. You’ll then move into Microsoft Graph, where you’ll explore its unified API and practice queries in Graph Explorer. Finally, you’ll advance to techniques like pagination and batching to handle data more efficiently and build scalable integrations.

Exercise 1: Secure access with managed identities Exercise 2: Managed identities: system vs user assigned Exercise 3: Assigning UAMI for multiple resources Exercise 4: Introduction to Microsoft Graph Exercise 5: Classifying HTTP methods Exercise 6: Microsoft Graph explorer's quick tour Exercise 7: Exploring data with Graph explorer Exercise 8: Advanced usage of Microsoft Graph Exercise 9: Client-side pagination with $top Exercise 10: Match responses to requests