Azure新手求助：如何自动迁移Office365邮件附件至Azure VM并执行测试

Hey there! I totally get the pain of manually setting up a Logic App for every subscriber—let's fix that with scalable, automated approaches that eliminate repetitive work. Here are two solid strategies tailored to your scenario:

1. Single Logic App + Centralized Subscriber Management (Polling-Based) #

This approach uses one Logic App that pulls from a centralized list of subscribers, so you only need to update the list instead of creating new apps.

• Step 1: Store subscriber data centrally
  Set up an Azure Storage Table or Azure SQL Database to keep track of all your subscribers. Each entry should include:

  • Subscriber's Office 365 email address
  • Target Azure VM details (e.g., VM name, resource group, test script path)
  • Optional: A flag to enable/disable the subscriber temporarily

• Step 2: Build the core Logic App

  • Start with a Recurrence trigger (adjust the frequency based on how quickly you need to process new emails—e.g., every 5 minutes).
  • Add an action to fetch all active subscribers from your centralized storage.
  • Use a For Each loop to iterate over each subscriber:
    1. Call the Office 365 Outlook Get emails (V3) action, filtering for unread emails with attachments. Use the subscriber's email address from your storage entry.
    2. For each matching email, download the attachments to the Logic App's temporary storage.
    3. Transfer the attachments to the target VM—you can use Azure VM Run Command to copy files (via Azure File Share or direct blob access) or use Azure Automation Runbooks for more complex transfers.
    4. Execute your test script on the VM using Run Command or a custom script extension.
    5. Mark the email as read (or add a custom category) to avoid reprocessing.

• Pro Tips

  • Add error handling: Use Logic App's built-in retry policies for VM actions, and set up a notification (e.g., Teams/email) if a subscriber's workflow fails.
  • Use Azure Storage Queue to decouple email processing from VM operations—push attachment details to a queue, then have a separate Logic App or Azure Function handle the VM tasks.

2. Event-Driven Workflow with Microsoft Graph API + Azure Function (No Polling) #

This is the more efficient approach, as it triggers workflows only when a new email arrives (no unnecessary polling).

• Step 1: Set up a subscriber management API
  Create an Azure Function with CRUD endpoints to add/remove subscribers. When a subscriber is added:

  • The function calls the Microsoft Graph API's subscriptions endpoint to create a webhook subscription for the messageCreated event on the subscriber's mailbox.
  • Set the webhook callback URL to point to a HTTP trigger in your single Logic App.

• Step 2: Build the event-handling Logic App

  • The HTTP trigger receives the Graph API event payload, which includes the email ID and subscriber's mailbox info.
  • Use the Graph API to fetch the full email and its attachments (you'll need an Azure AD app registration with Mail.Read permissions for this).
  • Follow the same attachment transfer and test execution steps as the polling approach.
  • When a subscriber is removed, the Azure Function calls the Graph API to delete the corresponding webhook subscription.

• Pro Tips

  • Use Azure AD app registration with least-privilege permissions to access Office 365 mailboxes.
  • Validate Graph API webhook requests to ensure they're legitimate (use the validation token sent during subscription creation).

Key Optimizations for Both Approaches #

• Avoid duplicate processing: Track processed email IDs in Azure Storage or SQL Database, and filter them out in your Logic App.
• Scale VM operations: If you have many subscribers, use Azure Batch or VM Scale Sets to distribute test workloads instead of overloading a single VM.
• Monitor and log: Enable Azure Monitor for your Logic Apps and Functions to track performance and troubleshoot issues quickly.

内容的提问来源于stack exchange，提问作者OrFe