Microsoft Entra Sign-in Logs
Ingest sign-in logs from Microsoft Entra ID
Integration Instructions
1. Create Storage Account
- Log into https://portal.azure.com
- Search for Storage Accounts
- Click create and provide the following options:
- Subscription: Choose a subscription for the storage account
- Resource Group: Any resource group can be selected
- Storage account name: Provide a name for the storage blob
- Region: Any region, US - West preferred
- Primary Service: Azure Blob Storage
- Performance: Standard
- Redundancy: Locally-redundant storage
- Logs are short-lived in these storage blobs, however you may choose Geo-redundant storage if you would like
- Review + Create > Create
2. Create Lifecycle Policy
We want to automatically expire logs after a certain period so that you aren’t paying for them after they’ve been ingested by Wirespeed. Wirespeed syncs logs every minute, but it’s common to set retention between 1-7 days. Wirespeed does not delete logs in your storage accounts after ingestion, which is why a lifecycle policy is used.
- Navigate to the Storage account that was created
- Select Data Management > Lifecycle management
- Click add a rule and provide the following options:
- Rule name: Provide a name for the rule
- Rule scope: Apply rule to all blobs in your storage account
- Blob type: Append blobs
- Blob subtype: Base blobs
- Click next
- If Base blobs were Last modified more than N days ago then Delete the blob
- Any value where N>=1 day is acceptable
3. Forward Logs
- Search for Sign-in Logs in the Azure Portal
- Provide a Diagnostic setting name
- Select Export Data Settings
- Select Add a diagnostic setting
- Logs > Categories > SignInLogs
- Destination details > Archive to a storage account
- Select storage account from Step 1
- Click Save
4. Integrate with Wirespeed
- Navigate to the storage account from Step 1
- Select Security + networking > Access keys
- Copy the connection string for key1
- Login to https://app.wirespeed.co
- Integrations > Add Integration > Microsoft Entra Sign-in Logs
- Provide your storage account name and connection string
Once complete, logs should show up under Events after ~10 minutes.
Cost
In the below calculations, we assume the average size of a sign-in event which is 5kb.
API Read Operations
We call the List and Create Container endpoint every minute, this endpoint has an associated cost of $0.05 per 10k requests (source). For the duration of a month, this totals** ~45k** API requests, totaling $.225/mo.
API Write Operations
This cost is dependent on Microsoft and how often they write to your storage account. If we assume they write once a minute at $0.0228 per 10k write requests (source), for ~45k monthly requests, we get a total of $.1026/mo.
Data Storage
With a lifecycle policy of 1 day and 1 million monthly sign-in events, 33k daily sign-in events would be stored at any given time. 33k events * 5KB/event = 165,000KB = .165GB
stored at any given time. With a storage rate of $0.15/GB (source) this would total** $.02475/mo**.
Data Egress
Azure charges for data leaving their network. While downloading from the account itself is free, you are charged for network egress at a rate of $.08/GB (source). Sign-in events are ~5kb per event, which totals** ~200k** sign-in events per GB. For an organization with 1 million monthly sign-in events, you can expect to pay $.40/mo.
If you observe otherwise in your environment please contact support.