I have mirrored my Office 365 web app to my local machine. I have a custom folder created in my mailbox which is connected to one third party application. All the emails that are moved to this custom folder basically gets synced to that application.
But when I try fetching those emails using Office 365 REST APIs (based on the folder ID), I am getting an error response "ErrorItemNotFound".
But I tried with one more Office 365 account which is not mirrored, the emails sync is working perfectly. So is there any difference in pulling the emails if the account is mirrored?
{"error":{"code":"ErrorItemNotFound","message":"The specified object was not found in the store."}}
Related
I have a hybrid environment with on-prem exchange (almost done migrating) and O365 Email.
I create a new user in our on-prem AD via powershell. It syncs properly via AADConnect to our Azure environment and creates the O365 user and Exchange online (O365) email account. Using powershell I can correct proxy addresses and the msExchRecipient/Remote attributes.
The expected result is that I have an email account on both sides for the hybrid environment, with the on-prem Exchange srerver showing the Mailbox Type as "Office 365".
For one particular user, I ended up with email accounts in both on-prem and online exchange as expected. The user receives messages in their O365 account. However, messages that are trapped by our Mimecast server are not getting through. The Mailbox Type listed in on-prem is "User". This is messing up the mail routing for incoming messages from outside the domain.
Is there a way I can powershell my way out of this mess and somehow convert the mailbox type from "User" to "Office 365"? I can't migrate the user because the account already exists in O365. If I delete the O365 I would lose the email.
Should I have my powershell user creation script create the ad user, create the on-prem mailbox and also perform the migration? At least until we are fully migrated and out of our hybrid environment?
For this user, would it work to delete the AD and on-prem Exchange, and re-create both manually? How would I connect the on-prem to online exchange without losing the mail?
Any insight into this can of worms would be greatly appreciated.
One of the documents I referenced is this one about Recipient Type Values:
https://answers.microsoft.com/en-us/msoffice/forum/all/recipient-type-values/7c2620e5-9870-48ba-b5c2...
: Keith
We have on-prem machines, and a bunch of them when offline, and we didn't know for several days because the pipelines just kept waiting for the machines. How can we set up an email when they go offline?
You could leverage something like the Azure Logic App, call the Azure REST API - Agents - List via the Http Action to check the TaskAgentStatus, and send some notification like send an email when the status is offline.
I'm trying to get the ManagementCertificate for a subscription located in Germany central (Frankfurt). For a non-german Subscription, I can obtain the certificate using the old manage.windowsazure.com portal but unfortunately the old portal is not available for a subscription located in Germany central.
I already tried to retrieve the publishsettings file (which contains the ManagementCertificate) using the Azure PowerShell cmdlet. Get-AzurePublishSettingsFile:
Get-AzurePublishSettingsFile -Environment AzureGermanCloud
This will open the web page https://manage.microsoftazure.de/publishsettings/index But the site is not available...
How do I retrieve the ManagementCertificate for a subscription located in Germany central?
Looks like this is not yet supported. However, I sent the certificate to a microsoft employee who could upload the certificate.
I have a virtual SharePoint 2007 environment, comprising of a domain controller, SQL server and application server (3 VM instances). The domain name is contoso.local. I need to email-enable two SharePoint document libraries and thereby created two separate domain user accounts - userA and userB. My understanding is that if I need to send and receive email within this environment via SharePoint, I must set up SMTP service on the SharePoint installed server whose hostname is MOSS2007. So I installed the SMTP Windows component and set up a default virtual SMTP server. After doing these, I see moss2007.contoso.local and contoso.local under domains. The drop directory of the former is C:\Inetpub\mailroot\Drop.
When I started Outlook Express the first time on the SharePoint server, it prompted me to set up a user. I set one up for userA and specified an email address of usera#moss2007.contoso.local. This ended up creating a folder at c:\Inetpub\mailroot\Mailbox\contoso.local\P3_UserA.mbx. When some SharePoint event receiver code sends an email to UserA#moss2007.contoso.local, the mail file appears in this folder, instead of C:\Inetpub\mailroot\Drop. My Outlook client is able to read this message, but the SharePoint email enabled document library is unable to receive and add this email to the document library, because it must be monitoring only the drop folder.
How do I set this up correctly, so the SharePoint email enabled document libraries corresponding to UserA and UserB correctly monitor and receive the correct emails respectively?
In the POP3 configuration of the IIS POP3 service you can define a folder where the folder structure will be created under.
For each user there will be also created a subdirectory named username.mbx. Like
c:\inetpub\mailroot\mailbox\domain\username.mbx...
But SharePoint will only look into the rootfolder like c:\inetpub\mailroot\.
You need to delete those mailboxes to get it work. See also this MSDN post Incoming email problem: mail in Drop and mailbox folder but not in list on this issue.
Im kinda new to Windows server, but have been checking out Microsoft Azure and like the IaaS.
Just a question about SSO verse Azure Active Directory Sync.
Im moving my infrastructure into Azure, my base is a AD server, "dirsync" or AD FS server and a few web servers etc. We use Google Apps for Email, Calendar and Drive.
So I see that there are two ways to keep my AD directory and Azure directory in sync. SSO and Azure Active Directory Sync.
If I use Azure Active Directory Sync and not setup AD FS on a server with SSO, will I still be able to use SSO with my Azure Directory to Apps the Microsoft have in the Azure portal?
The only reason I would need a AD FS server if I had Apps/Services on site that I wanted to use SSO with, correct?
I plan to run, kayako and CrashPlan in two VM's in Azure. Both will use LDAP/AD for usernames/password authentication. But would be cool to get SSO for both webapps so employees can sing-on via the myapps.microsoft.com portal.
The two ways are DirSync and AAD Sync. Refer: Synchronization Previews Now Available for Microsoft Azure Active Directory.
Sync = Same Sign On between on-premise and cloud
Sync + ADFS = Single Sign On between on-premise and cloud
Update
myapps.microsoft.com is for third-party vendors like SalesForce who have asked Microsoft to add them as a SaaS application to AAD. It's not for company specific apps.
For company specific apps., you need ADFS as above.
Having done that, if your user SSO's into your app. and then wants to use e.g. SalesForce, they won't have to login again.