Adding a Disclaimer to email messages in Office 365

In most emails, you could notice some disclaimer like below...
"The information of this e-mail is strictly confidential and...."
"This email and all contents are privileged..."

You can add those disclaimer in your office 365 environment too.
Here is steps for how-to,

To add a disclaimer to your company's outgoing messages, follow these steps:
- Sign in to the Office 365 portal (http://login.microsoftonline.com) as an administrator and open the Exchange Administration Center. ( See below sample screenshot)

- In the left navigation pane, click Mail Flow, and then click Rules.
- Click New, and then select "Apply disclaimers..."on the new rule page.
- In the Name of rule box, type a name for the new rule.
- Under *If, select the conditions that must met for a message to include the disclaimer.
- Under *Do the following, point to "Applend the disclaimer", and then Click Enter text, and then type the disclaimer text that you want.
- Specify any other settings that you want for the rule.
- Click Select one, and then specify a fallback action to take if the rule can't be applied.
- Under Choose a mode for this rule, click Enforce this rule.
- Click Save.

That's the how-to guide for adding a disclaimer in office 365 environment. I've attached sample screenshot for your reference. You can try to play for other option how those work.

May you all be happy.
(Be knowledgeable, pass it on then)

Comments

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, S

ICT for Myanmar in English

Search This Blog