Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi @nirvana_moksh,
Since the total size of all the 7 mailboxes is big, using middle storage is a good idea. How about filtering them out in the Query Editor? Please refer to the snapshot below. Finally, only the inbox is loaded.
Best Regards,
Dale
@v-jiascu-msftCould you expand on what you meant by "middle storage"? Also, wont doing this filter to "\Inbox\", first load all data for all folders and then filter to '\Inbox\" opposed to the "Navigation" process which first defines the whole path and then starts the download for that path instead?
Thank You
Hi @nirvana_moksh,
My bad. I didn't make it clear. It's exactly what have done. Retrieve all the emails to a SQL database then connect to it from the Desktop. You can filter the email before you dump them into the DB.
Because the "Navigation" process doesn't provide a filter function. So we load all the previews and then filter them. It's a preview of data in the Query Editor. It's fine to load the whole data. You can give it a try anyway.
Best Regards,
Dale
@v-jiascu-msft- I was thinking of doing the same using SSIS, but SSIS does not have a direct connector to connect to these Mailboxes, so I came across Microsoft Graph API, would you be able to suggest more on what will be the correct way? Maybe using Graph API in conjunction with SQL DB and Power BI?
Hi @nirvana_moksh,
After surfing the graph/overview, I find the Graph API is the bridge between the emails and the SQL DB. Power BI can work directly with SQL DB. So the process could be as follows.
1. Fetch emails with Graph API and store in a SQL DB. Filter the emails if possible.
2. Connect to the SQL DB from Power BI.
Best Regards,
Dale
User | Count |
---|---|
125 | |
106 | |
99 | |
63 | |
62 |
User | Count |
---|---|
135 | |
116 | |
101 | |
71 | |
61 |