Learning Objectives
- Configure security policies to classify, protect, and manage data
- Configure data retention for storage and databases
- Set up Azure SQL security features and auditing
- Learn how to configure storage account security and access
- Learn how to secure HDInsight clusters
- Configure Cosmos DB security
- Configure Data Lake security
- Learn good design features of an Azure application
- See how Azure App Services can secure your app
- See how a governance policy can help formalize security requirements
Intended Audience
- People preparing for Microsoft’s AZ-500 exam
- System administrators
- App developers
Prerequisites
- Experience with Microsoft Azure
- Experience with Office 365
- Basic knowledge of computer security principles
- Basic networking knowledge
Azure Data Explorer, as a big data service, can potentially produce a lot of data that will become irrelevant after a short period of time. By setting up data retention policies, you can reduce the likelihood of cost overruns and storing irrelevant data. There are two main properties to the Data Explorer retention policy. The soft delete period is a time span for which it is guaranteed data will be kept available to query and measure since the time it was ingested. This defaults to 100 years. When altering the soft delete period of a table or database, the new value applies to both existing and new data. A soft delete period of zero can be set as part of table-level retention. This is especially useful if data is going to be transformed, and is only present in a staging table temporarily. The soft delete period guarantees how long the data will be available for, but not necessarily when it will be deleted. As the data is not necessarily deleted immediately at the end of the soft delete period, it can linger for some time. Recoverability is the other property of the retention policy object. This defaults to enabled, and the data will be recoverable for up to 14 days after deletion.
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.