...
If the user previously had Email, the mail account still exists, and the Email Alias still points to it (that is, the only thing that was lost was a temporary lack of Affiliation or SOI, then Birthright sees an existing Email Address and decides there is nothing to do.
If the user had an Eliapps mail account that still exists in Google, but which is no longer referenced by a Primary Email Alias (which should not occur) and therefore does not appear to be active, and they now have an affiliation that gets O365 mail, then a new O365 mailbox is created and the Alias points to it. The If they now have an affiliation that gets Eliapps mail account still exists, but no new mail is sent to it.If the user had Eliapps mail, the account still exists, the alias has become Reserved, but the account was not deprovisioned, and the user now becomes a student in a School that uses Eliapps, Birthright goes through the steps of trying to create a new Eliapps account. We cannot aggregate data from Google because they limit request processing, so IIQ cannot ask if an account already exists. The Create operation sent to Google fails because the Google User object already exists. IIQ retries the Create a few times and gives up, but it is unnecessary since , IIQ attempts to create the Eliapps account but that fails because one already exists. We ignore this type of error and the old account becomes active again and behaves normally.
If the user had a no-Mail Eliapps account and a Mail O365 account, leaves, then returns as a student in a School that gets Eliapps mail, then IIQ will create a mail enabled account as “aliasname@yale.edu” the old no-Mail account was called “netid@yale.edu” and is not a duplicate, so now there are two Eliapps accounts. If the user had data in Google Drive, it appears to be gone. Generally there is no problem now, but after the user leaves any attempt to deprovision this account will discover the two accounts and probably failO365 mail and the account remained active but the Email Alias was deleted (which again should not have happened) then the account is still active. Now that Exchange Online processes all incoming mail, the Alias is no longer used to deliver mail to an O365 mailbox. Nor can this be changed. If Birthright processing were to try and create an Eliapps mail account, and even set the Primary Alias to point to “bulldogs”, then O365 mailbox would still get all the mail from Exchange Online.
If the user was gone long enough to go through the deprovisioning process, then many options were set to prevent the user from receiving mail in the old account, from logging on, or from being listed in directories. This special processing has to be undone with scripts that IIQ cannot run. To address this a report is generated each morning at 8:30 listing the users who were processed for Birthright Email. The report include a flag set when someone is deprovisioned. I read the report each day and run a Powershell script on anyone it identifies as previously deprovisioned. This takes a minute or two each day but addresses the problem.
...