Remember2

 You can submit messages to a queue or topic for delayed processing; for example, to schedule a job to become available for processing by a system at a certain time. This capability realizes a reliable distributed time-based scheduler.

Scheduled messages do not materialize in the queue until the defined enqueue time. Before that time, scheduled messages can be canceled. Cancellation deletes the message.

You can schedule messages either by setting the ScheduledEnqueueTimeUtc property when sending a message through the regular send path, or explicitly with the ScheduleMessageAsync API. The latter immediately returns the scheduled message's SequenceNumber, which you can later use to cancel the scheduled message if needed. Scheduled messages and their sequence numbers can also be discovered using message browsing.

=================================================================================

Get a specified secret from a given key vault.

The GET operation is applicable to any secret stored in Azure Key Vault. This operation requires the secrets/get permission

GET {vaultBaseUrl}/secrets/{secret-name}/{secret-version}?api-version=7.1

===================================================================================

Soft delete for blobs protects your data from being accidentally or erroneously modified or deleted. When soft delete for blobs is enabled for a storage account, blobs, blob versions, and snapshots in that storage account may be recovered after they are deleted, within a retention period that you specify.

If there is a possibility that your data may accidentally be modified or deleted by an application or another storage account user, Microsoft recommends turning on soft delete

==================================================================================

To move the data from on premises to azure which resides in a Mongo DB database, we would need to move it to a Cosmos DB account. You can use Azure Database Migration Service to perform an online (minimal downtime) migration of databases from an on-premises or cloud instance of MongoDB to Azure Cosmos DB's API for MongoDB.

==============================================================================

#!/bin/bash

# Reference: az cosmosdb | https://docs.microsoft.com/cli/azure/cosmosdb

# --------------------------------------------------

#

# Create a Table API table

#

#

# Variables for Cassandra API resources

uniqueId=$RANDOM

resourceGroupName="Group-$uniqueId"

location='westus2'

accountName="cosmos-$uniqueId" #needs to be lower case

tableName='table1'

# Create a resource group

az group create -n $resourceGroupName -l $location

# Create a Cosmos account for Table API

az cosmosdb create \

    -n $accountName \

    -g $resourceGroupName \

    --capabilities EnableTable \

    --default-consistency-level Eventual \

    --locations regionName='West US 2' failoverPriority=0 isZoneRedundant=False \

    --locations regionName='East US 2' failoverPriority=1 isZoneRedundant=False

# Create a Table API Table

az cosmosdb table create \

    -a $accountName \

    -g $resourceGroupName \

    -n $tableName \

    --throughput 400