#Salesforce Admin333 debatiendo

Hi Tracy - yes, Apex Messaging.sendEmail with SingleEmailMessage.setToAddresses() is the right native fit for RAW emails (no records needed, and with no names a static body needs no merge). Two refinements: 

1. Don't run it from Dev Console Execute Anonymous - that's a single synchronous shot with no restartability and it can hit governor limits. Use Batch Apex (or Queueable) and chunk it: up to 100 addresses per SingleEmailMessage, so ~50 emails total. 

2. Mind the cap - it's 5,000 EXTERNAL addresses/day per org for Apex single email (the error is SINGLE EMAIL LIMIT EXCEEDED). 5,000 fits in one day but leaves zero headroom, so if anything else in the org sends email that day you'll blow it. Safer to split across two days or run it first thing. 

The bigger flag though: Salesforce's transactional email isn't a bulk-marketing engine. 5,000 near-cold sends from raw addresses can dent your org's deliverability/reputation, and you get NO unsubscribe link, bounce handling, or open tracking. If this is marketing/newsletter, a real platform (Account Engagement/Pardot, Marketing Cloud, or even Mailchimp) is the right call - better inbox placement + built-in CAN-SPAM unsubscribe. 

If you'd rather stay native and no-code: import the 5,000 as Leads, build a list view, and use Lightning 'List Email' with your template - same 5,000/day cap, but zero Apex. 

If this helps, please mark it as the Best Answer so it helps the next person 🙂

Hi Pranav - yes, you can add the extra sites, and the pattern is one External Data Source per SharePoint site rather than reconfiguring the existing one. 

For each new site: 

1. Setup - External Data Sources - New. Type: 'Files Connect: Microsoft SharePoint Online'. Set the Site URL to that site collection's URL (a sub-site collection URL works too). 

2. Reuse your existing Authentication Provider - if the new sites are in the same Microsoft 365 tenant you do not need a new Azure AD app, just select the same Auth Provider in the lookup. (A different tenant would need its own Auth Provider.) OAuth is the only supported auth for SharePoint Online. 

3. Pick the Identity Type per data source: Named Principal (one shared service credential for everyone) or Per User (each user authenticates and inherits their own SharePoint permissions). 

4. Grant access: add each new External Data Source to the relevant Permission Sets/Profiles so users can see it. 

5. Save, then validate/sync - users will see the new site alongside the existing one under External sources in Files and can attach from it. 

So it is the same overall process, just a new External Data Source per site, sharing the Auth Provider wherever the tenant is the same. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

Short version: for a free Developer Edition org there is no Support case or phone channel - Salesforce does not provide login recovery for free orgs, so it is self-service only. A few things to try before giving up on it: 

1. On the login page use Forgot Your Password and enter your username (the email-format string you log in with - it is often not the same as your actual email). The reset link is sent to the email address on your User record, not to the username. 

2. Check that inbox carefully, including Spam/Junk, for a message from

, and add it to safe senders. A missing reset mail is almost always deliverability or the wrong inbox. 

3. If anyone else has admin access to that org, they can reset it for you from Setup > Users > Reset Password (or run System.setPassword in the Developer Console). 

If the reset email simply never arrives, it means the email on the account is one you can no longer access - and since Support will not recover a free DE org, the practical move is to spin up a fresh Developer Edition org from the developer signup page (they are free and unlimited). Any data or metadata in the old org is only recoverable if you can log back in. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks 🙂